RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

Could you attach the WSS4J config you're using on both the client and server side? Colm. -Original Message- From: santhosh00724 [mailto:santhosh00...@gmail.com] Sent: 27 March 2009 17:30 To: dev@cxf.apache.org Subject: WSSecurityEngine: Callback supplied no password for: null when

RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

My Client Config : bean id=wss4jOut class=org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor constructor-arg map entry key=action value=Timestamp Signature Encrypt/ entry key=user value=myclientkey/ entry key=signaturePropFile

wsdl2java -p option change

Hi It looks like the use of the -p flag with wsdl2java has changed dor cxf 2.2. Now it reports -p option cannot be used when wsdl contains mutiple schemas for my wsdl, even though the wsdl compiles with version 2.1.4. The wsdl in question does import other schema, so I reckon that this is

Re: wsdl2java -p option change

Eamonn, On Mon March 30 2009 9:25:23 am Eamonn Dwyer wrote: It looks like the use of the -p flag with wsdl2java has changed dor cxf 2.2. Now it reports -p option cannot be used when wsdl contains mutiple schemas for my wsdl, even though the wsdl compiles with version 2.1.4. Hmm... I

Re: Uh, oh, JDK 1.6

Thanks. The MacOS 1.6 doesn't show the problem for me when I just run 'mvn', so I was stumped. On Mon, Mar 30, 2009 at 11:14 AM, Daniel Kulp dk...@apache.org wrote: On Sat March 28 2009 2:40:34 pm Benson Margulies wrote: THe 1.6 build, which I presume uses the JAXB in JDK 1.6, is breaking. I

RE: wsdl2java -p option change

Hi Dan The explicit mapping from namespace to package name works for me. I've created a to change the message in Jira for it in cxf, CXF-2144. I can volunteer for the patch too 2.1.4 did allow the unqualified specifying of package name for me though. Thanks Eamonn -Original Message-

Re: wsdl2java -p option change

On Mon March 30 2009 1:05:30 pm Eamonn Dwyer wrote: Hi Dan The explicit mapping from namespace to package name works for me. I've created a to change the message in Jira for it in cxf, CXF-2144. I can volunteer for the patch too Please do. :-) Dan 2.1.4 did allow the unqualified

RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

Thank you for reply, This is what I am getting now. I am using CXF 2.1.3. is this a problem. I tried using CXF 2.2 2.1.4 I am getting : java.lang.ClassNotFoundException: org.springframework.context.support.AbstractRefres hableConfigApplicationContext Santhosh. Original Exception with CXF

RE: wsdl2java -p option change

Hi Since XJC already supports using single package name for multiple schemas with different namespace by means of passing the -p parameter, why should this feature be disabled? If we pass -xjc-p,package-name in the wsdl2java then XJC should (and does pick) up the single package for all

GSoC Proposal:Implement the SOAP/JMS specification for CXF

Hi all, I want to take part in the GSoC. Aftter looking into the suggestions by Daniel Kulp, I have modified my proposal and published this proposal on GSoC. I have published my proposal about cxf-soapjms on http://wiki.apache.org/general/soc2009-soapjms-proposal. The GSoC page is here: