[ http://issues.apache.org/jira/browse/GERONIMO-365?page=all ]
David Jencks updated GERONIMO-365:
----------------------------------
Fix Version: 1.0-M5
Description:
Currently Queues and Topics can only be created as adminobjects in a RAR
deployment. This means the user has to modify the system-jms-plan.xml, deploy a
standalone RAR or add a RAR into their EAR file; none of these options is very
friendly.
We should add a mechanism similar to the in-line stuff used to define resources
for application clients and make that available to any module type (EAR, WAR,
EJB, ...)
was:
Currently Queues and Topics can only be created as adminobjects in a RAR
deployment. This means the user has to modify the system-jms-plan.xml, deploy a
standalone RAR or add a RAR into their EAR file; none of these options is very
friendly.
We should add a mechanism similar to the in-line stuff used to define resources
for application clients and make that available to any module type (EAR, WAR,
EJB, ...)
Environment:
> Need ability to create queue/topic outside RAR
> ----------------------------------------------
>
> Key: GERONIMO-365
> URL: http://issues.apache.org/jira/browse/GERONIMO-365
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Reporter: Jeremy Boynes
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> Currently Queues and Topics can only be created as adminobjects in a RAR
> deployment. This means the user has to modify the system-jms-plan.xml, deploy
> a standalone RAR or add a RAR into their EAR file; none of these options is
> very friendly.
> We should add a mechanism similar to the in-line stuff used to define
> resources for application clients and make that available to any module type
> (EAR, WAR, EJB, ...)
--
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
