I believe that's because these are primitive values rather than objects.
More JAXB user friendliness. If you change them to be of type Double
rather than double it should make the elements optional in the schema.
I don't understand how a schema validation problem causes your fault,
though. Here's what you showed us:
<faultstring>wrong number of arguments while invoking public
com.soap.webservice.api.ResolveAddressResult com. soap.webservice.api.
TransactionServiceEndpoint.resolveAddress(com. soap.webservice.api.Address)
throws com. soap.webservice.api.TransactionException with params
null.</faultstring>
That looks like it's coming from your service code. Can you add some
logging to where you generate the fault to see what's happening to cause it?
- Dennis
On 05/10/2013 05:39 PM, jasminadesai wrote:
Hmm...that is strange.
All others that have the same XmlElement definition do have minOccurs="0".
But the latitude and longitude properties do not have minOccurs="0". I am
now confused.
This xsd is generated by cxf. Any diea why did it not add minOccurs="0".
Regards,
Jasmina
--
View this message in context:
http://cxf.547215.n5.nabble.com/cxf-2-2-1-schema-validation-throws-error-tp5727471p5727484.html
Sent from the cxf-user mailing list archive at Nabble.com.
