The way you explained the entire flow is fantastic.. Thanks a lot for your post.

I too have to insert the custom fault message to the details tag of SOAP:Fault, I googled a lot and finally stopped by your amazing post…That’s what now I am going to do…

How did the XMLBeans generate the ServiceFaultDocument class but in XSD, the element is mentioned as ServiceFault?

Just one request!!!!
Can u please post the ServiceFaultDocument java class, I know it’s a generated class, just for the sake curiosity, please post it.

If you want to get right to it with your own XML schema and instance, follow these basic steps:
1) Install XMLBeans.
2) Compile your schema. Use scomp to compile the schema, generating and jarring Java types. For example, to create a employeeschema.jar from an employeesschema.xsd file:

scomp -out employeeschema.jar employeeschema.xsd

3) Write code. With the generated JAR on your classpath, write code to bind an XML instance to the Java types representing your schema. Here’s an example that would use types generated from an employees schema:

File xmlFile = new File(“c:\employees.xml”);

// Bind the instance to the generated XMLBeans types.
EmployeesDocument empDoc =
EmployeesDocument.Factory.parse(xmlFile);

// Get and print pieces of the XML instance.
Employees emps = empDoc.getEmployees();
Employee[] empArray = emps.getEmployeeArray();
for (int i = 0; i < empArray.length; i++)
{
System.out.println(empArray[i]);
}

Is this what I am suppose to do? As from what I understand, it will create a jar file but where does the EmployeesDocument datatype come from? Pls correct me and advice if I'm wrong.

Instead, I’ve used the technique described to translate my specific Java exception into the complex type the web service contract is expecting.

Cheers,
Naren