Axis 2.0
currently supports the JNDI
lookup model, with the client invocation looking something like:
jms:/Topic?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url="">
The full
documentation is in Subversion, /xdocs/1_1/jms-transport.html.
The docs seems to indicate that it has been tested (only?) with
ActiveMQ, but I’ve
used it with Tibco EMS as well. InitialContext is used to get both the
ConnectionFactory
and Destination.
Brennan Spies
Sr. Programmer
Analyst
Shared
Application Services
-----Original
Message-----
From: Brian De Pradine
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 24, 2006 10:27 AM
To:
[email protected]
Cc:
[EMAIL PROTECTED]
Subject: RE: WS
Addressing ::
Axis2 :: JMS Webs ervice lookup issues
Hello Vaibhav,
I
would have responded earlier, but I was out last week. Anyway, I recall
from
one of your earlier emails that you were using WebSphere to host your
JMS web
service. If this is the case, then you may be able to use the new
client here
[1] to access it. This client runs in a J2SE environment, and supports
things
like JNDI look up. Do note, however, that I am not sure whether the JMS
support
in Axis2 will work with this client. I believe that it was only tested
with
ActiveMQ, but I could be wrong :-)
[1]
http://www-1.ibm.com/support/docview.wss?uid=swg24012804
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will
you find
the time to do it again?
"Vaibhav
Pandey" <[EMAIL PROTECTED]> wrote on 16/10/2006 06:05:19:
> Hi,
> I am trying to forward reply from
the
destination WS to another WS(actually
> a JMS WS) using WS Addressing.
> For this i need to specify various
configurations like:
>
>
java.naming.provider.url="" etc....now as given in my
> examples its usually
tcp://localhost:port and
thn tcp is configured in
> axis2.xml
>
> Now as i can see in the axis2.xml
file there
are configurations for tcp but
> not for iiop.....does that make any
difference ??
> Bcoz after configuring all the
required
parameters, i am getting an error
> that unable to do the lookup.....i
have tried
practically all possible
> configurations.........kindly let
me knw if u
r aware of any configuration
> details regarding this..............
>
>
> Thanks & Regards,
> Vaibhav
>
>
>
> -----Original Message-----
> From: Sanjiva Weerawarana
[mailto:[EMAIL PROTECTED]]
> Sent: Saturday,
October 14, 2006 7:26 PM
> To: [email protected]
> Subject: Re: WS Addressing :: Axis2
:: JMS
Webs ervice lookup issues
>
>
> On Fri, 2006-10-13 at 11:43 +0530,
Vaibhav Pandey
wrote:
> > Hi all,
> > i have a small doubt regarding
the
protocol to be used during lookup of my
> > JMS WS installed in an
application
server other than the one in which i
> have
> > installed axis...........
> >
> > as mentioned in all tutorials:-
> > tcp://localhost:6061
> > there is a mapping of tcp with
transport
recievers and transport senders
> in
> > axis2.xml but there is nothing
of this
sought for iiop ..........
> > My JMS WS is in web sphere
RAD6 and i
want to do a lookup of it:-
> > iiop://localhost:2809
> >
> > Do i need to add any new
entries in this
file in order to provide support
> > for iiop or is it that there
is no
support yet for it ??
>
> There's no support for it. As far
as I know
there aren't any SOAP stacks
> that support sending SOAP over
IIOP. Its not
theoretically impossible
> but its not a common pattern for an
object to
receive a SOAP message as
> a string first argument!
>
> Can you explain what you're looking
for?
>
> Sanjiva.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail:
[EMAIL PROTECTED]
>
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail:
[EMAIL PROTECTED]
>
