More trouble with Messaging example

When I try the messaging client, here's what I get...   C:\xml-axis>java  samples.message.testMessage Exception in thread "main" No 'methodName' option was configured for the service 'MessageService'   What is wrong?  I used the deployment descriptor provided in the download (c:\xml-axis\s

Bad envelope namespace error

I get the following error when deploying a web service using the AdminClient utility. I am working withe the latest CVs sources. Has anyone seen this error? AxisFault faultCode: http://xml.apache.org/axis/:Server.userException faultString: org.xml.sax.SAXException: Bad envelope namespace: f

Trouble with Messaging example (urn:foo)

When I try the messaging client, here's what I get...   C:\xml-axis\samples\message>java  samples.message.testMessage  -lhttp://localhost:8080/axis/servlet/AxisServlet Exception thrown in thread "main"  The AXIS engine could not find a target service to invoke!  targetService is urn:foo   W

Connection Refused Error

When I execute the following command in samples/userguide/example3 directory from Unix, I got the following error.   Command: java org.apache.axis.client.AdminClient deploy.wsdd Error: Processing file deploy.wsdd AxisFault   faultCode: http://xml.apache.org/axis/:Server.userException   faultStri

Re: Follow-Up to the email discussion about portType name vs. service name

Thomas, If you would like to send me a patch to set the service stanza name, I would be happy to commit it. Please make the options named "serviceStanzaName" with the one letter option as "S", and "portTypeName" with the one letter option as "P". (Please make sure the help messages, etc. are ch

Re: The client fails decoding the response

If I have time on Monday I will try and debug this situation. Are you using the latest version of Axis. There have been some changes in this area. Thanks Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115)

Re: determination programmatically

1) Why don't you use the WSDL2Java tool to discover which elements are needed? Run it with -d Session. 2) How are you determining the qnames for the mapping ? 3) If you are dealing with non-axis clients/servers, it is possible that arrays can be received that use the type="qname of array" form

Re: default java beans serializer/deserializer

Yes the serializer/deserializer handle complexTypes. I would suggest that you run your wsdl through WSDL2Java to build your stubs. Thanks Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115)

Re: Deploying a Serializer, but not a Deserializer??

This sounds like a bug. Have you tried the latest Axis code ? If there is a bug, I can look into it on Monday. If you don't want to install a deserializer, you *should* be able to: 1) not specify deserializer in the TypeMapping, or 2) specify deserializer with an empty string, or 3) sp

Re: SOAP and Java Reference Classes

Here's an idea. 1) Take your interface/implementation class and run it through Java2WSDL to create a wsdl file. 2) Take the wsdl file and run WSDL2Java to generate the client and server side stubs/skeletons. 3) Study the stubs and skeletons... A couple of things that I do know: a) The Axis runti

Re: New to axis arrays

Here's a couple ideas. 1) Look at the samples.echo.TestClient code. There are some examples in the code for sending and receiving arrays. 2) If you have the wsdl for the service, run WSDL2Java to generate client side stubs. Even if you don't use the stubs, you can see how the stubs invoke the

Re: AXIS alpha3 does not generate all classes

I ran the current version of WSDL2Java, and it appears that all of the files are properly generated. ArrayBindingImpl.java ArrayService.java deploy.wsdd ArrayBindingSkeleton.java ArrayServiceLocator.java undeploy.wsdd ArrayBindingStub.java ArrayPort.java SOAPStruct.ja