[
https://issues.apache.org/jira/browse/CXF-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951223#comment-13951223
]
Vjacheslav Borisov commented on CXF-5644:
-----------------------------------------
I checked out trunk version, compiled and successully tested server-side
transformation with @XSLTTransform and XSLTJaxbProvider
It working as expected, and path-resolution matches my needs.
But I am think that @XSLTTransform could be used for client-side transformation
too (same syntax, possibility to quickly switch from/to client/server side
transformation in design and runtime based on browser/accept header)
Without it I need different annotations for client and server side:
@XMLInstruction("<?xml-stylesheet type=\"text/xsl\"
href=\"../../stylesheets/testappjava/document.xsl\"?>")
@XSLTTransform(value="../../stylesheets/testappjava/document.xsl",
mediaTypes = "application/xhtml+xml")
What do you think about
"Should JAXBElementProvider recognize it in method addProcessingInstructions to
write out <?xml-stylesheet processing instruction ?" ?
And i should say - Thank you. Actually we started using jax-rs from jersey, but
then switched to apache cxf becouse it has almost same features as jersey and
plus
Xslt, xsd providers, useful Bean injection (from query params and form) and
many others
> Introduce XSLTTransform annotation to support server-side transformations
> -------------------------------------------------------------------------
>
> Key: CXF-5644
> URL: https://issues.apache.org/jira/browse/CXF-5644
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
