[jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-578) Allow messaging to use app server's multiplex JGroups channel

[Ovidiu Feodorov (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-578?page=all ]

Ovidiu Feodorov reopened JBMESSAGING-578:
-----------------------------------------

             
Some observations:

- The dependent multiplexor service should be start as part of ServiceContainer initialization sequence, and not is startServerPeer(). Look at ServiceContainer.start(), things need to be consistent.
- I would suggest JChannelFactory instead of ChannelFactory, (in the same note, XMLJChannelFactory and everythine else ...JChannel..., to avoid confusion with our Channels)
- I would suggest NamedJChannelFactory instead of NameChannelFactory. Also, if NameChannelFactory is only used for testing, it doesn't belong in the public area, needs to go under tests.
- multiplexer-stacks.xml shouldn't be under META-INF for a scoped JBoss 4 deployment, but together with the rest of the config files, in sar's root.
- I am still seeing unprocessed $Id$ SVN tags



> Allow messaging to use app server's multiplex JGroups channel
> -------------------------------------------------------------
>
>                 Key: JBMESSAGING-578
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-578
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.2.0.Beta2
>
>
> When running JBM inside the app server, we should allow JBM to use multiplex JGroups channels that are already configured in the app server.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira