cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Súsanna Þorvaldsdóttir (JIRA) <j...@apache.org>
Subject [jira] Commented: (CXF-2463) SOAP 1.2 service return SOAP 1.2 Fault message in response to SOAP 1.1 request when exception is thrown
Date Fri, 11 Dec 2009 09:53:18 GMT

    [ https://issues.apache.org/jira/browse/CXF-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789198#action_12789198
] 

Súsanna Þorvaldsdóttir commented on CXF-2463:
---------------------------------------------

I am desperate, I only have this error if I am using cxf version 2.1.9 or 2.2.5.

If I use less version like 2.1.3 we get the build error:
urls[39] = file:/C:/Users/susanna/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/C:/apache-maven-2.0.10/lib/maven-2.0.10-uber.jar
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org/apache/log4j/Appender
org.apache.log4j.Appender
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/log4j/Appender
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:247)
	at org.apache.cxf.common.logging.LogUtils.<clinit>(LogUtils.java:80)
	at org.apache.cxf.BusFactory.<clinit>(BusFactory.java:40)
	at org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:260)

We are working with a big project that have 1 parent pom and 5 children. 
The above error makes me need to clean and package all 5 children if I change the code, and
that takes 5 min. just because I change one file.
This project has 20-30 wsdl from different vendors. Where there are conflict with user

I have quite a few of settings like these:
 <wsdlOption>
     <wsdl>${basedir}/src/main/resources/wsdl/xx.wsdl</wsdl>
           <extraargs>
                <extraarg>-p</extraarg>
                <extraarg>is.xx.yy</extraarg>
            </extraargs>
</wsdlOption>

I have tested maven 2.2.1 and 2.0.10, cxf 2.1.3 up to 2.1.8 and 2.2.5 down to 2.2.3, I am
using Intell. 9 and 9beta.

Nothing has helped, and I haven't found any information about this on the web.



> SOAP 1.2 service return SOAP 1.2 Fault message in response to SOAP 1.1 request when exception
is thrown
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2463
>                 URL: https://issues.apache.org/jira/browse/CXF-2463
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.2.3
>            Reporter: Michael Brennan
>            Assignee: Daniel Kulp
>             Fix For: 2.1.8, 2.2.5
>
>
> I've created a JAX-WS web service using JAXB databinding that I would like to support
both SOAP 1.1 and SOAP 1.2. Based on info I saw referenced elsewhere, I configured it as a
SOAP 1.2 endpoint expecting that CXF (as of version 2.2.3, anyway) would properly return a
SOAP 1.1 response to a SOAP 1.1 request.
> This works fine for successful responses, but when my service throws an exception, CXF
is returning a SOAP 1.2 fault message. I tried changing my code to throw a SOAPFaultException
and used SOAPFactory to explicity create a SOAPFault for SOAP 1.1. protocol. In this case,
the fault code ends up scoped to the SOAP 1.1 namespace, but it's returned in a SOAP 1.2 envelope
(and SOAP 1.2 format Reason).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message