You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2009/03/08 01:04:56 UTC
[jira] Closed: (OPENEJB-1006) Added 'openejb.vendor.config'
property settable to any of: geronimo, glassfish, jboss, weblogic
[ https://issues.apache.org/jira/browse/OPENEJB-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-1006.
----------------------------------
Resolution: Fixed
Ok, and here's the 3.0.1 branch commit:
Adding container/openejb-core/src/main/java/org/apache/openejb/Vendor.java
Sending container/openejb-core/src/main/java/org/apache/openejb/config/ConfigurationFactory.java
Adding container/openejb-core/src/main/java/org/apache/openejb/util/Options.java
Transmitting file data ..
Committed revision 751341.
> Added 'openejb.vendor.config' property settable to any of: geronimo, glassfish, jboss, weblogic
> -----------------------------------------------------------------------------------------------
>
> Key: OPENEJB-1006
> URL: https://issues.apache.org/jira/browse/OPENEJB-1006
> Project: OpenEJB
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 3.0, 3.1
> Reporter: Fredrik Jonson
> Assignee: David Blevins
> Priority: Minor
> Fix For: 3.0.1, 3.1.1
>
> Attachments: make-automatic-inclusion-of-sun-descriptors-optional.patch
>
>
> When a project's target environment is both Geronimo and Glassfish it is convenient if geronimo does not interfere with the sun specific deployment descriptors, such as sun-ejb-jar.xml. By default openejb currently parses both openejb-jar.xml and sun-ejb-jar.xm - which may cause deployment failures when the sun descriptor contains configurations specifically tailored for Glassfish.
> The goal of this issue is to make automatic inclusion of the sun-specific deployment descriptors optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.