On Wed, May 28, 2008 at 08:19:50PM +0530, keith chapman wrote: > > I could point you to the commit that fixed this issue. But then you will > have to apply that patch against the version you are running to get it > working. >
Of course. That'd be a kind of last resort. I'll try 1.4 when I can. Thank you. > > You mean distinguish weather the response was POX or REST? I didn't really > get what you mean here. > Never mind. Only that I wasn't trying to claim that Axis2 supports or doesn't support REST. > > WSDL 2.0 is designed to use any type system, But at the moment its only XSD > that we support. So using WSDL 2.0 will not give you any advantage in > describing the schema. Ok. Thanks. Maybe it would help me in some other way. > I didn't really understand your requirement here again. But if you want the > elements to be in any order you can use <all> instead of <sequence> inside > the complexType. May be i can give you a better answer if you can explain > this a bit more. > I can't use <any> inside <all>, only <element>, and I don't know the names of all elements that can come there. My requirements are a bit insane. If you're curious, get back to my original message, it should be clearer there. But it's a bit of an academic exercise, in the sense that it is not a very useful use case. I don't think people should be expected to be doing this with Axis. Axis is useful when the data exchanged is well defined, if you have to accept nearly anything the server returns and do something close to xml-scrapping, then no middleware is going to be able to help you much (beyond an http client and an xml parser). That's why I titled it "a little beyond sanity". -- Xavi Drudis Ferran [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
