[rhauch]

I've replicated the issue and found a fix. Basically, it was a timing issue oly when a new repository was initialized: the "/jcr:system" content was created and saved, and the Repository components (e.g., lock manager, namespace manager, etc.) tried reading the "/jcr:system" content before the cached content (without the "/jcr:system" tree) was flushed at the end of the save operation. The fix will be in the next release.

[rhauch]

I'm just about ready to merge in the fix for all these (JNDI- and JTA-related) issues, and the Alpha5 will contain all the fixes. We also now have Arquillian integration tests that use EJBs to verify that this functionality is working.

I should point out, however, that I changed the default JNDI names to be a bit more consistent with the typical JNDI names used by other implementations. We used to register a repository at "jcr/local/{repositoryName}", and the "local" segment was a bit unnatural since many other implementations often use "jcr/local" for the repository instance.

With Alpha5, the JNDI names will be different. Each repository is always registered at "jcr/{repositoryName}" (notice the "local/" segment has been removed), and if a custom JNDI name is explicitly specified in the repository configuration then the repository is also registered at that name. Likewise, ModeShape's 'org.modeshape.jcr.api.Repositories' implementation (e.g., the engine) is now registered at "jcr". See our documentation for more details and code examples.