Hi Phil,
Looks like a bug,
Can you log an issue, turn on the -V to get the stack trace, and put it
on the jira.
https://issues.apache.org/jira/browse/CXF
Thanks,
James
This is what I changed the file to...
wsdlLocation="http://192.168.81.129/Services/SalesOrderService.asmx?WSDL";
This is what I changed the file to...
wsdlLocation="http://192.168.81.129/Services/SalesOrderService.asmx?WSDL";
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl";
xmlns:jaxb="http
Strange, I can pass this without error, do you replace the wsdlLocation
and the targetNamespace?
What's the version of CXF are you using? what's the jdk version?
Can you try with hello_world.wsdl in samples, just change one of the
type to xsd:dateTime, see if it works
If you still got errors, c
Cannot get past.. WSDLToJava Error : Thrown by JAXB : JAXB version
attribute must be present
Tried adding jaxb:version="2.0" to the root jaxws:bindings element but
this did not help.
Any suggestions?
thanks
Phil
James Mao wrote:
Hi Phil,
Here is an example,
http://java.sun.com/xml/ns/j
Hi Phil,
Here is an example,
http://java.sun.com/xml/ns/jaxws";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:jxb="http://java.sun.com/xml/ns/jaxb";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
node="wsdl:definitions/wsdl:types/xs:[EMAIL PROTECTED]'http://date
Thanks James,
I'll give this a go but I'm not familiar with the binding file format.
This is what I've got from numerous web searches. Think I'm missing a
node attribute with a xpath query but not sure what it should look like.
wsdlLocation="http://192.168.81.129/Services/SalesOrderService.
What about use the java.util.Calendar or java.util.Date? will that make
any difference?
I have not tried your testcase, but you can try add a jaxws binding file
when you do wsdl2java to map the xsd:dataTime to java.util.Calendar
James
Have discovered how to log with interceptors and this has s
Have discovered how to log with interceptors and this has shown that the
string representation of the outgoing dateTime does not appear to be
"valid".
From the wsdl a field is mapped as xs:dateTime...
type="xs:dateTime"/>
When this is received from the service it comes in as...
2007-08-03T00:
