Re: incomplete generated WSDL file

I strongly recommend _against_ using Java2WSDL - the WSDL is very poor in my opinion. Last time I used Axis I hand-cut the WSDL; vetted it within XMLSpy & Eclipse (uses the W3C test suite) and used WSDL2Java. On 12/10/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: Hi,   I am using Axis v1.4.   My a

Re: Schema Validation (WAS: [axis2] Validating Messages :: WSDL :: )

If there is going to be a discussion then I would very much like to participate in it. I am in the middle of building a production system where I do in fact need to validate against the schema. In fact the WSDL (doc literal) will form the basis of a commercial interface specification for 3rd partie

Re: [axis 1.4] - AxisFault - Bug

Line 994, 1009, etc are in error:  

Re: WSDL2Java and one-way binding

I've given up on service-generated-WSDL - I hand-cut/validate WSDL and use WSDL2Java to generate both the server-side skeleton and the client side stubs. I haven't done it yet but I'm told its straight forward to modify the generated code to return static WSDL files rather than genertaing WSDL on t

Re: [1.3] Handling arrays - interop with .NET

Contrary to what appears to be standard practice I've abandoned the JavaServiceClass->WSDL approach and start from hand-cut WSDL which I validate using an Eclipse plug-in (checks against WS-I). I also check the WSDL within XMLSpy2006. I've take this approach because I currently have a situation whe

Re: [1.3] Handling large values

I'd suggest moving to a multi-message interchange and server-side reassembly of the data. I'm in the process of doing this very thing but that's because my data is a list of XML elements of logically unbounded length... On 6/29/06, Simon McMahon <[EMAIL PROTECTED]> wrote: > Why Not use attachm