What may be happening is that text/html ends up being 'less' preferred.
Can you update @Produces like this:
@Produces({"text/html;1.0", "application/xml;0.8", "application/json;0.8"});Also, capture HTML Accept value - we need to know how it looks like; Use CXF logging feature or get it from HttpHeaders or use tcpmon Cheers, Sergey On Thu, May 26, 2011 at 5:00 PM, gunanup <[email protected]> wrote: > Hi sergey, > I am sorry for previous msg , yes all my clients accepts text/html becoz i > am using webbrowser and soap ui to test > as you have said i looked into the documentation , I found i am missing the > thing in the configuration > > <bean id="uriResolver" > class="org.apache.cxf.systest.jaxrs.URIResolverImpl"/> > > <jaxrs:server id="CcmdServiceRESTFull" address="/restFull" > staticSubresourceResolution="true"> > <jaxrs:serviceBeans> > <bean > class="com.emailvision.apiccmd.service.CcmdServiceRESTFull" > autowire="constructor" /> > </jaxrs:serviceBeans> > <jaxrs:providers> > <bean id="xsltProvider" > class="org.apache.cxf.jaxrs.provider.XSLTJaxbProvider"> > <property name="outTemplate" > value="classpath:/xml/responseWrapper.xsl" > /> > <property name="resolver" ref="uriResolver"/> > </bean> > </jaxrs:providers> > </jaxrs:server> > > but the class does not exists > > help > thanks > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/add-HTML-output-to-JSON-and-XML-tp4427885p4429090.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Sergey Beryozkin Application Integration Division of Talend http://sberyozkin.blogspot.com
