that is the connection factory from the RAR, (note the .ra package) Jboss is
responsible for populating its jndi space with artifact that originate from
a deployed RAR. Have a peek at the ra.xml conatined in the .rar file to see
the contract.
2009/8/27 moonbird <moonb...@ymail.com>
>
> ...now I am getting a little bit confused. I can see the ActiveMQ
> ConnectionFactory registered in my Global-JNDI-Namespace. (Did you see what
> I posted in the JBoss forum ?) So did I find a bug ? In your described
> case
> no other JMS-Provider than JBoss Messaging could register objects in JBoss
> JNDI ?? sounds confusing :-/
>
>
>
>
> bsnyder wrote:
> >
> > On Wed, Aug 26, 2009 at 6:01 AM, Gary Tully<gary.tu...@gmail.com> wrote:
> >> use both! let the remote clients use the activemq initial context
> factory
> >> and let components within jboss use the jboss provider.
> >
> > Gary's suggestion is correct because it's actually not possible to add
> > resources to the java: context in the JBoss JNDI. The java: context is
> > read-only except for the main thread (JBoss).
> >
> > Bruce
> > --
> > perl -e 'print
> > unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> > );'
> >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bruceblog.org/
> > Twitter: http://twitter.com/brucesnyder
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JNDI-with-ActiveMQ-embedded-in-JBoss-AS-tp25151104p25167536.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
