Hi,
Here is an explanation :)
In Codegen what happens is that the WSDL file is read and converted
into the equivalent Axis* object tree (AxisService,AxisOperation and
so on). The subsequent parts of the codegen relies on this
representation of the WSDL and what you get inside the resources
In the soap:address definition: soap:address l ocation=urlThat caused the validation error you reported. There was another extraneous line break in a namespace URI -- but I don't recall where. I suspect it might generate another error.
AnneOn 5/12/06, Sebastian J. Schultheiss [EMAIL PROTECTED]
This WSDL looks fine.On 5/10/06, robert lazarski [EMAIL PROTECTED] wrote:
Anne, might you be able to take a look at the attached wsdl ? It
validates fine, but I see the same error, created a jira, and I'd like
to track it down. Don't think this wsdl has changed - I thought
it was working in
Hi Anne,
thanks for your response. We re-run the WSDL2Java Tool after removing
the namespace attribute from the soap:body tags. However, the WSDL
that is generated by the WSDL2Java tool (the one you find in the
specified -o directory/resources) is not formatted like that, I've
attached it.
Why
For some reason the tool put a line break between the l and ocation in the location attribute in the service definition. Please file a JIRA.Anne
On 5/11/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi Anne,thanks for your response. We re-run the WSDL2Java Tool after removingthe namespace
Hi there!
We've used the attached WSDL to create a service client by means of
the WSDL2Java tool (xmlbeans databinding). After implementing the
simplest of business logics in the server, we deployed the service .aar
in the axis2 install inside a tomcat server. According to the status
page, the
Hi,You need to run generated build.xml file or specific target ant jar-client, it will create jar file for which includes all the databinding code as well supported classes. Just make sure if that jar is in your client classpath along with other axis2 and xmlbean libraries.
Hope this
Could you please log a bug in JIRA and then upload the wsdl? So that
we can track and fix the problem?
thanks,
dims
On 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi there!
We've used the attached WSDL to create a service client by means of
the WSDL2Java tool (xmlbeans
There is already is a jira for this error, judging by the stack trace:
http://issues.apache.org/jira/browse/AXIS2-649
I started digging deeper last weekend - I updated the issue - but I'm a bit swamped at the moment to go any further for now.
Robert
http://www.braziloutsource.com/On
Sebastian,There are errors in your WSDL. You must remove the namespace attributes from the soap:body binding descriptions. (The namespace attribute must be use only with RPC style.)Anne
On 5/10/06, Sebastian J. Schultheiss [EMAIL PROTECTED] wrote:
Hi there!We've used the attached WSDL to create a
Anne, might you be able to take a look at the attached wsdl ? It
validates fine, but I see the same error, created a jira, and I'd like
to track it down. Don't think this wsdl has changed - I thought
it was working in previous axis2 versions.
Thanks,
Robert
http://www.braziloutsource.com/
On
11 matches
Mail list logo
