Hi ,
Has anyone successfully implemented the JMS transport handler in Wrox
Axis book(pg 155)
using Beta 2? I basically took the example and taylored it to my own needs
but the JMSListener
seems to choke on the message. With the book based on Beta 1 I'm guessing
it may be a compatibility
issue. On the server where JMSListener is running I get:
---Invoking AxisServer.invoke()---
java.lang.NullPointerException
java.lang.NullPointerException
at org.apache.axis.message.RPCElement.<init>(RPCElement.java:106)
at
org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:137)
at
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deserializa
tionContextImpl.java:831)
at
org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1376)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidat
or.java:1214)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1182)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:374)
at
org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationCon
textImpl.java:202)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:306)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:279)
at JMSListener.onMessage(JMSListener.java:128)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1806)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1765)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.Kernel.execute(Kernel.java:229)
at weblogic.kernel.Kernel.execute(Kernel.java:241)
at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:1687)
at weblogic.jms.client.JMSSession.invoke(JMSSession.java:2016)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:504)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchOneWay(DispatcherImpl.java:42
9)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Anyone else experiencing this?
Thanks,
-Cyrus
-----Original Message-----
From: Lyndon Durham [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 26, 2002 1:02 PM
To: [EMAIL PROTECTED]
Subject: Re: Does AXIS supports SMTP. JMS etc.
Transports and handlers are used to allow developers the ability to
configure and deploy their own usage or implementation of Axis. The core
of Axis is the Engine that handles the actual SOAP Message etc.
Therefore in short even though Axis ships with a HTTP transport as part
of the Axis release, the impetus is up to you to use whatever transport
protocol you choose to get the SOAP Message to the Axis Engine. So you
could build any number of transports i.e smtp,jms, file transport etc.
