geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration
Date Wed, 08 Jul 2009 09:40:14 GMT


Forrest Xia commented on GERONIMO-4475:

A bug found:
if stopped a new created broker, the JMS resources page will show nothing, even the default
broker is still running! 
Moreover, the jms connector module which depends on the new created broker is still in running
state. But we should expect it in stopped state.

> Improve JMS portlet for AMQ 5.3 Broker configuration
> ----------------------------------------------------
>                 Key: GERONIMO-4475
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 2.2
>            Reporter: Ivan
>            Assignee: Ivan
>             Fix For: 2.2
>         Attachments: G4475-activemq-broker-00.patch, G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch,
G4475-geronimo-activemq.patch, G4475-geronimo-management.patch
> Currently in the administrator console, the users could not add another embed broker.
Also, they could not edit the broker through administrator console.
> I list the features that I could see :
> 1. While creating the broker, let the use upload a  configuration file. 
> 2. While editing the broker, show a text area, so that the user could edit the spring
XML file in it. Shall we give the user a more friendly interface, so that they do not need
the edit the XML file directly. I am not sure how it should look like.
> 3. Update the connector port let,  so that while creating a new connector, the user could
specify the broker that it belongs to.
> Please help to give some comments !

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message