[
https://issues.apache.org/jira/browse/CXF-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pederson updated CXF-2769:
-------------------------------
Attachment: cxf2769.tar
Yes, you're right. I apologize. I could have sworn I tried that.
I removed the non-static nested version (HelloFault2) and kept the un-nested
version (HelloFault3). The demo now works with both versions. I've
re-attached for anyone else who is interested.
-- Eric
> Must use Java static nested class for faultbean when using JAX-WS java first
> ----------------------------------------------------------------------------
>
> Key: CXF-2769
> URL: https://issues.apache.org/jira/browse/CXF-2769
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.7
> Reporter: Eric Pederson
> Attachments: cxf2769.tar
>
>
> You have to use a Java static nested class of the Exception class for a
> faultbean when using JAX-WS java first. All other types of classes result
> in errors of the type
> org.apache.cxf.interceptor.Fault: Could not find JAXB information for bean
> class <bean class> in context. Make sure it follows JAXB conventions.
> You should be able to use any class if it follows the guidelines of JAX-WS
> section 3.7
> Better yet CXF should be able to generate the bean classes off the Exception
> classes dynamically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
