[
https://issues.apache.org/jira/browse/CXF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942362#comment-13942362
]
Sergey Beryozkin commented on CXF-5625:
---------------------------------------
Hi
It appears there might be some opportunity to optimize, example, avoid setting
a stylesheet parameter property on XSLTJaxbProvider and use the the info from
XMLInstruction, but I'm not sure what exactly you have in mind.
For example, suppose we have Accept: text/xml. The idea of XMLInstruction is
that the transformation will be done on the browser-side. Why would we want to
transform on the server side too knowing that the browser will do the transform
?
Thanks, Sergey
> 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)
