/src/main/resources/wsdl/myService.wsdl
>
> -client
> -server
> -impl
>
>
>
> Regards,
> /Joe
>
> On Fri, Mar 31, 2017 at 5:33 AM, Giriraj Bhojak <girira...@gmail.com>
> wrote:
>
> > Hello,
> >
> > I have been trying to gener
Hello,
I have been trying to generate only mapped java classes from schema types
in WSDL. I do not need any client or server code. Just the POJOs.
I have tried various options listed on cxf.apache.org/docs/wsdl-to-java.html
I basically need to reuse the classes for a Java Rest client
r version).
>
> Colm.
>
> On Wed, May 11, 2016 at 8:31 AM, Giriraj Bhojak <girira...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I need to ensure that a text file I send using WS-Security policy must be
> > signed and encrypted as well.
> > Without using secu
Hi,
I need to ensure that a text file I send using WS-Security policy must be
signed and encrypted as well.
Without using security policy, I am able to send the file properly to a
jaxws based CXF endpoint.
MTOM is enabled as well.
When I enable WS-Security policy for that endpoint, I get an error
Hello,
I am trying to add ws security jaxws properties at global level for all the
endpoints configured via Spring, but adding them to cxf:bus element doesn't
seem to work, I have to replicate same properties in individual jaxws
endpoint declaration.
Is there a way to add jaxws properties
systest/ws/x509/DoubleItX509.wsdl;h=dcf01b23c124795a04be170f5d8079102a516b35;hb=HEAD
>
> On Wed, Mar 23, 2016 at 5:50 PM, Giriraj Bhojak <girira...@gmail.com>
> wrote:
>
>> Thank you Colm.
>> Would you have a policy example of using EncryptedElements instea
> On Wed, Mar 23, 2016 at 4:49 PM, Giriraj Bhojak <girira...@gmail.com>
> wrote:
>
>> Do you mean to say the timestamp is not just signed but encrypted as well
>> if it is part of the AsymmetricBinding?
>>
> No, just signed.
>
>> In my policy
Hello,
I need to sign and encrypt the timestamp WS-Security header.
My policy file has following assertions:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
" />
Hi,
I have been struggling with a basic question related to using signing and
encryption for REST services.
If the REST call (using JSON) happens over http or https via a browser, how
can I ensure that JSON payload is signed and encrypted, just like a SOAP
request that is signed and encrypted?
Thank you very much Sergey.
Thanks,
Giriraj
On Mar 18, 2016 6:06 AM, "Sergey Beryozkin" <sberyoz...@gmail.com> wrote:
> Hi,
> On 18/03/16 00:21, Giriraj Bhojak wrote:
>
>> Thank you Sergey.
>> I went through the spec. It mentions that the spec is not stab
t;> and a regular Java HTTP server, the data are signed, using JOSE (JWS
>> Compact) as one option.
>>
>> I actually presented this demo at Apache Con NA 2015, except I replaced
>> the demo server with a CXF JWS-enabled server.
>>
>> Sergey
>> On 17/03/16
See here:
>
> http://cxf.apache.org/docs/ws-securitypolicy.html
>
> Colm.
>
> On Mon, Mar 7, 2016 at 6:20 PM, Giriraj Bhojak <girira...@gmail.com>
> wrote:
>
> > Hello,
> >
> > WS-SP 1.3 doesn't support RSA with SHA256 as asymmetric algorithm.
> &g
Hello,
WS-SP 1.3 doesn't support RSA with SHA256 as asymmetric algorithm.
I am using a policy file and there is a need to use this algorithm.
Is there a way to override WS policy behavior and specify this algorithm
somehow?
We are using CXF 2.7.11 and WSS4J v 1.6.x.
Thanks,
Giriraj
Thanks Colm, I changed the namespace to the one you mentioned. Now I am
getting similar error, though the stack trace has the class referring to
200702.
org.apache.cxf.ws.policy.PolicyException: These policy alternatives can not
be satisfied:
I forgot to mention that I am setting ws-security.username and
ws-security.password programmatically onto BindingProvider.
Thanks,
Giriraj
On Feb 24, 2016 11:07 PM, "Giriraj Bhojak" <girira...@gmail.com> wrote:
> Hi,
>
> I have been trying to use UsernameToken WS-Securi
Hi,
I have been trying to use UsernameToken WS-SecurityPolicy assertion, but I
do not see the SOAP headers in the payload.
Hence I keep getting the following exception on the server side:
org.apache.cxf.ws.policy.PolicyException: These policy alternatives can not
be satisfied:
this gateway
address and imports its certificate to your client's truststore. CXF's
SSL configuration page explains how this is done.
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html
regadrs, aki
2015-04-22 3:58 GMT+02:00 Giriraj Bhojak girira...@gmail.com:
Hello,
I would like
Hello,
I would like to know how the proxy specific properties(ProxyServer,
ProxyServerPort and ProxyServerType) of client element of http-conf as per
this link should be used.
I need to call a JAX-WS endpoint that is accessed via proxy over https.
Do I need to import proxy certificate in the
:
TLSClientParameters tslClientParameters = new TLSClientParameters();
tslClientParameters.setSecureSocketProtocol(SSL);
httpConduit.setTlsClientParameters(tslClientParameters);
Regards,
Andrei.
-Original Message-
From: Giriraj Bhojak [mailto:girira...@gmail.com]
Sent: Mittwoch, 30. Juli 2014 19:40
:
http://ashakirin.blogspot.de/2012/09/cxf-performance-on-sun-solaris-platform.html
Regards,
Andrei.
-Original Message-
From: Giriraj Bhojak [mailto:girira...@gmail.com]
Sent: Montag, 28. Juli 2014 18:41
To: users@cxf.apache.org
Subject: Configuring jaxws clients for performance
Hello,
Could anyone recommend settings/properties (for e.g., number of client
connections/connection pool) that would impact the performance of clients
configured for calling an endpoint? I need to ensure that if large number
of endpoints invocation happen for a given jaxws:client, there are no
, 2014 at 11:58 AM, Andrei Shakirin ashaki...@talend.com
wrote:
Hi,
Unrecoverable key usually means that your keystore password is incorrect.
Have you tried to access keystore/truststore using JDK keytool?
Regards,
Andrei.
-Original Message-
From: Giriraj Bhojak [mailto:girira
, Jose María Zaragoza demablo...@gmail.com
wrote:
2014-07-17 0:11 GMT+02:00 Giriraj Bhojak girira...@gmail.com:
Thank you for the quick response.
Could you point me to an example of using JAXWS proxy-client's factory?
Did you mean org.apache.cxf.jaxws.JaxWsProxyFactoryBean class?
Yes
, Giriraj Bhojak girira...@gmail.com wrote:
I did try that. I must have goofed up with the passwords. But it's working
now.
But I need to understand something. The entry looks something like this:
sec:keyManagers keyPassword=keyPassword
sec:keyStore file=.keystore
My apologies. Please ignore my earlier reply. I sent the response to the
wrong mail thread.
Thanks a lot Jose, I was able to use factoryBean to achieve the desired
result.
Thanks,
Giriraj.
On Thu, Jul 17, 2014 at 6:28 PM, Giriraj Bhojak girira...@gmail.com wrote:
I just found out that if I
Hello,
I have used Spring based configuration to define a jaxws client.
The spring bean looks something on following lines:
jaxws:client id=id
serviceClass=SomeClass address=someAddress
jaxws:inInterceptors
ref bean=inInterceptor /
bean
:00 Giriraj Bhojak girira...@gmail.com:
Hello,
I have used Spring based configuration to define a jaxws client.
The spring bean looks something on following lines:
jaxws:client id=id
serviceClass=SomeClass address=someAddress
jaxws:inInterceptors
ref
.
-Original Message-
From: Giriraj Bhojak [mailto:girira...@gmail.com]
Sent: Freitag, 11. Juli 2014 22:16
To: users@cxf.apache.org
Subject: Supplying passwords for key manager and trust manager to
http:conduit
Hello all,
I am using http-conduit for SSL support in CXF 2.7.11
Hello all,
I am using http-conduit for SSL support in CXF 2.7.11.
Is there a way I can specify a password callback for sec:keyManagers and
sec:trustManagers?
Thanks,
Giriraj.
Message-
From: Giriraj Bhojak [mailto:girira...@gmail.com]
Sent: Thursday, July 10, 2014 5:36 AM
To: users@cxf.apache.org
Subject: Using SSL with CXF web service
Hello,
I have setup a CXF endpoint on Tomcat. I have enabled SSL on tomcat.
I am able to access the deployed webservice using
anyone please help me out with this?
I can't figure out what SSL handshake fails.
Thanks,
Giriraj.
On Thu, Jul 10, 2014 at 9:39 AM, Giriraj Bhojak girira...@gmail.com wrote:
Hi Xilai,
Thank you for the reply. I did check the passwords and they were correct.
It turns out that the keystore
Hello,
I have setup a CXF endpoint on Tomcat. I have enabled SSL on tomcat.
I am able to access the deployed webservice using
http://localhost:8080/webapp/services/one.
When I use the SSL port(https://localhost:8443/webapp/services/one) and try
accessing the same webservice thru my java program,
the
XMLStreamReader from the message, wrapper it with a new stream reader that
would then record the read events. (the wrapped stream reader method
would also work for 2.7.x, but like I said, a bit more complex to write)
Dan
On May 12, 2014, at 6:05 PM, Giriraj Bhojak girira...@gmail.com wrote:
Hi
Hi,
I am using cxf (2.7.8 )with wss4j(1.6.13).
For the sake of debugging I need to see the outgoing messages.
I have added cxf:inInterceptors and cxf:outInterceptors in the spring
config.
This helps me see the signed and encrypted message.
Is there a way to see the clear-text version of the
, but encrypting passwords
in keystores is supported out of the box in WSS4J 2.0 and CXF 3.0.0.
Follow Colm's blog for details:
http://coheigea.blogspot.de/2014/02/apache-wss4j-200-part-iv.html
Regards,
Andrei.
-Original Message-
From: Giriraj Bhojak [mailto:girira...@gmail.com]
Sent
Hello,
I am running into a problem if I extend the
org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor via spring beans.
I have a bean definition defined as(haven't shown complete bean
definition) :
bean class=org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor
id=interceptor
me figure out what's wrong?
Thanks,
Giriraj.
On Thu, Apr 24, 2014 at 2:17 PM, Colm O hEigeartaigh cohei...@apache.orgwrote:
I don't quite follow. Could you paste your entire spring config please?
Colm.
On Thu, Apr 24, 2014 at 7:08 PM, Giriraj Bhojak girira...@gmail.com
wrote:
Hello
ok.
Colm.
On Thu, Apr 24, 2014 at 7:35 PM, Giriraj Bhojak girira...@gmail.com
wrote:
Here is the working config:
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=
http://cxf.apache.org/jaxws
BSP compliance is enabled by default.
I debugged a lot and identified BSP specific attributes/namespaces being
added to KeyInfo element. So the signature was actually invalid.
Disabling BSP compliance did the trick for me, for now. I may have to find
another alternative in future.
Hope this helps
Hello,
I have a cxf client deployed under a web-module A on WAS 8.5 with versions
as cxf 2.7.8 and a wss4j 1.6.13.
The service provider B is on Tomcat with similar configuration.
I had to set the class loader policy for web project to parent last and I
also disabled Websphere's JAXWS engine.
I
Hello,
I am pretty sure someone must have faced this issue earlier.
I have a cxf client deployed under a web-module A on WAS 8.5 with versions
as cxf 2.7.8 and a wss4j 1.6.13.
The service provider B is on Tomcat with similar configuration.
I had to set the class loader policy for web project to
41 matches
Mail list logo
