[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-21 Thread Ivan (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665760#action_12665760
 ] 

Ivan commented on GERONIMO-4475:


Update patch to support PortOffset in the activemq configuration xml file, a 
customized spring placeholder is added.
For discussion, please refer to 
http://www.nabble.com/Dual-ActiveMQ-configuration-style--WAS:-Add-tomcat-specific-configuration--tt21453929.html
Thanks !

> Improve JMS portlet for 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: Donald Woods
> Fix For: 2.2
>
> Attachments: 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.



[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-07 Thread Ivan (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661834#action_12661834
 ] 

Ivan commented on GERONIMO-4475:


I will update the portlet according to the G-4484, so remove the old patch.

> Improve JMS portlet for 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.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.



[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-07 Thread Ivan (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661510#action_12661510
 ] 

Ivan commented on GERONIMO-4475:


I divided the patch for three parts, for we could see clearly which parts are 
changed.

activemq-portlet
a. jsp files ( broker editing in the "server" folder and jms resource in 
the "jmswizard" folder )
b. java files ( broker editing and jms resource to support multiple brokers 
)
c. resource property files

geronimo-management
a. add two methods to the jmsmanager interface ( addbroker and removebroker 
)

activemq-broker
a. add a activemq-template file
b. change the activemq.xml file, use system property placeholder 
${activemq.brokerName}
c. do some modification about the plan.xml
d. change the pom file to copy the template file to the conf/template folder

geronimo-activemq
a. add a new attribute ( broker name ) for the Broker GBean 

Currently, the patch provide a simple way to add the broker. When the user 
clicks the add broker link, a big edit box will show on the page, and a 
template configuraiton file will be loaded. So that the user can directly edit 
the configuration in that edit box. When the save button is clicked, some 
actions will be done :
a. save the xml file to /var/activemq/conf/${brokerName}.xml
b. set the data folder to /var/activemq/data/${brokerName}
c. A broker gbean is added to the activemq-broker configuration

For the user could configure the connectors in the broker configuration file, 
so I removed the add connector links (actually, no implementations for it exist 
 in the current source repository).

Please help to giving any comment , thanks !

> Improve JMS portlet for 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.patch, 
> G4475-activemq-portlet.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.



[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-05 Thread Donald Woods (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660804#action_12660804
 ] 

Donald Woods commented on GERONIMO-4475:


Use 5.3-SNAPSHOT for now, as we rant into TCK failures with AMQ 5.2.

> Improve JMS portlet for 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
>
>
> 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.



[jira] Commented: (GERONIMO-4475) Improve JMS portlet for Borker configuration

2009-01-05 Thread Ivan (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660790#action_12660790
 ] 

Ivan commented on GERONIMO-4475:


After updating the local source files from svn, just find the ActiveMQ version 
for 2.2 snapshot is changed to 5.3-snapshot.
So I wonder which version we will include in 2.2, for I am working on the JMS 
portlet, I need to the right version to work with.
Thanks for giving a comment !

> Improve JMS portlet for 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
>
>
> 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.