Serializer not found using style="wrapped"

The following service declaration specifies style="wrapped": When I invoke the web service I get: No serializer found for class com.intel.lexnet.MatchResult. I do include a beanMapping: and things work fine if there is no style="wrapped" attribute. Any thoughts on why I get a

no SOAPAction header!

Hmm, there seems to be many issues about "no SOAPAction header!" My problem is. My client code running under Eclipse driven by sdk1.4.1_02 is running fine. Then I moved my client source code, and axis related jars to clean install on a w2000 server driven by 1.4.1_05, and now I get this annoying

another Axis logging question

I'm trying to create/use a custom log4j.xml (same as log4j.properties, but XML format). As directed in the Axis documentation, I removed log4j.properties from axis.jar and have placed my custom log4j.xml in the classpath. But, now when I run the axis-admin Ant tasks (e.g., to deploy or undeploy

log4j.properties question

Is there any way to get Axis to reconfigure logging (based on an updated log4j.properties) without rebooting the servlet container that it is running inside of? Thanks, Mark

InvocationTargetException

Hi all, I deployed my web service with Tomcat 4.1.27 and axis 1.1 and I get the following error when a call is made to the service: Exception in thread "main" AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.reflect.Inv

Re: no SOAPAction header!

You could capture the messages on the wire[1] in both cases and compare them. See if the header is there, what its value is etc. [1] - http://www.mindreef.com/ Regards Jim Peter Meldgaard wrote: Hmm, there seems to be many issues about "no SOAPAction header!" My problem is. My client code r

RE: Undeploy typeMapping using org.apache.axis.utils.Admin

Thanks for your examples, Subrahmanya. I am actually looking for examples that  include deployment and undeployment, since this is what fails for me.  The failure is that does not get removed from server-config.wsdd upon undeployment.  Specifically, this is the undeployment descriptor that I ha

no SOAPAction header!

Hmm, there seems to be many issues about "no SOAPAction header!"   My problem is.   My client code running under Eclipse driven by sdk1.4.1_02 is running fine.   Then I moved my client source code, and axis related jars to clean install on a w2000 server driven by 1.4.1_05, and now I get

Re: Does Axis ignore irregularities in SOAP Faults?

The XMLA fault is clearly in error. I have no doubt that Axis is barfing on the custom fault code. The spec clearly states that any custom fault code must be namespace qualified. I'm astonished that any SOAP client could process it. My understanding is that .NET barfs on invalid fault codes. But

RE: Undeploy typeMapping using org.apache.axis.utils.Admin

Hi Ramya Nagarajan ,   Please find the legal deploy/undeploy descriptor for your convenience if it meets your criteria.   With Thanks and Regards,   B. Subrahmanya NayakMember Technical Staff,HCL Technologies Ltd.,Net Centric Division,B-41, A-11,Sector 16,Noida - 201301Ph: 120-2510701/702/

Re: Undeploy typeMapping using org.apache.axis.utils.Admin

Thanks for your suggestion, Wolfgang.  Unfortunately, the typeMapping still does not get removed from server-config.wsdd.  Even when I change the to contain all of the parameters in the undeployment descriptor as it had in the deployment descriptor, the problem still persists. Are there any exam

Re: Undeploy typeMapping using org.apache.axis.utils.Admin

> Then I have an undeployment descriptor: > http://xml.apache.org/axis/wsdd/"; > xmlns:gsdl="http://www.gridforum.org/namespaces/2002/10/gridServices"; > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; > xmlns:ogsatype0="http://www.gridforum.org/namespaces/2003/03/OGSI"; > xmlns:

Undeploy typeMapping using org.apache.axis.utils.Admin

Hi everyone,         I have some problems undeploying a typeMapping once it has been deployed.  For example, I have the following deployment descriptor:         This gets deployed using:     java  org.apache.axis.utils.Admin server server-deploy.wsdd Then I have an undeployment descriptor:

Re: Web Services and backwards compatibility

I actually posted a similar message to the group not too long ago -- > you can likely find it in an archive Oops, and even with the same subject - sorry! I certainly did a keyword search, but obviously not with the "keywords" I then used for the subject.. Ah - one apology - you wrote "compatabili

Does Axis ignore irregularities in SOAP Faults?

I have a Java application that uses the Axis client libraries to consume the services provided by a Microsoft OLAP/XMLA web service. The web service returns SOAP faults that are invalid. This has been confirmed from MS. They also go on to say that most clients they have tested with accept this irre