[prev in list] [next in list] [prev in thread] [next in thread] 

List:       geronimo-dev
Subject:    [jira] [Issue Comment Edited] (GERONIMO-6180) Persistence ref info
From:       "Ivan (Issue Comment Edited) (JIRA)" <jira () apache ! org>
Date:       2011-09-29 5:52:45
Message-ID: 1092864889.6382.1317275565450.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/GERONIMO-6180?page=com.atlassian.jira.plug \
in.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117016#comment-13117016 \
] 

Ivan edited comment on GERONIMO-6180 at 9/29/11 5:50 AM:
---------------------------------------------------------

Commit changes to trunk at r1177170.
It looks to me that, EJB builder should have no knowledge for the persistence \
references, and no need to create corresponding entries in the openejb jndi tree. \
Need to double check whether other references information should be also removed, as \
I know that Geronimo might need OpenEJB Jndi tree for some global resource access.  
      was (Author: xuhaihong):
    Commit changes to trunk at r1177170.
It looks to me that, EJB builder should have no knowledge for the persistence \
references, and no need to create corresponding entries in the tree.  
> Persistence ref info should not processed by EJBBuilder
> -------------------------------------------------------
> 
> Key: GERONIMO-6180
> URL: https://issues.apache.org/jira/browse/GERONIMO-6180
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues) 
> Components: OpenEJB
> Affects Versions: 3.0-M1
> Reporter: Ivan
> Assignee: Ivan
> Fix For: 3.0
> 
> 
> For those persistence reference information in the spec DD, they should not be \
> processed by EJB builder, as they will be handled by JPA builder.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]