] Why do I get service skeletons taking
OMElement, and uncompilable code?
Oops, a little late here and I misread the method
signature. Getting
XmlObject instead of OMElement probably isn't what you
were hoping
for, so perhaps as Anne implied xs:any is the culprit.
Do keep
@ws.apache.org
Subject: Re: [Axis2] Why do I get service skeletons taking
OMElement, and uncompilable code?
Oops, a little late here and I misread the method signature.
Getting XmlObject instead of OMElement probably isn't what
you were hoping for, so perhaps as Anne implied xs:any
, 2006 5:38 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Why do I get service skeletons taking
OMElement, and uncompilable code?
Oops, a little late here and I misread the method signature.
Getting XmlObject instead of OMElement probably isn't what
you were hoping for, so perhaps
I suspect it's because you have xs:any in your schema. Since WSDL2Java doesn't know what will be in the message, it defaults to OMElement.AnneOn 6/20/06,
Derek [EMAIL PROTECTED] wrote:
I'm getting rather frustrated trying to use Axis2 to do something apparentlypretty basic.Using the WSDL and
, June 20, 2006 5:10
PMTo: axis-user@ws.apache.org;
[EMAIL PROTECTED]Subject: Re: [Axis2] Why do I get service
skeletons taking OMElement, and uncompilable code?I
suspect it's because you have xs:any in your schema. Since WSDL2Java doesn't
know what will be in the message, it defaults
To add to what Anne said, you're using a version of axis from May 05,
2006 . While that may be the official 1.0 release, there were several
important bugs fixed for xmlbeans after that.
The good news is that this is the code that I was able to produce from
the latest nightly:
/**
*
Oops, a little late here and I misread the method signature. Getting
XmlObject instead of OMElement probably isn't what you were hoping
for, so perhaps as Anne implied xs:any is the culprit.
Do keep in mind the bug fixes in the xmlbeans code since the 1.0
release, however.
Good luck,
Robert
