geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Borker configuration
Date Wed, 04 Feb 2009 15:59:59 GMT

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

Donald Woods reassigned GERONIMO-4475:
--------------------------------------

    Assignee: Ivan  (was: Donald Woods)

Ivan, did you run a full build including the testsuite with this patch?
I'm getting the following testsuite failure with the patch applied -
{noformat}
-------------------------------------------------------------------------------
Test set: TestSuite
-------------------------------------------------------------------------------
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.908 sec <<< FAILURE!
sendRequests(org.apache.geronimo.testsuite.enterprise.jms.MessageSenderTest)  Time elapsed:
1.053 sec  <<< FAILURE!
java.lang.Exception: did not receive message: 3
        at org.apache.geronimo.testsuite.enterprise.jms.MessageSenderTest.sendRequests(MessageSenderTest.java:74)
{noformat}

> Improve JMS portlet for AMQ 5.3 Borker configuration
> ----------------------------------------------------
>
>                 Key: GERONIMO-4475
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4475
>             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.


Mime
View raw message