geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Charles (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Sun, 02 Nov 2008 09:01:47 GMT

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

John Charles updated GERONIMO-4337:
-----------------------------------

    Attachment: plugins.svn.diff.zip

I got some time last week to look at the compilation issue. I have attached 
pom file changes and changes to the activemq5-broker GBean class files to 
get the activemq5-broker service running in Geronimo. I tested the 
deployment of the activemq5-broker module in a geronimo-tomcat assembly and 
it fired up ok. I also tested it against a simple jms client using the 
SendRecieveQueue and it worked.

The activemq4-ra module compiles but complains about needing a GBeanInfo 
reference for MDBTransferBeanOutQueue and SendReceiveQueue mentioned in the 
plan. I ran out of time to explore this further but commenting these 
adminobjects out isolated that they were causing the module to fail on 
startup. Perhaps you can point me in the right direction here.

John C.




> Upgrade to activeMQ 5.x
> -----------------------
>
>                 Key: GERONIMO-4337
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4337
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2
>            Reporter: David Jencks
>             Fix For: 2.2
>
>         Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x.  A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the
activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept.
 From discussions with Hiram I think that trying to reconfigure the broker while its running
is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the
g. admin console.

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