You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Fredrik Jonson (JIRA)" <ji...@apache.org> on 2009/03/12 21:24:50 UTC
[jira] Resolved: (GERONIMO-4573) OpenEJB tries to parse
sun-ejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fredrik Jonson resolved GERONIMO-4573.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.4
I can confirm that the solution in OPENEJB-1006 has resolved this issue too. When I replace the openejb-core snapshot jar with the latest release candidate in the repository of a geronimo 2.1.4-SNAPSHOT, and use the following environment setting:
JAVA_OPTS=-Dopenejb.vendor.config=GERONIMO
I no longer see the deployment failure caused by the existence of a sun-ejb-jar.xml in my ejb module.
> OpenEJB tries to parse sun-ejb-jar.xml
> --------------------------------------
>
> Key: GERONIMO-4573
> URL: https://issues.apache.org/jira/browse/GERONIMO-4573
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 2.1.3
> Environment: Deiban 5.0, sun jdk1.6u12, geronimo-jetty6 2.1.3.
> Reporter: Fredrik Jonson
> Fix For: 2.1.4
>
>
> I'm trying to create an application with a inbound rar connector implementation, and have the ear deploy properly on both Geronimo and Glassfish 2.1. To solve that I declare my resource adapter reference both in a openejb-jar.xml for the geronimo specific configuration and a sun-ejb-jar.xml for the glassfish specific configuration.
> This solution works on glassfish, it ignores openejb-jar.xml as intended. In geronimo, openejb seems to pick up and try to parse the sun-ejb-jar.xml even though the ejb module also contains both a ejb-jar.xml and openejb-jar.xml.
> Since sun-ejb-jar.xml is application server specific for Sun/Glassfish I expect Geronimo to stay away from it entirely.
> This issue has been raised before, but I could not find anything relevant in jira. Check the following mail note:
> http://marc.info/?l=geronimo-dev&m=118857105323864
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.