Re: Version 1 NewCookie is not compliant with RFC 2109

Looking at org.apache.cxf.jaxrs.impl.NewCookieHeaderProvider.toString() it seems CXF does not have check about the cookie version. So if we have special character which is only allowed in version 1 cookie, there will be an issue. +1 for this change. Iris Ding -- View this message in context

Re: What dataType in Dispatch API should I use to gain best performance?

consuming operation while supporting soapHandler? Thanks & Best Regards, Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/What-dataType-in-Dispatch-API-should-I-use-to-gain-best-performance-tp5759221p5759772.html Sent from the cxf-dev mailing list archive at Nabble.com.

What dataType in Dispatch API should I use to gain best performance?

y bad. Do you know what dataType is suggested to gain best performance when using the Dispatch API? Or is there any CXF internal dataType that can be used to gain best performance? Thanks & Best Regards, Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/What-da

Re: Performance Enhancement for CXF jaxrs

Hi Sergy, How about using: message.get(Message.BASE_PATH) + ":" + rawPath + ":" + httpMethod + ":" + requestContentType + ":" + acceptTypes; I have a proposed solution for this and will open a jira for this. Let's discuss the implementation deta

Performance Enhancement for CXF jaxrs

subsequent request. Provider matching is under the same situation as well. We can provide a cache for matched provider to save effort. What do you think of this problem? Can we add such support in CXF? Thanks & Best Regards, Iris Ding -- View this message in context: http://cxf.54721

Re: MessageBodyReader and MessageBodyWritter should follow different sorting rule

Thanks Sergey, I confirmed in lastes CXF code, this has arleady been fixed. -- View this message in context: http://cxf.547215.n5.nabble.com/MessageBodyReader-and-MessageBodyWritter-should-follow-different-sorting-rule-tp5757415p5757483.html Sent from the cxf-dev mailing list archive at Nabble.

MessageBodyReader and MessageBodyWritter should follow different sorting rule

380. We can get this fixed to adjust the MessageBodyReader sorting rule. I have opened an JIRA: https://issues.apache.org/jira/browse/CXF-6412 and provide a fix for this probllem. Can you help review it and give your comments? Thanks & Best Regards, Iris Ding -- View this message in context

Re: atom support in CXF

Thanks Sergey for the reply. It is good news that these providers are put into other modules just because better modularization. We can be more sure to put them in :) -- View this message in context: http://cxf.547215.n5.nabble.com/atom-support-in-CXF-tp5757256p5757260.html Sent from the cx

atom support in CXF

& Best Regards, Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/atom-support-in-CXF-tp5757256.html Sent from the cxf-dev mailing list archive at Nabble.com.

CompletionCallback can not get the Throwable if error occurs in other interceptor (no serviceinvokerInterceptor)

ook at this problem? https://issues.apache.org/jira/browse/CXF-6373 Thanks & Best Regards, Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/CompletionCallback-can-not-get-the-Throwable-if-error-occurs-in-other-interceptor-no-serviceinvokerI-tp5756543.html Sent from t

Re: NPE when calling ServiceUnavailableException.getRetryTime()

Thanks a lot Sergey for taking care of this issue! Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/NPE-when-calling-ServiceUnavailableException-getRetryTime-tp5756231p5756318.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: NPE when calling ServiceUnavailableException.getRetryTime()

eHeaderProvider to handle Date type. I do not think NPE here is correct. If so, does it mean we do not support this API( ServiceUnavailableException.getRetryTime()) call at all? Thanks & Best Regards, Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.c

NPE when calling ServiceUnavailableException.getRetryTime()

. Can you please take a look at the problem? Thanks a lot! Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/NPE-when-calling-ServiceUnavailableException-getRetryTime-tp5756231.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: ContainerResponseContext.getLinks() lose links

Thanks Sergey for taking care of this issue. In my test, I just use below two links: http://localhost:9080//rest/resource/getlinks html://localhost:8080/nohttp Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/ContainerResponseContext-getLinks-lose-links

ContainerResponseContext.getLinks() lose links

below javadoc for Link: getRel() Returns the value associated with the link rel param, or null if this param is not specified. Can you please take a look at the problem? I have already created a jira https://issues.apache.org/jira/browse/CXF-6352 for it and attached a proposed fix. Thanks a lot! Iris

CXF fails to find a correct MessageBodyWritter for List if Resource method is defined under async way

kList.add(b1); bookList.add(b2); } } I have opened CXF-6001 for this issue and uploaded a proposed fix. Looking forward to your comments! Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-fails-to-find-a-correct-MessageBodyWritter-for-List-E-if-Resource-method-is-defined-under-async-y-tp5748709.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: Throw Error in ExceptionMapper

