Re: JAX-RS : initial WADL support

Hi Sergey, Given he following: @WebService(name=MyService, targetNamespace=http://some.domain.com/;) @SOAPBinding(use=Use.LITERAL, style=Style.RPC) @Consumes(text/xml) @Produces(text/xml) @Path(/) public interface MyService { @GET @Path(/search/) @WebMethod

Re: JAX-RS : initial WADL support

Hi Gabo Hi Sergey, Given he following: @WebService(name=MyService, targetNamespace=http://some.domain.com/;) @SOAPBinding(use=Use.LITERAL, style=Style.RPC) @Consumes(text/xml) @Produces(text/xml) @Path(/) public interface MyService { @GET @Path(/search/) @WebMethod

Re: [CXF-2.2.5][Java1.5] Define namespace by configuration

Hi, Is it JAXRS or JAXWS ? I think you can probably rely on the custom XMLStreamReaders/Writers to translate between diff namespaces. If it is JAXRS then you might also want to try to configure a JAXBElementProvider, starting from 2.2.5, ex, say you need to have {http://bar}bar converted into

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

Hi, If you're referring to the fact that you can not use say a JAXRS QueryParam(principal.password) then yes, it's a bug which will be fixed shortly...At the moment only the values are decoded (by default). Assuming it is the case, the workaround is to register a custom RequestFilter which

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

Thanks Sergey, Could you tell how to register a custom requestFilter - I have not done that yet.. Sergey Beryozkin-2 wrote: Hi, If you're referring to the fact that you can not use say a JAXRS QueryParam(principal.password) then yes, it's a bug which will be fixed shortly...At the

MTOM producer - different content-id in XOP:Include and MIME part for the same attachment?

Hi List, we are using in a camel route a cxf producer (client) enpoint with MTOM enabled. The consumer (server) at the moment is a 'black box' sitting in our customer's environment. The issue: following to an (apparently) valid request from our CXF client, the server replies with a SOAP fault:

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

It looks to me that there are two places at least where this needs to be fixed: 1. the JAXRSUtils line 926 - the key needs to be decoded currently: queries.add(values[0], value); fix would be: queries.add(HttpUtils.urlDecode(values[0]), value); 2. Somewhere in the JAXRS UNMARSHAL phase we

Missing Prefix

Hi I need to connect to a third party web service using addressing 2004/08. The soap xml which would work perfectly needs to look as below but certain prefixes are missing which makes the server reject it. The missing prefixes are ns1 from ns1:SectorCode and all wsa prefixes like wsa:Action.

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

It looks to me that there are two places at least where this needs to be fixed: 1. the JAXRSUtils line 926 - the key needs to be decoded currently: queries.add(values[0], value); fix would be: queries.add(HttpUtils.urlDecode(values[0]), value); Yes, fixed on mainline 2. Somewhere in the

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

Ok taking care of the Form params with CustomFormEncodingProvider by stepping on the populateMap. public class CustomFormEncodingProvider extends FormEncodingProvider Trying this now.. The queryHandler is less clear which base class to use for a provider, could you tell which one handles it by

Re: Adobe Flex HTTPService escapes dot with %2e breaking CXF logic on the server

Ok taking care of the Form params with CustomFormEncodingProvider by stepping on the populateMap. public class CustomFormEncodingProvider extends FormEncodingProvider Trying this now.. The queryHandler is less clear which base class to use for a provider, could you tell which one handles it

Re: Missing Prefix

Is there any way you can attach a small testcase that demonstrates this? I haven't seen a case where the prefixes are missing yet. It's probably due to an old version of xerces or other dependency causing some wacky behavior. Maybe a stax version. Not really sure though. I'd need a

Re: ClientTransportException and ServerSideException

On Thu December 10 2009 12:09:27 pm kiffin wrote: I am porting a Metro JAXWS application to CXF. There are two exceptions in the code not available in CXF. Do we have the equivalent for ClientTransportException and ServerException in CXF? For the ClientTransportException, it's pretty much

CXF REST nested bean initialization in the POST x-www-form-urlencoded

I've ran into some small gotcha with my java bean parameter. It has simple bean nested inside as a member,which works fine if I execute GET request with params on the url, for examle: /login?principal.username=dude Here is my GET entry point: On the top of the impl I have: @Consumes({text/xml,

Re: [CXF-2.2.5][Java1.5] Define namespace by configuration

Hi Sergey, Thanks for the update, but if I understood the class property correctly, this only allows one to use the other but does not necessary replace. Also, it does not seem to affect the wadl generated. I added the following: bean class=org.apache.cxf.jaxrs.provider.JAXBElementProvider

[DOSGI] ServiceListener without objectClass

Hi all, I am trying to use a service listener that handles all imported interfaces, without knowing what the actual interface is. To do this, I created a service listener with the following filter: (service.imported=true). But this doesn't work. In the CxfFindListenerHook there is a check to see