I forgot to mention--
The failure I consistently get on the server-side from running any of my
Message-style services is a NullPointerException, as you can see below.
In particular, the following lines could be enlightening. Personally I
have no clue what it is doing or why there is the word RPC in there:
"Caused by: java.lang.NullPointerException
at org.apache.axis.message.RPCElement.<init>(RPCElement.java:106)
at org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:137"
- Exception:
java.lang.NullPointerException
at org.apache.axis.AxisFault.makeFault(AxisFault.java:116)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:433)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:306)
at org.apache.axis.handlers.soap.SOAPService$SOAPRequestHandler.invoke(S
OAPService.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:154)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:121)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:288)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:57
6)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:190)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve
.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2343)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:
468)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1012)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1107)
at java.lang.Thread.run(Thread.java:536)
Caused by: 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(Dese
rializationContextImpl.java:831)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXP
arser.java:445)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Abst
ractXMLDocumentParser.java:216)
at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNames
paceBinder.java:829)
at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBi
nder.java:590)
at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidat
or.java:829)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen
t(XMLDocumentFragmentScannerImpl.java:748)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1454)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XM
LDocumentFragmentScannerImpl.java:333)
at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardP
arserConfiguration.java:525)
at org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardP
arserConfiguration.java:581)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.j
ava:1157)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa
tionContextImpl.java:202)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
... 39 more
> Hi,
>
> This is a question for people experienced in document-style web services.
> MessageService sample service works, but any attempt I make at a message
> service fails to work. Any hints as to what I am neglecting to do??
>
>
>
> Here is more detail:
>
> I made a simple client which sends a single SOAP message to the service that
> I specify. When I send it to MessageService (the sample message style server
> in the "samples\message" directory), all is well and the client receives a
> response which is an echo of the original request message.
>
> However, whenever I try to make my own MessageService-like service, I get
> an Internal Server Error as a response, whenever I use the client to invoke it.
>
> It has gotten to the point where I am cloning the MessageService files.
> All I do is replace the name MessageService with NessageService, and change
> the directory message to nessage. I make the name changes in the deploy.wsdd
> file and I change the java file name and the contents.
>
> I am doign the same exact steps for each service-- in fact I even made a
> batch file to prove this to myself. Undeploying, recompiling, puting the
> resulting class files in the appropriate WEB-INF classes directory, deploying
> the wsdd file.
>
> In fact, I have no clue what could be causing the different behaviors (working
> vs broken). Is there something significant about the wsdd file's "deployment"
> "name" attribute? (grasping at straws here.)
>
> Does anyone know where the magical document-style pivot method signature is
> documented somewhere? OF course, in my testing I am using the same exact
> signature as that which is used in OmiService, but I am wondering where that
> is documented and what kind of flexibility is allowed.
>
> Sigh. Thanks,
> Alex
