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)" <de...@geronimo.apache.org> on 2006/09/23 02:49:22 UTC
[jira] Created: (GERONIMO-2427) NamingBuilders should handle both
j2ee 1.4 and jee 5 environment entries (such as resource-refs)
NamingBuilders should handle both j2ee 1.4 and jee 5 environment entries (such as resource-refs)
------------------------------------------------------------------------------------------------
Key: GERONIMO-2427
URL: http://issues.apache.org/jira/browse/GERONIMO-2427
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: buildsystem
Affects Versions: 1.2
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 1.2
(related to GERONIMO-2414). Currently the ref builders only take one kind of e.g. resource ref, either j2ee 1.4 or jee5. It's pretty easy to make them accept either kind, thus allowing incremental migration to jee5 deployment descriptors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2427) NamingBuilders should handle both
j2ee 1.4 and jee 5 environment entries (such as resource-refs)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2427?page=all ]
David Jencks closed GERONIMO-2427.
----------------------------------
Resolution: Fixed
Axis service-ref builder and env entry builder modified to use parameterized namespaces, rev 449846
sandbox javaee set to supply both namespaces rev 449847
> NamingBuilders should handle both j2ee 1.4 and jee 5 environment entries (such as resource-refs)
> ------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2427
> URL: http://issues.apache.org/jira/browse/GERONIMO-2427
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 1.2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 1.2
>
>
> (related to GERONIMO-2414). Currently the ref builders only take one kind of e.g. resource ref, either j2ee 1.4 or jee5. It's pretty easy to make them accept either kind, thus allowing incremental migration to jee5 deployment descriptors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2427) NamingBuilders should handle both
j2ee 1.4 and jee 5 environment entries (such as resource-refs)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2427?page=comments#action_12437039 ]
David Jencks commented on GERONIMO-2427:
----------------------------------------
Resource-ref, admin object ref, and ejb ref builders fixed in rev 449135 (geronimo), 449136 (openejb), and 449137 (sandbox/javaee). With these changes I can run daytrader on geronimo-jetty6-jee5
> NamingBuilders should handle both j2ee 1.4 and jee 5 environment entries (such as resource-refs)
> ------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2427
> URL: http://issues.apache.org/jira/browse/GERONIMO-2427
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 1.2
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 1.2
>
>
> (related to GERONIMO-2414). Currently the ref builders only take one kind of e.g. resource ref, either j2ee 1.4 or jee5. It's pretty easy to make them accept either kind, thus allowing incremental migration to jee5 deployment descriptors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira