You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/05/04 19:19:15 UTC
[jira] Updated: (GERONIMO-3134) jpa jndi references can refer to
gbeans in the web module, not just in parent modules. This needs to work.
[ https://issues.apache.org/jira/browse/GERONIMO-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-3134:
-----------------------------------
Attachment: GERONIMO-3134.patch
I think this fixes the problems but don't want to apply it until the server is running more smoothly.
> jpa jndi references can refer to gbeans in the web module, not just in parent modules. This needs to work.
> -----------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3134
> URL: https://issues.apache.org/jira/browse/GERONIMO-3134
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: web
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0-M6
>
> Attachments: GERONIMO-3134.patch
>
>
> Previously all the jndi references in a web app pointed to gbeans in the parent ear, or to gbeans in completely separate modules. With jpa, a persistence unit can be in a war, so jndi refs need to be able to point to gbeans in the war child configuration. Since the ConfigurationManager doesn't know about these child configurations, we need a different way to find them. I implemented a list of artifactIds (normally one or two for javaee) that let the reference traverse the tree of child configurations until it finds the right one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.