[
https://issues.apache.org/jira/browse/CXF-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3762.
------------------------------
Resolution: Fixed
Fix Version/s: 2.4.3
>From a spec compliance thing, I'm not concerned. This is a non-default flag.
> It may prevent complete round tripping of wsdl -> java -> wsdl, but if you
>use the original wsdl at runtime, it should work fine.
That said, I did modify it a bit. I made no attempt to load the exception
class at code generation time. The main reason is that if you are generating
code into the maven module that also defines the exception, it won't work. By
not checking, it delays the checking to the compile step, but that should be OK.
> Add an -exceptionSuper flag, allowing wsdl2java to generate exceptions which
> extend from java.lang.RuntimeException
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-3762
> URL: https://issues.apache.org/jira/browse/CXF-3762
> Project: CXF
> Issue Type: New Feature
> Components: Tooling
> Affects Versions: 2.4.2
> Reporter: aaron pieper
> Assignee: Daniel Kulp
> Labels: jaxb, wsdl2java
> Fix For: 2.4.3
>
> Attachments: patch.txt
>
>
> When using CXF's wsdl2java tool, generated exceptions always extend
> java.lang.Exception. It would be nice if exceptions could optionally extend
> java.lang.RuntimeException instead. This could be accomplished by adding a
> flag like -exceptionSuper=.... on the wsdl2java tool, which would allow us to
> specify our own superclass.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
