[dna-issues] [JBoss JIRA] Issue Comment Edited: (DNA-640) JNDI-Based Deployment

[Randall Hauch (JIRA)]

    [ https://jira.jboss.org/jira/browse/DNA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503119#action_12503119 ] 

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?
  
> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch, HOWTO-access-DNA-JNDI.txt
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
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