Conflicting type generation across WSDLs

Question

I have two WSDLs that refer to the same XSD. The XSD defines a complexType T that I use as the type for a soap:fault message in wsdl A. wsdl B does not define any faults.
The problem I am seeing is that if I generate interfaces for wsdl A followed by wsdl B, then the type generated for T does not extend java.lang.Exception. This makes sense, because without any fault definitions in B, WSA thinks T is just a regular type, not an Exception type. But it's tricky because it makes the output dependent on the order of generation, and in fact you could have cases where no order gives the desired output.
I can refactor my XSD so there is one common schema and separate schemas for A and B. But I'm also wondering if there is any way WSA can allow me to solve this problem without refactoring. For example can I generate interfaces/proxies for multiple wsdl files at the same time and have WSA resolve any such conflicts?
Thanks!
-Patrick

Answer 1

What exchange are you on? Sometimes it can be months before they get round to actually migrating your line over from the old 20CN DSLAMS to the 21CN MSANS.
Sometimes, and I'm not sure on the stipulations, but a regrade in contract is required before your circuit is upgraded to 21CN. I don't think that applies if you've had the email though.
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the the reply answers your question then please mark as ’Mark as Accepted Solution’