Thanks Sergey, cxf-5943 is opened to track this and a patch is uploaded. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/Throw-Error-in-ExceptionMapper-tp5747662p5747748.html Sent from the cxf-dev mailing list archive at Nabble.com.

Throw Error in ExceptionMapper

is problem? Thanks. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/Throw-Error-in-ExceptionMapper-tp5747662.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: @context injection through setter method - method name restriction

Sergey, Thanks. I am willing to contribute I will start to work in the ClassCastException soon. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5747118.html Sent from the cxf-dev mailing

Re: @context injection through setter method - method name restriction

Thanks a lot Sergey. Will fix #1 in cxf-5897. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746890.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: @context injection through setter method - method name restriction

I think we can make it follow below two rules: 1. If the parameterType is not an Interface, just ignore the method. 2. Scan available providers to make sure there is one provider who can deal with the parametertype, otherwise, just ignore it as well. any thoughts? Iris Ding -- View this

Re: @context injection through setter method - method name restriction

Sergey, I mean if we want to support parameter type(custom context) in setter method other than those specified in spec, we can not add check about parameter type. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name

Re: @context injection through setter method - method name restriction

OK, Then Sergey if we want to allow custom context we need support it via another way.. -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746802.html Sent from the cxf-dev mailing list archive at Nabble.c

Re: @context injection through setter method - method name restriction

it. any thoughts? Have CXF already supported all above types now? Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746796.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: @context injection through setter method - method name restriction

Thanks Andrei and Sergey. An issue is opened to track this: https://issues.apache.org/jira/browse/CXF-5897 -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746781.html Sent from the cxf-dev mailing lis

@context injection through setter method - method name restriction

Info HttpHeaders Request SecurityContext What do you think about this problem? Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

Thanks Sergey. Let's keep an eye on what is going on for the JAXRS SPEC clarification. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/two-issues-in-org-apache-cxf-jaxrs-provider-DataSourceProvider-tp5745783p5745974.html Sent from the cxf-dev mailing list archi

Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

Thanks Sergey for your fix for this issue. But actually I have a question for the fix as it is against spec for support of subclasses or concrete implementations for DataSource. I have put my question in https://issues.apache.org/jira/browse/CXF-5835 as well. The other question is: In ProviderFa

Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

Thanks Daniel for digging out the issue. So how about below change to convert the ClassCastException to a 415 response? public T readFrom(Class cls, Type genericType, Annotation[] annotations, MediaType type, MultivaluedMap heade

Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

original incomming InputStream, Users will loose control of it. He might need to use specific API to operate the different stream. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/two-issues-in-org-apache-cxf-jaxrs-provider-DataSourceProvider-tp5745783p5745788.html Sent

Re: two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

used. In such case, if we return directly the original InputStream, users will loose control of the behaviour the returned InputStream. what do you think about this point? Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/two-issues-in-org-apache-cxf-jaxrs-provider

two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider

Hi Guys, I think There are two issues in org.apache.cxf.jaxrs.provider.DataSourceProvider: Issue 1: ClassCastException if you post a FileDataSource in your resource class: Issue 2: Return the original InputStream directly in InputStreamDataSource.getInputStream(). I have created a JIRA in http

Why only modify SOAPMessage in Inbound when setPayload in JAXWS logicalHandler?

Hi Guys, In setPayload(Source s) method of org.apache.cxf.jaxws.handler.logical.LogicalMessageImpl.java, we will set SOAPMessage directly in Inbound as below: SOAPMessage m = message.getContent(SOAPMessage.class); if (m != null && !MessageUtils.isOutbound(message)) { try {

Re: extensions dynamically added/removed from exited bus

Thanks a lot, Daniel! -- View this message in context: http://cxf.547215.n5.nabble.com/extensions-dynamically-added-removed-from-exited-bus-tp5730582p5732472.html Sent from the cxf-dev mailing list archive at Nabble.com.

Re: extensions dynamically added/removed from exited bus

e the bus, Is this understanding right? Many Thanks! Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/extensions-dynamically-added-removed-from-exited-bus-tp5730582p5731571.html Sent from the cxf-dev mailing list archive at Nabble.com.

extensions dynamically added/removed from exited bus

cxf jar, eg: the 5th cxf jar. In this scenario, we need to remove the extensions defined in the 5yh cxf jar from the existed bus. But I can not find a suitable way to do this. Can somebody please shed some lights on this? Many Thanks! Iris Ding -- View this message in context: http://cxf

Re: Outsource WSDL/XSD jax-ws-catalog

You can put jax-ws-catalog.xml under META-INF within your application. So that CXF will recognize it and use it. Details you can find in org.apache.cxf.catalog.OASISCatalogManager.java. Iris Ding -- View this message in context: http://cxf.547215.n5.nabble.com/Outsource-WSDL-XSD-jax-ws