cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5625) Server side xslt transformation using @XMLInstruction
Date Thu, 20 Mar 2014 21:55:44 GMT


Sergey Beryozkin commented on CXF-5625:


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:
>             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
> But realisation is hardcoded that xslt is applied to second mime type in @Produces annotation
> 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

This message was sent by Atlassian JIRA

View raw message