embre 2002 20:49
> À : [EMAIL PROTECTED]
> Objet : RE: [JBoss-user] ExternalContext and HA-JNDI weirdness
>
>
> Sorry too little sleepI'm not communicating effectively..
>
> Heres a quick sketch out
>
> Using JBoss 3.0.2
>
>
> -Situation A - Works
>
&
wrote:
> What do you mean by "It doesn't work"? and "It fails"?
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de Brian
> > Towles
> > Envoyé : samedi, 28 septembre 2002 18:44
&g
What do you mean by "It doesn't work"? and "It fails"?
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Brian
> Towles
> Envoyé : samedi, 28 septembre 2002 18:44
> À : [EMAIL PROTECTED]
> Objet :
Howdy all
I having an issue using ExternalContext to point to a a HAJNDI instance
on a separate cluster of jboss machines.
I have JBoss to JBoss communication working fine with tyrex on an
instance to instance basis. And I have ExternalContext working fine
when I point it to the normal JNDI p
Hi,
I've added a queue, which is from jboss on a remote machine, to the global
JNDI namespace on my local machine using org.naming.jboss.ExternalContext.
I can access the queue's name but get the following exception when I try to
send a message to the queue:
[OILServerILService] Client request r
Does anyone know how I can configure an externalContext mbean within a
jboss.jcml file to allow the jboss on one machine access a queue defined in
a jboss running on a seperate machine?
Thanks for any response.
Renae.
___
JBoss-user mailing list
[EM
