Re: Axis Serialization Behavior

Thanks a lot Dennis. Cheers, -Buddhike On Tue, Mar 1, 2011 at 5:30 PM, Dennis Sosnoski wrote: > Ah, I hadn't realized you were using Axis(1). With Axis2 you can select > the data binding using a parameter to Wsdl2Java. You should be able to see > examples included in the Axis2 download, or yo

Re: Axis Serialization Behavior

Ah, I hadn't realized you were using Axis(1). With Axis2 you can select the data binding using a parameter to Wsdl2Java. You should be able to see examples included in the Axis2 download, or you can try my code from this article: http://www.ibm.com/developerworks/java/library/j-jws8.html I haven't

Re: Axis Serialization Behavior

Thanks Dennis. Do you know of a link with some sample code on how to do this? Sorry, I'm not really familier with Axis2. Thanks again. Cheers, -Buddhike On Tue, Mar 1, 2011 at 4:46 PM, Dennis Sosnoski wrote: > Hi Buddhike, > > The handling of unexpected XML elements is determined by the data

Re: Unexpected subelement

Hi Ryan, When you arbitrarily add more data to the XML content of an existing service you're breaking the service contract, in that messages using the new content will not be valid according to the older schemas. If you want to allow this type of flexibility on the service end you've got two choi

Re: Axis Serialization Behavior

Hi Buddhike, The handling of unexpected XML elements is determined by the data binding technique used. JAXB is the sloppiest data binding supported by Axis2 (on a par with WCF), and if you change to that you should be ok. - Dennis Dennis M. Sosnoski Java SOA and Web Services Consulting

Re: unsubscribe

- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org

unsubscribe

- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Unexpected subelement

So, I'm kind of remote debugging this from our clients perspective. I Got everything up and running and was able to reproduce the error with an older version of Axis2 (1.2). The newest version I have (1.5.4) does not seem to have this problem (using ADB) So upgrading is a good workaround for our cl

byte order marker

We've build a client to a .Net webservice with axis2 that doesn't work when the server returns a byte-order-marker. The service provider cannot remove these bytes on their end. Any thoughts on working around this issue. Is there a configuration option to ignore these? Is there a class we ca

unsubscribe

RE: Unexpected subelement

We have similar behavior in our axis2 ADB stubs. Although I don't think this statement is 100% accurate: 'on every request Axis checkes the endpoints WSDL and verifies that it is EXACTLY like the stubs it has' The stubs built off of the WSDL at a particular point in time. Stubs aren't dynamical

unsubscribe

Unexpected subelement

Hi, I have a soap web service served from a .net app. Sometimes we add fields to some of the objects but these are always optional and from a XML/HTTP standpoint the xml tags that represent those fields could be left out and it works fine. (like say we have user with a firstname and lastname and we

working example of Rampart - Anyone?

Hi, Anyone can point to a working complete example of Rampart code for signing and encrypting of SOAP messages? Thanks for your help.

Need help on Asynchronous Webservice implementation

Hi All, I am new to AXIS2 webservice implementation. I would like to implement webservice which has in-out type but should be treated as asynchronously. To do this i have done following change on service side: - Update MessageReceiverInOut class with following * public* *void* receive(*final*

Re: Axis Serialization Behavior

Anyone? (please... :-)) On Sun, Feb 27, 2011 at 4:28 PM, Buddhike de Silva < buddhike.desi...@geeksdiary.com> wrote: > Hi All, > > We are doing some interop tests between Axis and WCF. In our WCF service we > have a type like this. > > [DataContract] > > public class CompositeType > > { > > [Da