Re: CXF-DOSGI subproject ML?

András This issue has been fixed on the trunk thanks for your input Sergey On 28/09/11 19:01, András Liter wrote: Hello Sergey, I think I have found the problem, considering the following code: http://svn.apache.org/repos/asf/cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/h

Re: Cxf maven plugin on m2e indigo

It looks like starting with 1.1 of m2e, plugins themselves can embed lifecycle mappings: http://wiki.eclipse.org/M2E_compatible_maven_plugins That might be something worth looking into. A patch to accomplish that would be more than welcome. :-) Doesn't really solve the issues for 1.0, but

Re: The security context token is expired or is not valid ERROR

On Thursday, December 15, 2011 9:55:02 PM manoj_cxf wrote: > Hi Dan, > Thanks for reply. > Yes there is WS Security policy described in the given WSDL. > Can you please provide me some code sample how to put it all together. Basically, you should just need to: 1) add the cxf-rt-ws-security, cxf-r

Re: moving to cxf 2.5 org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

Yes, there was a bug fixed in WSS4J 1.6.2 that was probably causing the error you were seeing: https://issues.apache.org/jira/browse/WSS-301 Colm. On Fri, Dec 16, 2011 at 3:35 PM, fachhoch wrote: > I think its a  bug with  wss4j-1.6.0.jar  I replaced this with > wss4j-1.6.3.jar   it works. > >

Re: moving to cxf 2.5 org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

I think its a bug with wss4j-1.6.0.jar I replaced this with wss4j-1.6.3.jar it works. -- View this message in context: http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurityException-The-signature-or-decryption-was-invalid-tp5077993p5080564.html Sent from th

Re: How to treat the situation when we want to return null from the SEI method

Ok... Miguel On Fri, Dec 16, 2011 at 5:26 AM, Sergey Beryozkin wrote: > Hi > > Are you recommending to get all the XML responses from JAX-RS methods > wrapped up, and similarly unwrapped on the input ? > We don't really do that in case of JAX-RS, I think it will only introduce > the problems; > >

Re: cxf:bus overrides dynamically added interceptors by features

On Friday, December 16, 2011 8:24:12 AM Andrei Shakirin wrote: > Thanks for info Dan! > > I will test it with 2.5.1-SNAPSHOT. > > Btw: do you have already any thoughts how to harmonize the stuff in next > 2.6.X, 3.X version? I think 2.5.1 should have them acting the same. The lifecycles of the

CXF doesn't Log via FileHandler in java.util.Logging

I am pretty confused why CXF (2.5) doesn't log through Filehandler while other applications can successfully log on the same file (using same logging.properties file) . Can someone hint me if I am missing anything ? Here is my logging.properties file: handlers=java.util.logging.FileHandler .lev

Re: CXF marshalling error on the client side!

Hi, Thanks for your response. Below the code of the JaxbFactory : public class JAXBDataBindingFactory { public DataBinding create() throws Exception { JaxbConfiguration configurationManager = JaxbConfiguration.getDefault(); Map contextProperties = configurationManager.getJaxbContex

Re: How to treat the situation when we want to return null from the SEI method

Hi Are you recommending to get all the XML responses from JAX-RS methods wrapped up, and similarly unwrapped on the input ? We don't really do that in case of JAX-RS, I think it will only introduce the problems; It seems to be of some possible use for cases when we have empty responses (@Xml

Re: (JAX-RS) Mapping params to custom types

Hi Brice On 15/12/11 20:04, Brice wrote: Hi Sergey, I think I hit another issue. I think I got a workaround, yet I'm not sure it is the best way to do this. But first I'll explain the faced problem : I would like to map some exception that might be raised during the message handling, some ra

Re: moving to cxf 2.5 org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

Do you have a test-case that shows the bug? Colm. On Thu, Dec 15, 2011 at 8:20 PM, fachhoch wrote: > I enabled     org.apache.ws logging here is more debug from logs > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurit

Re: Unresolved constraint in bundle - when starting DOSGi on Felix 4.0.1

The last DOSGIi build passed in Jenkins, you may get the multibundle distro from here: https://builds.apache.org/job/CXF-DOSGi/194/org.apache.cxf.dosgi$cxf-dosgi-ri-multibundle-distribution/ Cheers, Sergey On 16/12/11 08:55, Peter Nerg wrote: Finally got it to build but it fails on a junit te

Re: Unresolved constraint in bundle - when starting DOSGi on Felix 4.0.1

Finally got it to build but it fails on a junit test case. Tried a few times in case it would be an intermittent error, but no if fails always. Not sure what file it tries to access but it fails to find it anyways. Results : Tests in error: testDiscoveryRoundtrip [felix](org.apache.cxf.dosgi.sy

RE: cxf:bus overrides dynamically added interceptors by features

Thanks for info Dan! I will test it with 2.5.1-SNAPSHOT. Btw: do you have already any thoughts how to harmonize the stuff in next 2.6.X, 3.X version? Completely refuse from Spring and support only blueprint? Use other technology to control lifecycle? Regards, Andrei. -Original Message

Re: Unresolved constraint in bundle - when starting DOSGi on Felix 4.0.1

Just realized that perhaps /mvn package/ is not sufficient as the dependencies within the sub-modules may not be resolved so I tried /mvn install/ and it worked...until I got an OutOfMemory...my poor laptop is struggling... I'll get back as soon as I've managed to build the source and deploy/confi