Is now fixed in TRUNK
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059139#4059139
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059139
___
jboss-user mailing list
jboss-use
http://jira.jboss.com/jira/browse/JBMESSAGING-999
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056405#4056405
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056405
___
jboss
"JasonHsu" wrote : The most confusing part is the attribute name
"SourceProviderLoader" in bridge configuration file.
|
You don't want to touch the SourceProviderLoader dependency in the bridge
config. I only used that as an example of something else that uses dendendencies
anonymous wrot
I checked
http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch2.chapter.html#ch2.servicedep.fig,
however it didn't say how to do it exactly. The most confusing part is the
attribute name "SourceProviderLoader" in bridge configuration file. I have no
idea what attribute name I can use to set
This is all explained in detail in the JBoss AS guide
http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch2.chapter.html#ch2.servicedep.fig
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055986#4055986
Reply to the post :
http://www.jboss.com/index.html?modu
This is not really a question specific to JBM or the bridge, it's more of a
question of "How do I ensure one MBean deploys before another".
This is done in JBoss by declaring a dependency in the MBean deployment
descriptor, and is heavily used throughout JBoss.
In the example bridge config. for