Note that this is an error. You must not include the namespace attribute in the <soap:body> definition in a document style service:
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
<soap:body namespace=" http://PointsCalculator.ve.recursionsw.com/types"
use="literal" />
transport="http://schemas.xmlsoap.org/soap/http" />
<soap:body namespace=" http://PointsCalculator.ve.recursionsw.com/types"
use="literal" />
Your WSDL imports a namespace, but you don't provide the schema for that namespace. Given that you define an element of the same name in the embedded schema that you reference from the imported namespace, I don't understand why you import the namespace. I would assume that you want to reference the element defined in your schema. See my response to one of your other posts for an updated and corrected WSDL file.
Anne
On 6/8/06, Jim Bender <[EMAIL PROTECTED]> wrote:
Deepal,
I am not really sure what you are asking, but I am replying with the
two files attached,
instead of "inline" (the WSDL file and the generated skeleton).
The WSDL file is that generated by Java2WSDL with the duplicate complex
type definition removed.
I am reviewing how I invoke WSDL2Java. Right now, I am using
the command line that I use for Axis2 0.93, which works well.
In the WSDL file, these two document elements seemed to imply that I should see
the document/literal style service generated, as I expected and as I
get by default
in Axis2 0.93:
<soap:binding style="document"
transport=" http://schemas.xmlsoap.org/soap/http" />
<soap:body namespace="http://PointsCalculator.ve.recursionsw.com/types"
use="literal" />
The WSDL2Java is run using Leafcutter to execute the Java Ant task with
a command line to invoke WSDL2Java, as I do for my 0.93 implementation.
Regards,
Jim
On 6/8/06, Deepal Jayasinghe < [EMAIL PROTECTED]> wrote:
> forward with correct prefix
>
> Jim Bender wrote:
>
> > I hand-edited the wsdl file generated from the Java2WSDL process to
> > remove the duplicate complex type definition and skipped WSDL
> > generation. What I ended up with was a skeleton for a
> > non-document/literal web service:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
