I can see that your SOAP response doesn't include any xsi:type declarations.
Try to turn it on in your wsdd.
/Christer
-Original Message-
From: Agarwal, Naresh [mailto:[EMAIL PROTECTED]
Sent: den 30 september 2003 07:46
To: [EMAIL PROTECTED]
Cc: Christer Holmér
Subject: RE: Bug - Axis
This
might not be of very much help, but hopefully bring some hope. I have been
experiencing problems with soap arrays and .NET, but it works for us now. I
don't remember the details, but I think we had to specify the array size
explicitly in the actual soap message.
ArrayOfTransaction
This is a versioning problem with Log4j. I had the same problem while using
OpenJMS and Axis 1.1 simultaneously. The problem was that OpenJMS uses Log4J
1.3.3 and Axis uses Log4J 1.2.8. I solved the problem by altering the
classpath, including the Log4J 1.2.8 jar before the 1.1.3 jar.
Regards,
I'm not sure exactly what you want to do. I have done something similar
though. I hope that this will help you on the way.
/Christer
project basedir=../../../../ default=generate-server name=build
property name=axis_web_inf_dir
You could reload the axis context in Tomcat. I'm doing that in ANT, like
this:
target name=reload depends=init
echo message= ** reload axis **/
get src=http://localhost:80/manager/reload?path=/axis;
dest=reloadresult.txt
username=manager
The class path won't matter (at least not in the version of Axis I checked),
as a FileInputStream is created with the path to the WSDL file. The path
could be absolute or relative to your startup directory.
Taken from org.apache.axis.handlers.soap.SOAPService
/**
* Generate WSDL. If we
This works if you have JSSE installed (included in JDK 1.4). See
documentation at http://java.sun.com/products/jsse/.
In short, set the following System properties:
java.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
javax.net.ssl.keyStore=keystore_file
