[ https://issues.apache.org/jira/browse/CXF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942985#comment-13942985 ]
Vjacheslav Borisov commented on CXF-5625: ----------------------------------------- Yes, I forgot that XMLInstruction is general use and not only xslt specific. I agree, @XsltTransform is good variant, and another variant is to use XMLInstruction "as is" for path to xslt stylesheet And use @XsltTransform to setup target mimeType only. > Server side xslt transformation using @XMLInstruction > ----------------------------------------------------- > > Key: CXF-5625 > URL: https://issues.apache.org/jira/browse/CXF-5625 > Project: CXF > Issue Type: Improvement > Components: JAX-RS > Affects Versions: 3.0.0-milestone2 > Reporter: Vjacheslav Borisov > Priority: Minor > > XSLTJaxbProvider could look to @XMLInstruction to determine path to xslt > transformation, like this > @Produces({"text/xml", "application/xhtml+xml"}) > @XMLInstruction("<?xml-stylesheet type=\"text/xsl\" > href=\"../../stylesheets/testappjava/document.xsl\"?>") > Like this > https://github.com/bystrobank/testappjava/blob/master/src/main/java/ru/ilb/common/rs/XsiXSLTJaxbProvider.java > But realisation is hardcoded that xslt is applied to second mime type in > @Produces annotation ("application/xhtml+xml") > May be this hardcode is not applicable in public library > This can be used to write service that can be used both with server-side and > client-side xslt transformation identically or to serve xml or html based on > Accept: header > Deployed application > http://tomcat-bystrobank.rhcloud.com/testappjava/web/document/list -- This message was sent by Atlassian JIRA (v6.2#6252)