Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-28 Thread José Manuel Prieto
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 > Hi José, > > You have found a bug in CXF, that Dan has fixed: > > https://issues.apache.

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-28 Thread Colm O hEigeartaigh
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

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-23 Thread José Manuel Prieto
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 h

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-21 Thread Colm O hEigeartaigh
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.

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-15 Thread José Manuel Prieto
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 r

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-15 Thread José Manuel Prieto
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 > Could you create a test-case that shows the problem? > > Colm. > > > On Wed, Jan 15, 2014 at 9:23 AM, José Manuel Prieto

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-15 Thread Colm O hEigeartaigh
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 c

Re: DefaultCryptoCoverageChecker property checkFaults

2014-01-15 Thread José Manuel Prieto
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 C

DefaultCryptoCoverageChecker property checkFaults

2014-01-14 Thread José Manuel Prieto
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