You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <ji...@apache.org> on 2006/11/17 07:07:37 UTC

[jira] Updated: (GERONIMO-1511) Rewrite JMS portlet

     [ http://issues.apache.org/jira/browse/GERONIMO-1511?page=all ]

Matt Hogstrom updated GERONIMO-1511:
------------------------------------

    Fix Version/s: Wish List
                       (was: 1.2)

> Rewrite JMS portlet
> -------------------
>
>                 Key: GERONIMO-1511
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1511
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ, connector, console
>    Affects Versions: 1.0
>            Reporter: Aaron Mulder
>             Fix For: Wish List
>
>
> The JMS connection factory and destination portlets should be replaced by a single JMS manager portlet.  This should use the JMSManager and show all the available JMS brokers, listing the available connection factories and destinations for each one.  When adding a connection factory or destination, it should use the JSR-88 DConfigBeans to construct the deployment plan for the new configuration.  I'm not yet sure whether it should group the resources by configuration, perhaps just list the owning configuration there.  I'm also not sure whether it's important to be able to add connection factories and destinations simultaneously in a single new configuration -- probably not, though it would be nice in terms of generating plans and so on.

-- 
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