best practices for versioning of soap faults?

Hi all, I'm curious as to what ya'll think is the best solution for versioning the sop faults returned from the server back to the client. Is there any "best practices" available for this? I currently version my wsdl's using namespace naming, and so I plan on doing the same with soap

RE: A Document confusion

Hello there, I have been struggling recently with that article,using most recent Version of Castor and axis and got all problem solved (I have even written my own ws following that model.. According to that article, u have to start with the schema (.xsd) and the WSDL file As article

RE: A Document confusion

Hello, I didn't noticed that u attached files.. Well, try to replace following lines of your WSDL file with types xsd:schema elementFormDefault=qualified targetNamespace=http://www.sequoiallc.net/test_xml/WSDL/v1_0/importType s xsd:import

Re: Socket time-outs introduced in 1.2beta3

Update on this issue: I have started getting time-outs on methods that return less data as well. When I revert to 1.2beta2, everything is back to normal and working condition. Should I enter a bug? Anand On Sun, 12 Sep 2004, Anand Natrajan wrote: : All, : : As part of the web services I am

RE: The Attributes and the UN-wrapper style

I have actually seen axis support document style (very close to wrapped) attributes in version 1.0 RC1... Here is a document-style encoded WSDL schema Snippet of a Email Add element: xs:simpleType name=EmailKind xs:restriction

Re: string arrays with doc/literal

Steven, I'm not sure exactly what is going on here, as I've never used Java2WSDL, yet. However, it seems to me that the tool would not have much information to go on, for the Bean class, and probably wouldn't be able to deserialize or serialize it. The Bean class simply has one private field,

simple explanation of document/literal

If you're relatively new to SOAP, you may find this simple explanation of document/literal useful to you: http://www.nelson.monkey.org/~nelson/weblog/tech/webservices/doclitSoap.html

Re: Can't put JAX-RPC handler to work (Newbie question)

Hi Venkat et al., thanks a lot for your answer. I have tried both of your tipps but unfortunatly I did not proceed though both ideas worked more or less (see below for details). I started believing that my problem isn't an issue with the code but maybe with the chain's namespace so that the

RE: The Attributes and the UN-wrapper style

Not that Axis does not support attributes at all it does support it in general. It just does not support it for the wrapper element, which is not really wrong since JAX-RPC spec specifies so. I could fix Axis to support it for this element which would be against the spec. I would like to know from

bug in apache axis 1.2 beta ?

Hi all, I'm usign axis 1.2 beta with jboss,as webapp no jboss-net, to access a EJB using java:EJB as provider. When I restart Jboss and try a client axis works ok, but when I restart Jboss and after getting a correct wsdl http:///axis/services/ MyService?wsdl the client fails with a

DIME using gzip

Hi there, (B (BI am tying to implement GZIP enabling Apache Axis. reffering follow URL. (Bhttp://www-106.ibm.com/developerworks/webservices/library/ws-sqzsoap.html (B (BI have successed "version web service(Default Web Service)" using gzip, (BBut DIME Web service using gzip, AXIS can not

.NET supports DIME, Axis Supports MIME,,,, how to interoperate?????

Hi ! I want to send a SOAP Attachments from .NET client to Axis Java. Have anyone tried this before? Since .NET packages the attachment according to DIME, will Axis in the server side (which uses MIME) be able to correctly interpret it? Thanx in advance Mahen