Ellecer Valencia wrote:
Thanks for the suggestion Dennis. I have also used it to generate
client code via CXF (which defaults to JAXB), and didn't fail on
generation of code as well.
JAXB may be stripping off the whitespace. That's what I initially
assumed should be done, but from looking at
It turns out JAXB is actually treating the whitespace as part of the
name, just like ADB (and JiBX, at present). The funny part is JAXB
actually reports an error if the name contains any invalid
non-whitespace characters.
I'll point out this problem on the JAXB list.
- Dennis
Dennis
Hi,
What's wrong with this schema fragment?
element name=authorizePurchaseResponse
complexType
sequence
element name=purchaseId type=string
maxOccurs=1
minOccurs=1/element
Hi Ellecer,
I'd say this is an error in your schema definition and should be
reported as such by the schema processing. Schema says the value of the
name attribute should be of type NCName, which only allows name
characters in the value.
Have you tried this schema with any other schema
Thanks for the suggestion Dennis. I have also used it to generate
client code via CXF (which defaults to JAXB), and didn't fail on
generation of code as well. Haven't looked at xmlbeans or jibx yet.
I also got errors about unexpected subelement when calling the web
service, but it was for
