RE: Selecting default media type [...@producemime]

Thanks for the reply Sergey. I'm currently using CXF 2.1.3 As u said, filters can be one of my solutions. (And i'll try that out.) However, I'm looking for a more direct way to set my default provider. Does CXF (2.1.3) has no support for doing this? Sergey Beryozkin-2 wrote: > > Or you can try

JAX-WS and Simple Frontend CXF for webservices - WSDL interop compliant? use with .NET? what about JSON (with vraptor.org)?

http://cwiki.apache.org/CXF20DOC/simple-frontend.html http://cwiki.apache.org/CXF20DOC/jax-ws.html In the "code first" model where the above two CXF approaches dynamically produce the WSDL on deployment, is the WSDL .NET and interop compliant? ie: Can I hit the ?WSDL URL with .NET and get WSDL t

Re: [JAX-RS] Fault handling

Hi Sergey, Is it possible to specify a custom provider from an ExceptionMapper implementation? Or maybe a work around to remove the tags? I was hoping to avoid the chain-abort work-around. Again, my thanks. Gabo Sergey Beryozkin wrote: Hi Gabo Many thanks for creating the JIRAs. Exception

Re: @XmlSchema(location=...)

Dan is too polite, or lazy, to write, "Benson was completely confused to suggest that the current behavior is intended. The behavior you asked for is intended." But please be sure to read that into his reply. On Tue, Feb 17, 2009 at 10:50 AM, Daniel Kulp wrote: > > Definitely log a bug for this

chunking

Hello, I have a problem that occurs when chunking is turned on. I turned it off and tested it in eclipse, and the error went away. However when I deploy it to Tomcat the error returns. Is there a way I can tell if chunking is actually turned off? I turned on logging in the cxf.xml file and got th

Re: D-OSGi question

Hi Thomas, Yeah that exception is a known issue. Its filed as https://issues.apache.org/jira/browse/CXF-2028 but the system should still work when not using security. On the missing org.apache.servicemix.specs.locator bundle. I'm definitely seeing it in the multibundle.zip [1] but the bundle name

Re: @XmlSchema(location=...)

Definitely log a bug for this (and provide a test case if possible). If you would like to start digging into it, I can point out some places to start your investigation: JAXBDataBinding - in the generateJaxbSchemas() method, put a breakpoint or println or something in the createOutput() method

RE: Selecting default media type [...@producemime]

Or you can try to use _type=xml query if possible, or write RequestFilter which will check if it's */* and if yes then replace Message Accept value with application/xml Cheers, Sergey -Original Message- From: Sergey Beryozkin [mailto:sbery...@progress.com] Sent: 17 February 2009 14:33 To

RE: Selecting default media type [...@producemime]

Hi In CXF 2.1.3 JAXB provider is considered less specific as it has no explicit ProduceMime/ConsumeMime values. In 2.1.4 you can explicitly register JAXB provider (org.apache.cxf.jaxrs.provider.JAXBElementprovider) and this will ensure that Accept:*/* is mapped to JAXB... Cheers, Sergey -Or

Selecting default media type [...@producemime]

Hi, I have two methods in the resource class having @ProduceMime("application/json") & @ProduceMime("application/xml") Any incoming request with header - Accept:*/* is being mapped to json by default. However, I require it to be xml. Anyway, I can do that? I tried using @ProduceMime("*/*") on th

RE: [JAX-RS] Fault handling

Hi Gabo Many thanks for creating the JIRAs. ExceptionMappers are not CXF interceptors, they can be categorized as JAXRS providers only. I'm still unclear at all as to where such Result tags may come from - needs to be investigated indeed. It looks like text_plain responses are wrapped ? Cheers,

Re: [JAX-RS] Fault handling

Hi Sergey, Thanks for the update. If you could create a JIRA and attach a sample interceptor and a sample service class then it would help a lot and ensure the issue is tracked. https://issues.apache.org/jira/browse/CXF-2045 - this is for the headers being lost https://issues.apache.org/jira

RE: [JAX-RS] Fault handling

Hi Gabo So it does look like Result prefixes are added by the outbound chain somewhere. I'm sorry I didn't investigate the issue with custom headers being lost when added in a CXF out interceptor - but now that you posted some code in the other email I will try to reproduce the problem. If you

Re: [JAX-RS] Fault handling

Hi Sergey, I have replaced the CXFInterceptor with a ResponseHandler implementation. So no chain-abort now. Body of the handleResponse is as follows: MultivaluedMap map = response.getMetadata(); map.add("Authentication-Info", "nextnonce=\""+RestHandlerUtility.generateNonce(base

complextype duplicated in wsdl

Hi all I'm newbie using cxf and webservices. So I apologize if I use not right terms. I defined my webservices using annotations. I created also interfaces used by my webservice. When I create my war and I see in my browser, all wsdls show me complextype as follow ... The problem is th

Re: [OutInterceptor][HttpHeader] Adding Authorization-Info entry to http header

Hi Sergey, > so I'll try to write one and see what happens. Sorry for the late reply. I tried this again with the recent snapshot and the headers are still lost unless I abort the interceptor chain. The implementation I have extends AbstractPhaseInterceptor. Phase is at Phase.POST_PROTOCOL.

SV: CXF / JAXB "Java first approach" - remove minOccurs="0"

Hi, I am also interested in removing minOccurs="0" in the wsdl but I can't see how I can do that when using the cxf-java2ws-plugin. As far as I know no spring context is used? Are there other ways to configure the plugin? Any help is appreciated! //Lennart -Ursprungligt meddelande- F