Continuations status?

Hi, What is the status of CXF continuations and where do I find the best documentation on how to use it? Is the support for continuations usable for production? I see some mentionings of beta status etc but that might be outdated? Also, I tried to look for documentation how to use it but the

Troubles with ContinuationProvider

Hello, I'm trying to use Continuation API in my CXF based restful webservice. Every time I want to access ContinuationProvider - I receive null: ContinuationProvider provider = (ContinuationProvider)context.get(ContinuationProvider.class.getName()); Continuation c = provider.getContinuation();

Re: Continuations status?

Also, another question: How do I get the Context without injection? We are currently not running our service in Spring, so we need to get the Context some other way... On 18 October 2011 09:05, Kent Närling kent.narl...@seamless.se wrote: Hi, What is the status of CXF continuations and

CXF JAXB service getting confused with package names

Hi, I have written a simple CXF webservice with Spring using the default JAXB bindings. It takes an email address - for example t...@abc.com.au The classes I use also use package names as au.com.abc as usual practice. If the email ends with abc.com.au I get the following error when the CXF

Re: Continuations status?

Hi As far as I'm aware CXF continuations are used in the Camel and ServiceMix integration layers. I haven't heard users explicitly using continuations in their own applications but the continuations support has definitely been improved over the last couple of years, I think it's very much

Re: Continuations status?

Hi, On 18/10/11 08:51, Kent Närling wrote: Also, another question: How do I get the Context without injection? We are currently not running our service in Spring, so we need to get the Context some other way... I'm presuming you are referring to JAX-WS WebServiceContext, given that you

Re: Continuations status?

Hi, thanks for the quick answer, however: On 18 October 2011 12:52, Sergey Beryozkin sberyoz...@gmail.com wrote: Hi, On 18/10/11 08:51, Kent Närling wrote: Also, another question: How do I get the Context without injection? We are currently not running our service in Spring, so we need

Re: Continuations status?

Hmmm... what you are doing should work. As an easy workaround, you can always call PhaseInterceptorChain.getCurrentMessage() to get the current CXF Message and pull values from there. You would need to use the CXF Message.* keys and not the JAX-WS keys. If you want to stick with

Question about XML payload

All: I have a web service that must send a single XML string as its only payload. Is there anything special about this case? Or can I treat it just as any other string? Thanks! David Sills

Re: Continuations status?

On 18 October 2011 13:32, Daniel Kulp dk...@apache.org wrote: Hmmm... what you are doing should work. As an easy workaround, you can always call PhaseInterceptorChain.getCurrentMessage() to get the current CXF Message and pull values from there. You would need to use the CXF Message.*

Re: Continuations status?

On Tuesday, October 18, 2011 9:05:48 AM Kent Närling wrote: Hi, What is the status of CXF continuations and where do I find the best documentation on how to use it? Is the support for continuations usable for production? I see some mentionings of beta status etc but that might be

Dynamic Concurrency changes on JMS

I would like to be able to change the concurrency settings of my JMS endpoint at runtime (concurrentConsumers, maxConcurrentConsumers, maxConcurrentTasks). Will changing the properties on the JMSConfiguration object effect its changes successfully at runtime? Or must these be changed only at

Re: Troubles with ContinuationProvider

Hi On 18/10/11 08:09, Mateusz Herych wrote: Hello, I'm trying to use Continuation API in my CXF based restful webservice. Every time I want to access ContinuationProvider - I receive null: ContinuationProvider provider = (ContinuationProvider)context.get(ContinuationProvider.class.getName());

HTTPS client configuration using JaxWsProxyFactoryBean

All: Is it possible to configure the JaxWsProxyFactoryBean to use HTTPS? It looks as though it should be, but I can't quite figure out how to connect up the bits. I have added this to the Spring configuration file: http:conduit

Re: CXF JAXB service getting confused with package names

What is the error message you're getting -- you apparently forgot to include it below. What is the data type of an email address -- does its Schema prevent two dots after the @ symbol? Also, is the problem that the email address abc.com.au in particular is failing or that *any*

Re: HTTPS client configuration using JaxWsProxyFactoryBean

I think if you add a factory.setEndpointName() call to the appropriate qname used in the http:conduit, it should work. Alternatively, if you setup the address on the factory prior to calling create (factory.setAddress(...)), you can configure the http conduit via something like:

Re: Troubles with ContinuationProvider

2011/10/18 Sergey Beryozkin sberyoz...@gmail.com: Hi On 18/10/11 08:09, Mateusz Herych wrote: Hello, I'm trying to use Continuation API in my CXF based restful webservice. Every time I want to access ContinuationProvider - I receive null: ContinuationProvider provider =

CXF is seeing my implementor class as the SEI

I've been developing a code-first WebService with CXF, version 2.4.3; following the guidelines at http://cxf.apache.org/docs/developing-a-service.html#DevelopingaService-Writingtheinterface My SEI interface is: /@WebService( name=ProvisioningOrderService, serviceName=ProvisioningOrderService,

Re: SecureConversationInInterceptor removing all assertions

There definitely looks like a bug in here someplace, but I'm not 100% sure where or the cause. It definitely needs to replace the Assertion map (since the policy may be very different), but it likely should go through the old map and re-assert any policies on the new map that were asserted

