Hiram,  I think that's a good idea since that code is so closely tied
to geronimo and can easily be affected by changes to it.  Case in
point is that I recently debugged a problem in the geronimo console
due to changes in 1.1 and ended up needing to patch the AMQ gbean
code.  I created JIRAs in both Geronimo and AMQ since I knew that this
code is really in a cross section between the two projects.

By the way, the patch I mentioned still needs to be applied so that
connectors can be created from the 1.1 console:
https://issues.apache.org/activemq/browse/AMQ-727

Also, there's a patch that prevents new connectors from being lost
across server restarts:
http://issues.apache.org/jira/browse/GERONIMO-1451


Best wishes,
Paul

On 6/5/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
Howdy Folks,

I was planing to work on a patch that takes that gbean related modules
in ActiveMQ puts them in
geronimo.  I just wanted to make sure that there are no objections to
this.  Those gbean modules are mostly just gbean related glue code
which I think make more sense living in Geronimo.  No one else outside
of the geronimo project is interested in the activemq gbean modules.

Once that part is done, then I'll start to work on merging/modifying
the port to activemq 4.x that was done the 1.2-dead branch.

--
Regards,
Hiram

Reply via email to