[
https://issues.apache.org/jira/browse/GERONIMO-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061792#comment-13061792
]
Ivan commented on GERONIMO-6047:
--------------------------------
Forget to mention the Jira number in the comment.
--->
Author: xuhaihong
Date: Thu Jul 7 15:04:25 2011
New Revision: 1143864
URL: http://svn.apache.org/viewvc?rev=1143864&view=rev
Log:
a. Make the persistence unit/context query be compatible for both client and
server side
b. ConfigurationAwareReference could work without no artifact id
> Support to access app scope persistent reference configured in other modules
> of the ear package
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-6047
> URL: https://issues.apache.org/jira/browse/GERONIMO-6047
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: naming
> Affects Versions: 3.0
> Reporter: Ivan
> Assignee: Ivan
> Fix For: 3.0
>
>
> In the scenario, an ear package configured a java:app scope persistent
> reference in the application.xml, while accessing it from the client
> application, the exception below will be thrown
> java.lang.IllegalArgumentException: javax.naming.NamingException:
> app/env/persistenceUnit [Root exception is java.lang.I
> llegalStateException: No configuration found for id:
> default/ear/1-default/car], think that it is required to update the
> PersistenceReference in the app scope, like we create client reference for
> ejb reference. Not sure what to do with global scope, need more investigation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