Re: CXF is seeing my implementor class as the SEI

No, this is correct. The SEI represents the portType in the WSDL, not the Service. Thus, attributes that are specific to the Service are not allowed on the SEI. That would include the serviceName and portName attributes. Those would go on the @WebService annotation on the impl itself

Re: Dynamic Concurrency changes on JMS

On Tuesday, October 18, 2011 9:43:26 AM Jared S Warren wrote: I would like to be able to change the concurrency settings of my JMS endpoint at runtime (concurrentConsumers, maxConcurrentConsumers, maxConcurrentTasks). Will changing the properties on the JMSConfiguration object effect its

Re: Confusing error message Problem writing SAAJ model to stream in case if service not avalable

On Tuesday, October 18, 2011 10:58:09 AM Andrei Shakirin wrote: Hi, Just to be sure that proposed improvement makes sense and has no drawbacks. use case: Dispatch client sends stream message to remote Web Service using following code: final DispatchStaxSource dispatch =

Re: Wsdl2Java. Wrapper style mapping bug?

Well, the Coaches2Names operation doesn't meet the requirements for unwrapping. The name of the request element must match the operation name (it doesn't, it's Coaches2) and the response should be the operation name + Response.That is why it's not unwrapping. Dan On Sunday, October

Re: CXF is seeing my implementor class as the SEI

Thanks Daniel, I just noticed that myself - I should not have had the serviceName attribute on the interface. However, I'm still seeing some strangeness Here is my (modified) interface: /@WebService( name=ProvisioningOrderService,

Adding WS-Addressing From to SOAP header

Hello, I would like to request some help about how to add a From header to a SOAP message. I have created an interceptor inheriting from AbstractSoapInterceptor. In the handleMessage method I check if the message is outgoing, and if it is, I try to add a new header. In order to create the

mismatch for port 443, even with interceptors in cxf.xml

Hello, I'm deploying a cxf web service outside of the application server container. I know it's not the best way, but it does work with http. I added In and Out interceptors that use the encrypt/decrypt and sign property files. It looks like I still need to add something to deploy the web

Re: Troubles with ContinuationProvider

Yes, problem I mentioned in my first post was caused by no async support in web.xml. I added this line: async-supportedtrue/async-supported And everything worked well, almost... Now ContinuationProvider.getContinuation() return null after resuming the request (not always, but in ~95% of cases).

RE: Dynamic Concurrency changes on JMS

Spring JMS definitely allows it (I'm actually doing this on some other queues that aren't served by CXF in the exact same process). Any quick pointers for how I wire in a different MessageListenerContainer? (All of my others are using DefaultMessageListenerContainer and it meets all my needs in

Re: CXF JAXB service getting confused with package names

Good call - on closer inspection some search methods map to the proper JAXB objects and others dont map directly to them - i will add the proper mapping - the suffix of the email was irrelevant. Thanks for you time. -- View this message in context:

Re: How to set soapAction header in Dispatch API?

Thanks Dan. The newer version worked for me. I have another question. I want to use a single instance of dispatcherSoapMessage object per end point in a multi-threaded application, is cxf dispatcher implementation thread-safe? Thanks. -- View this message in context:

RE: Enum as one of the query params in wadl

Hey Sergey, I added a comment on this bug as it still doesn't be fully working for me. It is working for PathParam now, but still isn't working for QueryParam. Thanks, Jason -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: Friday, August 26, 2011 3:38

Re: mismatch for port 443, even with interceptors in cxf.xml

On 2011-10-19, at 上午5:08, nkunkov wrote: Hello, I'm deploying a cxf web service outside of the application server container. I know it's not the best way, but it does work with http. I added In and Out interceptors that use the encrypt/decrypt and sign property files. It looks like I

Re: mismatch for port 443, even with interceptors in cxf.xml

Hi thanks a lot for your answer but I need to use https protocol with ws-security.. I feel I miss some jetty configuration. Any help is very much appreciated! Nadia On Oct 18, 2011, at 9:15 PM, Freeman-2 [via CXF] ml-node+s547215n491600...@n5.nabble.com wrote: On 2011-10-19, at 上午5:08,

Re: mismatch for port 443, even with interceptors in cxf.xml

Hi, Yeah, in this case you need something like httpj:engine-factory bus=cxf httpj:engine port=443 httpj:tlsServerParameters sec:keyManagers keyPassword=password sec:keyStore type=JKS password=password file=certs/cherry.jks/ /sec:keyManagers

Re: mismatch for port 443, even with interceptors in cxf.xml

Freeman, Thanks so much! That solved the problem with https error It looks like the server is being deployed but something is still wrong - can't get the WSDL... In the log I see the following: Oct 18, 2011 10:55:57 PM org.apache.cxf.service.factory.ReflectionServiceFactoryBean

Re: mismatch for port 443, even with interceptors in cxf.xml

Hi, I think this is expected behavior, your browser need some configuration to trust the host with https. Take a look at similar discussion[1] [1]http://cxf.547215.n5.nabble.com/SSL-example-breaks-firefox-no-cipher-suites-in-common-td3340625.html Freeman On 2011-10-19, at 上午11:05,