You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2010/05/04 22:59:03 UTC
[jira] Commented: (CXF-2769) Must use Java static nested class for
faultbean when using JAX-WS java first
[ https://issues.apache.org/jira/browse/CXF-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863989#action_12863989 ]
Daniel Kulp commented on CXF-2769:
----------------------------------
Can you provide a test case? The TCK specificially does test these types of things and we have all kinds of unit and system tests as well where the beans aren't nested classes.
> 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
>
> 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.