Re: Axis Serialization Behavior

On 03/02/2011 07:54 PM, Buddhike de Silva wrote: > > Thanks Dennis. > > We thought about providing a xs:any element for extensibility. > However, this poses a few other problems as you mentioned below. I > wonder whether it's possible to do xs:any with maxOccurs="unbounded" > as a way of providing

Re: Axis Serialization Behavior

Thanks Dennis. We thought about providing a xs:any element for extensibility. However, this poses a few other problems as you mentioned below. I wonder whether it's possible to do xs:any with maxOccurs="unbounded" as a way of providing multiple arbirerary elements without violating XML schema. **

Re: Axis Serialization Behavior

Oh, and I should mention there's another way to get easy extensibility, which is to use attributes for simple values, rather than elements. You can use an xs:anyAttribute as part of your schema definition, and that will allow you to define new attributes in future iterations of the schema without b

unsubscribe

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

Re: Axis Serialization Behavior

Hi Buddhike, As I mentioned in my reply to a separate email on a similar issue, it's possible to design your schemas with extension points for adding more data in the future by using the xs:any element. The big limitation is that if you want to use the same namespace for your extension elements, t

Re: Axis Serialization Behavior

Thanks Josef. I like your idea. But this would be a little complicated in terms of what we are trying to achieve. To put more context around... We are building a public Web Service. And we want to be interoperable with main stream Java stacks. When it comes to releasing the next version of the prod

Re: Date help

Yes , i was thinking to do that , but i couldn't do that i use eclipse with axis2 , as i could find it allows only access the wsdl only from a url , so i can,t download the wsdl and change. or i have to change the generated stub with string for date objects. Thanks Emil On Tue, Mar 1, 2011 at

Re: Date help

Make it string instead of date. ** Martin 2011/3/1 Emil Dombagolla : > Thank you so much for your help. > > web server accept only that format. otherwise it gives an error. > > what is that transport , what i need to do there. > > thank you so much > > emil > > > > > On Tue, Mar 1, 2011 at 5:26 P

Re: Date help

Thank you so much for your help. web server accept only that format. otherwise it gives an error. what is that transport , what i need to do there. thank you so much emil On Tue, Mar 1, 2011 at 5:26 PM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote: > Why you need to preserve

Re: Date help

Why you need to preserve such format? Try using java.util.Calendar for transport. ** Martin 2011/3/1 Emil Dombagolla : > Hi all, > > Please help me on this. > > axis2 generated all my java codes based on the WSDL. > > in my code i set the date in following format,  as java.util.Date > > 2001-01-

Date help

Hi all, Please help me on this. axis2 generated all my java codes based on the WSDL. in my code i set the date in following format, as java.util.Date 2001-01-01 what i get when request send to the server is the following, Mon Jan 01 00:00:00 IST 2001 this becomes an error because of the inv

AW: Axis Serialization Behavior

Hi Buddhike Denis é all is right, breaking the contract is bad. But you can also think about how a collection would be serialized, given a collection of strings can be seen as a type. While this collection is i.e. a collection of elements and each element has name value pairs of type string.