geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-1511) Rewrite JMS portlet
Date Mon, 08 Dec 2008 23:27:44 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-1511.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   2.2
         Assignee: David Jencks

AFAICT there is only one portlet for setting up jms rars, and this has been the case for a
very long time.

> Rewrite JMS portlet
> -------------------
>
>                 Key: GERONIMO-1511
>                 URL: https://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
>            Assignee: David Jencks
>             Fix For: 2.2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message