Looks right for your message.
You can perhaps put some debugging in your code that generates the
TransactionException fault to tell you exactly what causes the fault.
From the message I'm guessing it's that the expected Address parameter
is not found, which is why I thought the elementFormDefault might be a
problem. Unfortunately JAXB unmarshalling just ignores anything it
doesn't know how to handle, and also ignores when required elements are
missing, so if there's anything at all off in your XML you end up with
null values passed to your code without any warning.
Aside from that, if you can show us the JAXB annotations on the Address
class that would confirm that the schema matches with the JAXB
annotations are saying.
- Dennis
On 05/10/2013 04:17 PM, jasminadesai wrote:
Here is the start of my schema definition:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:tns="http://test.webservice.com/transaction";
attributeFormDefault="unqualified" elementFormDefault="unqualified"
targetNamespace="http://speedtax.com/transaction";>
My schema and wsdl is auto generated from the java code and the soapui
request was created by importing the wsdl.
Is anything missing from what I am doing?
Regards,
Jasmina
--
View this message in context:
http://cxf.547215.n5.nabble.com/cxf-2-2-1-schema-validation-throws-error-tp5727471p5727479.html
Sent from the cxf-user mailing list archive at Nabble.com.
