File Release Notes and Changelog
Notes:
Changes:
<ul>
<li>Version 0.8.4 contains a switch to enable <strong>client side
XSL transformation</strong>. Therefore its possible to use an
optional <tt>xsl_clientside=true</tt> parameter in your request.
To make this possible the <strong>StrutsCXDocumentBuilder</strong>
then integrates an XSL-Stylesheet ProcessingInstruction with a
link to the XSL Stylesheet and forwards the pure XML file to the
client. </li>
<li>No need to supply a <strong>standardXSL</strong> any more. (Read
on for reasons why.) </li>
<li>The <strong>StrutsCXTransformer</strong> got its sendXML() method
introduced in v0.8.3 renamed to makeNoTransformation()! The parameters
this private method contains have been cleaned up, too. <br/>
Inside this method the response.setContentType() now sets the
encoding as well. Instead of <tt>"text/xml"</tt> it uses <tt>"text/xml;
charset="+charset</tt>. This little change let the browser know
which encoding to use. This way encodings outside the ISO-8859-1
can get displayed correctly. This makes the workaround with the
standardXSL unnecessary! <br/>
In consequence of this, inside the method transform() the parameter
<tt>String standardXSL</tt> has been removed.<br>
<br/>
The methods getFopparam() is renamed to getFOPParam() and the
setFopparam() got renamed to setFOPParam(). Both have private
access now.</li>
<li>All method calls to the StrutsCXTransformer.transform() have
been updated. Check out <strong>StrutsCXServlet</strong> and StrutsCXTransformer
itself.</li>
<li>In the <strong>web.xml</strong> the init of the StrutsCXServlet
to load the standardXSL has been removed.</li>
<li>Added a comprehensive client side XSL transformatin example
to the <strong>StrutsCX prototype</strong>.</li>
<li><strong>StrutsCXConstants</strong> contains some new parameter</li>
<li>See the <a href="api/v084/index.html" class="text01"><i>Version
0.8.4 API</i></a></li>
</ul>