Hi Colm,

I have downloaded and compiled the 2.7.x-fixes branch.(2.7.9-SNAPSHOT)
I have run client test and test passed!!

I confirm that is has been fixed.

Thanks
JMPrieto


2014-01-28 Colm O hEigeartaigh <cohei...@apache.org>

> Hi José,
>
> You have found a bug in CXF, that Dan has fixed:
>
> https://issues.apache.org/jira/browse/CXF-5527
>
> If you want to confirm that is has been fixed, then you can try your
> test-case with the latest CXF 2.7.9-SNAPSHOT code:
>
> http://svn.apache.org/viewvc/cxf/branches/2.7.x-fixes/
>
> Colm.
>
>
> On Thu, Jan 23, 2014 at 12:29 PM, José Manuel Prieto <
> joseman...@prietopalacios.net> wrote:
>
>> Hi Colm,
>>
>> I make a new very simple example.
>>
>> https://drive.google.com/file/d/0B9NfBsCykkXqX0wwbExSZEpEeEU/edit?usp=sharing
>>
>> Steps:
>> 1.- in server folder:  mvn install. Generate a war file
>> 2.- Clean tomcat webapps/ old example, work/Catalina/*, temp/*. It solve
>> a problem with "server.jks" and signed headers.
>> 3.- Start tomcat.
>> 4.- deploy war in tomcat.
>> 5.- in
>> CXF_checkFault/client/src/test/java/es/test/cxf/checkfault/client/ClientTest.java
>> read comments and run tests.
>>
>> RESUME:
>> When: <property name="checkFaults" value="true"></property>
>> Exception because the response header is not signed. Thats OK.
>>
>> When: <property name="checkFaults" value="false"></property>
>> Only SoapException reponses are OK
>> Server Response OK, is returned in the test as null or 0.
>>
>> Thanks for your time
>> JMPrieto
>>
>>
>> 2014/1/21 Colm O hEigeartaigh <cohei...@apache.org>
>>
>>> It seems the testcase is missing a dependency:
>>>
>>> [ERROR] Failed to execute goal on project identidad-paxaseMock: Could not
>>> resolve dependencies for project
>>>
>>> es.depontevedra.soap.interoperabilidad.identidad:identidad-paxaseMock:war:0.0.1:
>>> Could not find artifact
>>>
>>> es.depontevedra.soap.interoperabilidad.identidad:identidad-cliente_xunta_identidad:jar:0.0.1
>>> in central (http://repo.maven.apache.org/maven2) -> [Help 1]
>>>
>>>
>>> In addition, I noticed that you are mixing CXF versions. The root CXF
>>> version is 2.7.8, but in the pom for identidad-paxaseMock you have:
>>>
>>> <dependency>
>>>                         <groupId>org.apache.cxf</groupId>
>>>                         <artifactId>cxf-rt-bindings-http</artifactId>
>>>                         <version>2.5.11</version>
>>>                 </dependency>
>>>
>>>  <dependency>
>>>                         <groupId>org.apache.cxf</groupId>
>>>                         <artifactId>cxf-common-schemas</artifactId>
>>>                         <version>2.3.11</version>
>>>                 </dependency>
>>>
>>> Colm.
>>>
>>>
>>> On Thu, Jan 16, 2014 at 6:52 AM, José Manuel Prieto <
>>> joseman...@prietopalacios.net> wrote:
>>>
>>> > Sorry, I explain:
>>> > 1.- Start Tomcat.
>>> > 2.- In folder "identidad-paxaseMock" run: mvn install. It generate a
>>> war
>>> > file.
>>> > 3.- Deploy war file in Tomcat.
>>> > 4.- In folder "identidad-cliente_xunta":
>>> >         - src/main/resources/spring/spring-client_paxase: it has the
>>> > property "checkFaults".
>>> >         - Test to run (TestNG):
>>> >                 -
>>> >
>>> >
>>> es.depontevedra.soap.interoperabilidad.identidad.paxase.ClientPaxase.consultarIdentidad_prueba
>>> > (OK)
>>> >                 -
>>> >
>>> >
>>> es.depontevedra.soap.interoperabilidad.identidad.paxase.ClientPaxase.consultarIdentidad_excepcion.
>>> > (SoapFault, but test must OK)
>>> > 5.- Change property "checkFault" and run again the tests.
>>> >
>>> > thanks
>>> > JMPrieto
>>> >
>>> >
>>> > 2014/1/15 José Manuel Prieto <joseman...@prietopalacios.net>
>>> >
>>> > > Hi coheigea,
>>> > > I left a project in Google Drive:
>>> > >
>>> > >
>>> > >
>>> >
>>> https://drive.google.com/file/d/0B9NfBsCykkXqNWhielRla0ZiY00/edit?usp=sharing
>>> > >
>>> > > thanks
>>> > > JMPrieto
>>> > >
>>> > >
>>> > > 2014/1/15 Colm O hEigeartaigh <cohei...@apache.org>
>>> > >
>>> > >> Could you create a test-case that shows the problem?
>>> > >>
>>> > >> Colm.
>>> > >>
>>> > >>
>>> > >> On Wed, Jan 15, 2014 at 9:23 AM, José Manuel Prieto <
>>> > >> joseman...@prietopalacios.net> wrote:
>>> > >>
>>> > >> > Unsolved
>>> > >> >
>>> > >> > I followed this steps:
>>> > >> > 0.- Create diferent calls in spring file to
>>> > >> DefaultCryptoCoverageChecker,
>>> > >> > ref, bean, property --> no changes
>>> > >> > 1.- I create a custom Interceptor --> no changes
>>> > >> > public class CustomDefaultCryptoCoverageChecker extends
>>> > >> >         DefaultCryptoCoverageChecker {
>>> > >> >
>>> > >> >     public CustomDefaultCryptoCoverageChecker(){
>>> > >> >         setCheckFaults(false);
>>> > >> >     }
>>> > >> > }
>>> > >> >
>>> > >> > 2.- Change jaxb library version: form jaxb-impl:2.2.5-2 to
>>> > >> > jaxb-impl:2.1.13. --> no changes
>>> > >> > 3.- Change spring library version form spring:3.0.5.RELEASE to
>>> > >> > spring:3.2.6.RELEASE --> no changes
>>> > >> > 4.- Continuing the trace, I get to:
>>> > >> > DocLiteralInInterceptor.handleMessage(Message message){
>>> > >> >    ...
>>> > >> >    o = dr.read(p, xmlReader); call to -->
>>> > >> > DataReaderImpl.read(MessagePartInfo part, T reader)
>>> > >> >    ...
>>> > >> > }
>>> > >> >
>>> > >> > DataReaderImpl.read(MessagePartInfo part, T reader){
>>> > >> >    return JAXBEncoderDecoder.unmarshall(createUnmarshaller(),
>>> reader,
>>> > >> part,
>>> > >> >                                              unwrapJAXBElement);
>>> > >> > }
>>> > >> >
>>> > >> > Who instance JAXB? spring?.
>>> > >> > Why only one parameter change my wolrd?
>>> > >> >
>>> > >> > thanks for readme
>>> > >> > JMPrieto
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > 2014/1/14 José Manuel Prieto <joseman...@prietopalacios.net>
>>> > >> >
>>> > >> > > Hello,
>>> > >> > >
>>> > >> > > If I put property checkFaults="false" (in sringframework
>>> application
>>> > >> > > context file), only SoapFault Messages runs as expected.
>>> > >> > > My service return a Response object. The service response is 200
>>> > (OK),
>>> > >> > > send me a Response (I see it, in the server-log), my client
>>> obtain a
>>> > >> > > Response object but, all atributes to null.
>>> > >> > >
>>> > >> > > I trace until to SoapHeaderInterceptor.handleMessage(Message m).
>>> > This
>>> > >> > > methods contains:
>>> > >> > >     public void handleMessage(Message m) throws Fault {
>>> > >> > >         SoapMessage message = (SoapMessage) m;
>>> > >> > >         SoapVersion soapVersion = message.getVersion();
>>> > >> > >         Exchange exchange = message.getExchange();
>>> > >> > >
>>> > >> > >         MessageContentsList parameters =
>>> > >> > > MessageContentsList.getContentsList(message);
>>> > >> > >         ....
>>> > >> > >
>>> > >> > > When checkFaults="true", the var parameters(MessageContentsList)
>>> > has a
>>> > >> > > List [size=1] with Response object and atributes with some
>>> values.
>>> > >> > > When checkFaults="false", the var
>>> parameters(MessageContentsList)
>>> > has
>>> > >> a
>>> > >> > > List [size=1] with Response object and atributes to NULL.
>>> > >> > >
>>> > >> > > I thought it was a problem with springframework, but now i don´t
>>> > now.
>>> > >> > > can anybody help me?
>>> > >> > >
>>> > >> > > Thanks in advance
>>> > >> > > JMPrieto
>>> > >> > >
>>> > >> > >
>>> > >> > >
>>> > >> > >
>>> > >> > >
>>> > >> >
>>> > >>
>>> > >>
>>> > >>
>>> > >> --
>>> > >> Colm O hEigeartaigh
>>> > >>
>>> > >> Talend Community Coder
>>> > >> http://coders.talend.com
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> Colm O hEigeartaigh
>>>
>>> Talend Community Coder
>>> http://coders.talend.com
>>>
>>
>>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Reply via email to