* add some debug statements to the Stub and/or Skeleton to determine what is happening at the Call level,
* insert the monitor at the TCP level (see bottom of http://ws.apache.org/axis/java/user-guide.html) or add the logging handler to the requestChain to intercept the SOAP to debug the situation further.
Here's what I use to debug my SOAP over JMS since I don't have an HTTP connection You'll obviously need to change it slightly.
<transport name="JMSTransport" pivot="JMSSender">
<!--
<responseFlow>
<handler
type="java:org.apache.axis.handlers.LogHandler">
<parameter name="LogHandler.writeToConsole" value="false"/>
<parameter name="LogHandler.fileName" value="soap.log"/>
</handler>
</responseFlow>
-->
Ros�n H�kan wrote:
Hi, I have written an interface : public interface Myervice { public boolean logonTest(String username, String pword ); } and generated classes via java2wsdl and deployed the service. Then I wrote a client that passes a username/password to the service. My problem is that the second parameter 'pword' is empty (but not the first).
cheers - H�kan -
