Re: Bind CXFNonSpringServlet to another webcontext in OSGi

Hi Sergey, Thank you for your answer, I will check it out. Greetings Peter Am 10.01.2013 18:41, schrieb Sergey Beryozkin: Hi Peter See comments in the end On 10/01/13 17:12, Peter Schyma wrote: Hi, I am trying to realize the following scenario: 1. Have one bundle (WC) initialize a web

Re: SSL with DOSGi

Hi On 11/01/13 01:16, geecxf wrote: Hi Sergey, I got it to work! I almost can't believe that it does but I'm staring at the HTTPS response page as I'm typing this email. Thank you for pointing in me in the right direction. Sorry I did not answer yesterday, I had some vague idea that having

Re: Timing issue with WS-Security

Here are two possible explanations for this error message: 1) The Created time of the Timestamp was more than 5 minutes ago. This is rejected by default as it is considered stale. You can change this default via the JAX-WS property ws-security.timestamp.timeToLive (which takes a value in

Re: Configuring CXF to work with WS-Security

Hi Mike, Turn logging to DEBUG and see what the reason for the WSSecurityException was. Colm. On Thu, Jan 10, 2013 at 9:14 PM, Mike Thomsen mikerthom...@gmail.comwrote: I'm still fairly new to CXF and Java web services, so please bear with me. The service I am calling expects a WS-Security

Re: socket closed error in JAX-RS client?

On 11/01/13 00:33, Benson Margulies wrote: I have a relatively simple unit test that works fine on 9 out of 10 of the systems we run it on. On System #10, (CentOS 4.8), the client gets a Socket Closed exception trying to write the request to the server. Does this suggest anything to anyone?

RE: Sending lists of abstract types using JSON: is @JsonTypeInfo recommended way?

Thanks, Sergei. It works fine with CXF JSON provider and jaxbElementClassNames! Cheers, Andrei. -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: Donnerstag, 10. Januar 2013 12:30 To: users@cxf.apache.org Subject: Re: Sending lists of abstract types

Re: Configuring CXF to work with WS-Security

I turned on debugging at the log4j root logger and saw this: 07:06:22,754 DEBUG UsernameTokenProcessor:49 - Found UsernameToken list element 07:06:22,754 DEBUG UsernameTokenValidator:78 - UsernameToken user Mike 07:06:22,754 DEBUG UsernameTokenValidator:79 - UsernameToken password type null

Re: Timing issue with WS-Security

Thanks for you reply , client requrest includes timestamp so every request sent by client will contain timestamp , on server side ws security checks this timestamp if its either case A (5 minutes ago) or B (more than 60 seconds in the future) it rejects. Client gets its time from

Re: Timing issue with WS-Security

Client gets its time from client machine and server gets its time from server machine, what it both are in different timezone? The time is sent in UTC format, so timezone doesn't matter. my server is maintained by third party , I know the client which is mine the time is correct but

Re: Configuring CXF to work with WS-Security

Try using the action configuration: entry key=action value=UsernameTokenNoPassword Timestamp/ Colm. On Fri, Jan 11, 2013 at 12:35 PM, Mike Thomsen mikerthom...@gmail.comwrote: I turned on debugging at the log4j root logger and saw this: 07:06:22,754 DEBUG UsernameTokenProcessor:49 - Found

CXF client to support multi-user

Hi, I am using CXF client to connect to Exchange WebService, and I need to support multiple users in the runtime. I did something like this: …. JaxWsProxyfactoryBean factory1 = new JaxWsProxyfactoryBean(); factory1.setServiceClass(exchangeServicePortType.class);

Re: Bind CXFNonSpringServlet to another webcontext in OSGi

I found another solution which seems to work - except of one small issue. Instead of looking up the CXF bus, I expose now the DestinationRegistry configuration feature as OSGi Service, do the lookup for this feature and configure in each bundle a CXF bus using the shared DestinationRegistry.

Re: CXF port thread safety question

Hi Dan, Thanks for the response. I followed your suggestions, but unfortunately, I'm still getting the issue. I've digged a little deeper as to what is going on, and it looks to me that the Exchange reference in the ClientImpl is getting clobbered by the threads. So in the

Re: SSL with DOSGi

Hi Sergey, After stepping through the code here is my understanding of how this works (I am writing it down for posterity). The SpringBus bean instantiated via Spring DM sets the default bus in BusFactory. SpringBus extends ExtensionManagerBus which in turn extends CXFBusImpl. The

Re: Configuring CXF to work with WS-Security

Thanks! That seemed to work. Sent from my iPhone On Jan 11, 2013, at 9:51 AM, Colm O hEigeartaigh cohei...@apache.org wrote: Try using the action configuration: entry key=action value=UsernameTokenNoPassword Timestamp/ Colm. On Fri, Jan 11, 2013 at 12:35 PM, Mike Thomsen

Re: Java First generated WSDL - Can I force XSD's to be imported rather than Inlined?

This could be a solution to my problem, below. We are using Java first approach with Spring and CXF. We use Aegis Data Binding with Simple Front-end configured in Spring. We have several services in our application. Each service WSDL generated at runtime has inlined schema (data types)