You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
Seam JCR is a portable extension for CDI to a JCR (Java Content Repository) 2.0 compliant implementation (JSR-283). For now, we are testing against both JBoss Modeshape and Apache Jackrabbit (reference implementation).
To get started, add the following dependencies to your pom.xml:
<dependency> <groupId>org.jboss.seam.jcr</groupId> <artifactId>seam-jcr-api</artifactId> <version>3.1.0.Final</version> </dependency> <dependency> <groupId>org.jboss.seam.jcr</groupId> <artifactId>seam-jcr</artifactId> <version>3.1.0.Final</version> <scope>runtime</scope> </dependency> |
Name | Module role | Commit username (Git) | Organization | Hometown (Time zone) |
---|---|---|---|---|
George Gastaldi | Module co-lead | gastaldi | Independent | Joinville, SC, Brazil (UTC-3) |
John Ament | Module co-lead | johnament | Mt. Laurel, NJ, USA (UTC-5) |
Seam JCR is a portable extension for CDI to a JCR (Java Content Repository) 2.0 compliant implementation (JSR-283). For now, we are testing on JBoss Modeshape and Apache Jackrabbit (reference implementation).
Version | Time frame | Focus |
---|---|---|
3.0.0.Alpha1 | March 16th, 2011 - Released |
|
3.0.0.Alpha2 | July 22nd, 2011 - Released |
|
3.0.0.Beta1 | August 2011 |
|
This section serves as a whiteboard for design and ideas for this module. Once you've decided to pursue a feature, it should be added to JIRA as a feature request and linked from this page. It's up to you whether to keep the design notes or remove them once the JIRA issue has been created.
This section serves as a whiteboard for design and ideas for this module. Once you've decided to pursue a feature, it should be added to JIRA as a feature request and optionally linked from this page. |
Goal: Be able to map JCR events to CDI events.
If you use our proxied repository implementation, it will be automatically bound. Events are fired after the session is logged out and depending on the implementation in use the CDI events will occur in a background thread (ModeShape uses background threads). As a result, you cannot depend on a user session being active in the event firing.