[ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin... ] Brian Carothers updated DNA-640: -------------------------------- Attachment: DNA-640.patch Attached patch adds a standalone JNDI factory for the JcrEngine class that exposes JCR repositories. Multiple JCR repositories can be exposed by the same engine by creating successive JNDI references. On.ly one JcrEngine will be started/loaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin... ] Brian Carothers updated DNA-640: -------------------------------- Attachment: (was: DNA-640.patch) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin... ] Brian Carothers updated DNA-640: -------------------------------- Attachment: DNA-640.patch Uploaded a better version of the patch that will at least try to shutdown the repository if the JNDI implementation supports events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin... ] Brian Carothers updated DNA-640: -------------------------------- Attachment: HOWTO-access-DNA-JNDI.txt I agree wholeheartedly with the earlier comment about needing to document this in the Ref. Guide. However, the process isn't wholly smooth yet, as you can see from step 1 in the attached HOWTO. It does work in Tomcat though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin... ] Randall Hauch edited comment on DNA-640 at 1/9/10 10:58 AM: ------------------------------------------------------------ Do you think the factory should be logging AND throwing the exceptions? Seems to me that if it propagates an exception, it should not log it. This is usually a best practice, but this may need to be different because the engine may have multiple problems and because of the way it's part of JNDI and initialization. Thoughts? was (Author: rhauch): Do you think the factory should be logging AND throwing an exception? Seems to me that if it propagates the exception, it should not log it. This is usually a best practice, but this may need to be different because of the way it's part of JNDI and initialization. Thoughts? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira