You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Vincent DiPrenda <Vi...@us.fujitsu.com> on 2009/11/13 15:46:40 UTC
SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
I'm new to this forum, and have been searching for details of the
implementation of SOAP/JMS.
I've got a few questions, if somebody will be kind enough to help me
out.
1. I've read some posts stating that the implementation has been pulled
from axis2, and now exists in the ws-commons subproject.
I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi,
but can't seem to find the implementation. Am I looking in the right
place, if not, please let me know where I can find the jar. I'm assuming
once it's found, it's a simple matter of including it in the lib
directory of axis 2.
2. I've noticed some people have had luck with MQ. If there are any
tutorials regarding the procedures I would be grateful. (Most of the
stuff I've seen is based on older versions and seem to be reliant on
features on 4.1 or older of axis2. If they're still relevant, that's
fine, but I don't want to assume.
That should be enough to get me started.
Thanks,
Vinnie
Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Posted by "Asankha C. Perera" <as...@apache.org>.
Hi Vincent
> 1. I've read some posts stating that the implementation has been
> pulled from axis2, and now exists in the ws-commons subproject.
> I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi,
> but can't seem to find the implementation. Am I looking in the right
> place, if not, please let me know where I can find the jar. I'm
> assuming once it's found, it's a simple matter of including it in the
> lib directory of axis 2.
https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport
> 2. I've noticed some people have had luck with MQ. If there are any
> tutorials regarding the procedures I would be grateful. (Most of the
> stuff I've seen is based on older versions and seem to be reliant on
> features on 4.1 or older of axis2. If they're still relevant, that's
> fine, but I don't want to assume.
The transport is against the JMS API, so as long as your MQ version
works well in JMS 1.0/1.1, things should be fine
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
RE: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Posted by Vincent DiPrenda <Vi...@us.fujitsu.com>.
Thanks for all the help so far on the SOAP/JMS work.
I think I have all the big pieces hanging together.
I've written a client, and the programs decision on the jms transport handler seems to be getting confused during runtime.
Any ideas as to why the JMS transport is not being recognized below?
------------------------------------------------------------------------------
Here is the error:
2009/11/30 14:42:47,875 [main] ERROR ClientUtils - The system cannot infer the transport information from the jms:/ESTORE.S21IB.AUTHORIZECREDITCARD.REQUEST?transport.jms.DestinationType=queue&transport.jms.ContentTypeProperty=Content-Type?java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory&java.naming.provider.url=ldap://localhost:10389/ou=DiPrenda,o=ibm&transport.jms.ConnectionFactoryJNDIName=WebServicesRequestQCF URL.
java.lang.NullPointerException
at net.paymentech.ws.paymentechgateway.wsdl.paymentechgateway_wsdl.PaymentechAuthorizeCreditCardServiceStub.authorizeCreditCard(PaymentechAuthorizeCreditCardServiceStub.java:284)
at com.canon.paymentech.client.AuthorizeClient.authorize(AuthorizeClient.java:27)
at com.canon.paymentech.client.AuthorizeClient.main(AuthorizeClient.java:53)
The Service Endpoint that I would typically use under Websphere is as follows:
WEBSPHERE:
jms:/queue?destination=ESTORE.S21IB.AUTHORIZECREDITCARD.REQUEST&connectionFactory=jms/PAYMENTECH.REQUEST.QCF&replyToDestination=jms/S21IB.ESTORE.AUTHORIZECREDITCARD.RESPONSE&targetService=PAYMENTECH&initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory&jndiProviderURL=iiop://vasudv38:9064"
Where
jms:/queue? - Indicates to the pivot handler the transport
destination=ESTORE.S21IB.AUTHORIZECREDITCARD.REQUEST - Indicates the request queue
connectionFactory=jms/PAYMENTECH.REQUEST.QCF - The QCF
replyToDestination=jms/S21IB.ESTORE.AUTHORIZECREDITCARD.RESPONSE - The response queue
targetService=PAYMENTECH - the target service
initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory - The class for the Initial Context Factory
jndiProviderURL=iiop://vasudv38:9064" - The URL for my Websphere JNDI repository
The way I intrepret the AXIS service endpoint (from the JMS example) seems to be as follows
Example:
jms:/StockQuoteRequest?transport.jms.DestinationType=queue&transport.jms.ContentTypeProperty=Content-Type&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory
Mine:
jms:/ESTORE.S21IB.AUTHORIZECREDITCARD.REQUEST?transport.jms.DestinationType=queue&transport.jms.ContentTypeProperty=Content-Type?
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory&java.naming.provider.url=ldap://localhost:10389/ou=DiPrenda,o=ibm&
transport.jms.ConnectionFactoryJNDIName=WebServicesRequestQCF
------------------------------------------------------------------------------------
FYI: I've included all the required jars to talk to IBM MQ including com.ibm.mq.soap.jar
My understanding is that the com.ibm.mq.soap.transport.jms.Handler class is the class that the pivot handler looks to for approprate jms handling. Not sure about axis. Typically on a Websphere non j2ee app I have to pass the following VM argument.
-Djava.protocol.handler.pkgs=com.ibm.mq.soap.transport
I've also created the QCF and queue entries in ApacheDS and have verified that a stand-alone JMS program can read, interpret and execute (produce and consume) with those entries.
Sorry for being longwinded, but I think to figure out why the transport isn't being understood the background might be good.
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Friday, November 13, 2009 2:29 PM
To: axis-user@ws.apache.org
Subject: Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Vinnie,
Nightly builds are available from [1]. However, I'm not sure if these are builds of the trunk (the current development version) or the branch (the code that will become version 1.0). A guess it's the trunk. However, for the JMS transport there should not be much difference between the two.
Andreas
[1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-transport-jms/1.0-SNAPSHOT/
On Fri, Nov 13, 2009 at 20:12, Vincent DiPrenda <Vi...@us.fujitsu.com> wrote:
> Thanks Andreas,
>
> I'm assuming the code in the ws-commons will be available for use as a jar file under the Axis2 environment. Is that also available to preview at this point?
>
> Asankha was kind enough to send me the a link to the source of the JMS transport code, but I'm not quite sure of how it's indented to be integrated.
>
> Thanks
> Vinnie
>
> -----Original Message-----
> From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Sent: Friday, November 13, 2009 2:00 PM
> To: axis-user@ws.apache.org
> Subject: Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
>
> On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda <Vi...@us.fujitsu.com> wrote:
>> I'm new to this forum, and have been searching for details of the
>> implementation of SOAP/JMS.
>>
>> I've got a few questions, if somebody will be kind enough to help me out.
>>
>> 1. I've read some posts stating that the implementation has been
>> pulled from axis2, and now exists in the ws-commons subproject.
>> I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi,
>> but can't seem to find the implementation. Am I looking in the right
>> place, if not, please let me know where I can find the jar. I'm
>> assuming once it's found, it's a simple matter of including it in the lib directory of axis 2.
>
> We are in the process of releasing the transports. Since it is the first release at its new home, there is no site yet. A preview is available at [1].
>
> [1] http://people.apache.org/~veithen/transport/
>
>> 2. I've noticed some people have had luck with MQ. If there are any
>> tutorials regarding the procedures I would be grateful. (Most of the
>> stuff I've seen is based on older versions and seem to be reliant on
>> features on
>> 4.1 or older of axis2. If they're still relevant, that's fine, but I
>> don't want to assume.
>>
>> That should be enough to get me started.
>>
>> Thanks,
>> Vinnie
>
Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Posted by Andreas Veithen <an...@gmail.com>.
Vinnie,
Nightly builds are available from [1]. However, I'm not sure if these
are builds of the trunk (the current development version) or the
branch (the code that will become version 1.0). A guess it's the
trunk. However, for the JMS transport there should not be much
difference between the two.
Andreas
[1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-transport-jms/1.0-SNAPSHOT/
On Fri, Nov 13, 2009 at 20:12, Vincent DiPrenda
<Vi...@us.fujitsu.com> wrote:
> Thanks Andreas,
>
> I'm assuming the code in the ws-commons will be available for use as a jar file under the Axis2 environment. Is that also available to preview at this point?
>
> Asankha was kind enough to send me the a link to the source of the JMS transport code, but I'm not quite sure of how it's indented to be integrated.
>
> Thanks
> Vinnie
>
> -----Original Message-----
> From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Sent: Friday, November 13, 2009 2:00 PM
> To: axis-user@ws.apache.org
> Subject: Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
>
> On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda <Vi...@us.fujitsu.com> wrote:
>> I'm new to this forum, and have been searching for details of the
>> implementation of SOAP/JMS.
>>
>> I've got a few questions, if somebody will be kind enough to help me out.
>>
>> 1. I've read some posts stating that the implementation has been
>> pulled from axis2, and now exists in the ws-commons subproject.
>> I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi,
>> but can't seem to find the implementation. Am I looking in the right
>> place, if not, please let me know where I can find the jar. I'm
>> assuming once it's found, it's a simple matter of including it in the lib directory of axis 2.
>
> We are in the process of releasing the transports. Since it is the first release at its new home, there is no site yet. A preview is available at [1].
>
> [1] http://people.apache.org/~veithen/transport/
>
>> 2. I've noticed some people have had luck with MQ. If there are any
>> tutorials regarding the procedures I would be grateful. (Most of the
>> stuff I've seen is based on older versions and seem to be reliant on
>> features on
>> 4.1 or older of axis2. If they're still relevant, that's fine, but I
>> don't want to assume.
>>
>> That should be enough to get me started.
>>
>> Thanks,
>> Vinnie
>
RE: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Posted by Vincent DiPrenda <Vi...@us.fujitsu.com>.
Thanks Andreas,
I'm assuming the code in the ws-commons will be available for use as a jar file under the Axis2 environment. Is that also available to preview at this point?
Asankha was kind enough to send me the a link to the source of the JMS transport code, but I'm not quite sure of how it's indented to be integrated.
Thanks
Vinnie
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Friday, November 13, 2009 2:00 PM
To: axis-user@ws.apache.org
Subject: Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda <Vi...@us.fujitsu.com> wrote:
> I'm new to this forum, and have been searching for details of the
> implementation of SOAP/JMS.
>
> I've got a few questions, if somebody will be kind enough to help me out.
>
> 1. I've read some posts stating that the implementation has been
> pulled from axis2, and now exists in the ws-commons subproject.
> I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi,
> but can't seem to find the implementation. Am I looking in the right
> place, if not, please let me know where I can find the jar. I'm
> assuming once it's found, it's a simple matter of including it in the lib directory of axis 2.
We are in the process of releasing the transports. Since it is the first release at its new home, there is no site yet. A preview is available at [1].
[1] http://people.apache.org/~veithen/transport/
> 2. I've noticed some people have had luck with MQ. If there are any
> tutorials regarding the procedures I would be grateful. (Most of the
> stuff I've seen is based on older versions and seem to be reliant on
> features on
> 4.1 or older of axis2. If they're still relevant, that's fine, but I
> don't want to assume.
>
> That should be enough to get me started.
>
> Thanks,
> Vinnie
Re: SOAP/JMS Implementation on 5.1 (IBM MQ) questions.
Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Nov 13, 2009 at 15:46, Vincent DiPrenda
<Vi...@us.fujitsu.com> wrote:
> I'm new to this forum, and have been searching for details of the
> implementation of SOAP/JMS.
>
> I've got a few questions, if somebody will be kind enough to help me out.
>
> 1. I've read some posts stating that the implementation has been pulled
> from axis2, and now exists in the ws-commons subproject.
> I've looked in the XmlSchema, AXIOM, ws-commons-java5 and Neethi, but
> can't seem to find the implementation. Am I looking in the right place, if
> not, please let me know where I can find the jar. I'm assuming once it's
> found, it's a simple matter of including it in the lib directory of axis 2.
We are in the process of releasing the transports. Since it is the
first release at its new home, there is no site yet. A preview is
available at [1].
[1] http://people.apache.org/~veithen/transport/
> 2. I've noticed some people have had luck with MQ. If there are any
> tutorials regarding the procedures I would be grateful. (Most of the stuff
> I've seen is based on older versions and seem to be reliant on features on
> 4.1 or older of axis2. If they're still relevant, that's fine, but I don't
> want to assume.
>
> That should be enough to get me started.
>
> Thanks,
> Vinnie