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 2009/07/28 19:29:14 UTC
[jira] Resolved: (CXF-1479) When client gets fault response, it
throws "java.lang.NoClassDefFoundError: Could not initialize class
com.sun.xml.internal.ws.fault.SOAPFaultBuilder"
[ https://issues.apache.org/jira/browse/CXF-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1479.
------------------------------
Resolution: Invalid
Fix Version/s: Invalid
Assignee: Daniel Kulp
CXF 2.0.x doesn't support Java 6 due to mismatches with the JAXB and JAX-WS version built in. Marking invalid.
> When client gets fault response, it throws "java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.internal.ws.fault.SOAPFaultBuilder"
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-1479
> URL: https://issues.apache.org/jira/browse/CXF-1479
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.4
> Environment: Client is Java 1.6 console application, Services are running under Tomcat/Java 1.6
> Reporter: Michael Berkowitz
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> The summary pretty-much says it. What I would expect is to get an exception from the invoke() that contains whatever information is in the fault message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.