the problem is CustomExceptionGenerator.registerFault() method propagates
JClassAlreadyExistsException (which signals a collision) in a poor way. The
error shouldn't be thrown as an exception from here, but instead you should
report it in this method, where you have relevant context information available,
such as line number, name of the fault bean, etc.
When a fault bean generated by JAX-WS and other beans in JAXB collide, the error message is very poor. It will just say:
[ERROR] generator error: com.sun.codemodel.JClassAlreadyExistsException unknown location
the problem is CustomExceptionGenerator.registerFault() method propagates JClassAlreadyExistsException (which signals a collision) in a poor way. The error shouldn't be thrown as an exception from here, but instead you should report it in this method, where you have relevant context information available, such as line number, name of the fault bean, etc.
Environment
Operating System: All Platform: All
Affected Versions
[JAXWS 2.1 EA3]