Thanks for your answer Scott ! I really appreciate
your help !
>
> Q1 : I found two class extending HttpServlet : RPCRouterServlet and
> MessageRouterServlet : what is the difference between this two objects ?
>
> The RPCRouterServlet should be invoked when you are exposing "normal"
> methods on your service class. The MessageRouterServlet should be
> invoked when the service class implements methods with the "messaging
> signature"
> Q1 : I found two class extending HttpServlet : RPCRouterServlet and
> MessageRouterServlet : what is the difference between this two objects ?
>
> The RPCRouterServlet should be invoked when you are exposing "normal"
> methods on your service class. The MessageRouterServlet should be
> invoked when the service class implements methods with the "messaging
> signature"
==> Ok, you confirm my supposition. I used this
class because one of my collegue, using soap directly, detect this class is
used
via a PrintStackTrace in the server
method.
Question closed.
> Q2 : Is myt method correct ?
>
> This I do not know. I've never seen someone explicitly create an
> instance of a servlet class and delegate to it. I guess if you have all
> the config stuff for the instance to which you delegate included in the
> config of the delegator, initialization should work. Why do you
> delegate to doPost in the service method? Shouldn't you delegate to
> service?
>
>
> This I do not know. I've never seen someone explicitly create an
> instance of a servlet class and delegate to it. I guess if you have all
> the config stuff for the instance to which you delegate included in the
> config of the delegator, initialization should work. Why do you
> delegate to doPost in the service method? Shouldn't you delegate to
> service?
>
==> You rigth, I believe that service() wasn't
declared. I change that (but my problem is still the same, see
below)
Question closed.
> Q3 : on which parameter do I need to switch ?
>
> Typically, there is no parameter on which to switch, as the URLs used
> look like http://host:port/soap/servlet/rpcrouter and
> http://host:port/soap/servlet/messagerouter. However, you can encode
> whatever you want in the URL to determine how to switch: none of the
> SOAP code cares about the URL.
==> Super to know that ! Thanks.
Question closed.
>
> Q4 : is all the soap administration will work ?
>
> The command line admin should work. If you deploy the Apache SOAP
> webapp, the JSP pages will work, too.
==> You right, it is working fine.
Question closed.
Q5 : error on the server
:
I get an error on my client :
Generated fault: [Attributes={}]
[faultCode=SOAP-ENV:Server.Exception:] [faultString=org.w3c.dom.Node: method
getNamespaceURI()Ljava/lang/String; not found]
[faultActorURI=/servlet/uwa.maya.engine.MayaEngine] [DetailEntries=]
[FaultEntries=]
on the server, the method
org.apache.soap.transport.TransportMessage.unmarshall() fails during the
call
return
Envelope.unmarshall(doc.getDocumentElement());
This is an java.lang.NoSuchMethodError exception (
?? ) in the XML reader ??
Is somebody has an idea ?
I used the last version of xerces, and the version
2.3 of soap with a JDK 1.3
