amiro 01/05/18 15:03:43 Modified: java/xdocs/sources/xalan xsltc_constraints.xml Log: Release Notes for XSLTC's first release on Apache. Revision Changes Path 1.2 +167 -8 xml-xalan/java/xdocs/sources/xalan/xsltc_constraints.xml Index: xsltc_constraints.xml =================================================================== RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/xsltc_constraints.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- xsltc_constraints.xml 2001/05/10 18:09:54 1.1 +++ xsltc_constraints.xml 2001/05/18 22:03:42 1.2 @@ -1,13 +1,172 @@ <s2 title="XSLTC Usage Constraints"> +<p>As of this release, the following changes, additions, omissions, oddities, problems, etc exist in XSLT may impact +your use of XSLTC. +</p> +<ul> + <li><link anchor="new">Changes and New Features</link></li> + <li><link anchor="conf">Conformance</link></li> + <li><link anchor="demos">Running Demos</link></li> + <li><link anchor="knownproblems">Known Problems</link></li> + <li><link anchor="trax">Translets and TrAX</link></li> +</ul> +<anchor name="new"/> +<s3 title="Changes and New Features"> +<p>This - being the first release of XSLTC on Apache (xml.apache.org) - "What's changed" is +relative to Preview 5 of XSLTC posted on www.sun.com/xml/developers.</p> +<ul> + <li>Simplified stylesheets are now implemented.</li> + <li>Base package name has changed from <code>com.sun.xslt</code> to <code>org.apache.xalan.xsltc</code></li> + <li>You no longer have to get the BCEL.jar file; it is included in the distribution.</li> + <li>The Project X parser components and APIs have all been replaced with JAXP equivalents. + Consequently, you may deploy XSLTC with JAXP-conformant parsers, such as Xerces or Crimson.</li> + <li>Previously undocumented feature: -x. You can use the -x option on the java command line when you + compile translets or run them to get more detailed information on errors.</li> + <li>Addition of -s to DefaultRun - a new -s option has been added to the DefaultRun class + for use with test auotmation. When you use the option, it prevents System.exit() from being called when + and exception is encountered.</li> +</ul> +</s3> +<anchor name="conf"/> +<s3 title="XSLT 1.0 Conformance and Extensions"> <p>XSLTC does not yet support the following features of the <resource-ref idref="xsl"/>:</p> +<ul> + <li>The namespace axis is not implemented. You cannot get a node set containing the namespace nodes + in scope from a context node in the document tree. Otherwise, namespace functionality is implemented.</li> +</ul> +<p>XSLTC does not support a number of features that are not required by the XSLT 1.0 specification, +but which are supported by a number of other XSLT processors:</p> +<ul> + <li>Incomplete support for extension elements and external Java functions. Currently you can set up an extension function + to call a static Java function. For the extension namespace, use<br/> + http://xml.apache.org/xalan/xsltc/java/java/<class><br/> + where <class> identifies the class with the static method.</li> + <li>Lack of support for the redirection of output to multiple + output files from within a stylesheet (equivalent to xalan:redirect or + saxon:output).</li> + <li>XSLTC does not implement a node-set extension to convert result tree fragments to + node-sets. This would enable sorting and grouping of nodes assigned to a tree </li> +</ul> +</s3> +<anchor name="demos"/> +<s3 title="Running Demos"> +<p>XSLTC provides demos for using XSLTC as a servlet and as a handler for +Brazil (a new and powerful Web techology from Sun labs). To run these demos, +download Brazil from sunlabs:</p> +<p><code> <jump href="http://research.sun.com/research/download/index.html";>http://research.sun.com/research/download/index.html</jump></code></p> +<p>and the java extensions for servlets from Sun:</p> +<p><code> +<jump href="http://java.sun.com/products/servlet/download.html";> +http://java.sun.com/products/servlet/download.html</jump> +</code></p> +<p>The translet must be specified as a pure class name, accessible +through the Brazil handler's classpath. For example:</p> +<p><code> translet=mk054</code></p> +<p>The document must be specified as a valid URL. For example:</p> +<p><code> document=http://server/path/to/filename.xml</code></p> +<p>If the file is local to the Brazil handler, it has to be +specified using the "file:filename.xml" format.</p> +<note>You also need to make the Brazil and javax classes available from you classpath</note> +</s3> +<anchor name="knowproblems"/> +<s3 title="Know Problems"> <ul> - <li>The namespace axis.<br/><br/></li> - <li>Complete support for extension elements and functions. Currently you can set up an extension function - to call a static Java function. For the extension namespace, use<br/> - http://www.sun.com/xsltc/java/<class><br/> - [can we change this to xml.apache.org/xalan/xsltc/java/<class>]<br/> - where <class> identifies the class with the static method.<br/><br/></li> - <li><br/><br/></li> - <li><br/><br/></li> + <li>Casting variables. XSLTC requires you to explicitly type cast values + returned by variables or expressions, when you use them in tests. Always a good + practice, but it may seem like overkill in some in contexts, where other XSLT processors + automatically assume or convert to the correct type. For example. unless you cast $country + to a string in the following apply-templates, entry nodes whose <country> elements + contain a string matching the global $country parameter are NOT selected.<br/><br/> + <code><xsl:apply-templates select="entry[country=string($country)]"/></code></li> + <li>Order dependency of conditions within a predicate. If you have a predicate in a select or match + expression that has multiple conditions, one of which contains a union (X or Y), put it last. + Otherwise, the predicate fails to match node that it should.</li> + <li>When using DOM caching, as shown in the Servlet demo, if the source document is local to the + server, the cache is not refreshed when the source XML document is modified. This + problem does not apply when the source is associated with a URL.</li> + <li>If you have a list of references included or imported stylesheets, put any with + a relative path last; otherwise, stylesheets in the current directory are not found.</li> + <li>[1] should be treated equivalent to position()=1, but it is not. Therefore, if + you get unexpected results using such shortcut positional predicates, substitute the + full postion()= version.</li> + <li>XSLTC fails to match existing nodes when match expressions have + multiple steps with predicates containing the position function. + The following examples are taken from the XSLTMark oddtemplates.xsl test:<br/><br/> + <code> match='top/*[position()=2]'</code><br/> + <code> match='top/*[6]/kid[2]'</code><br/> + <code> match='top/*[position()=last()]'</code><br/></li> + <li>XSTLC has problems with output escaping, see bug 1403.</li> + <li>Case-order option with sorting is ignored.</li> + <li>As a minor side-effect of implementing simplified stylesheets, if you inadvertenly + go to compile a stylesheet and give the name of the .xml doc instead of the .xsl doc, + it may compile without a warning. In some cases, the compiler aborts with an error + about too many branches.</li> </ul> +</s3> +<anchor name="trax"/> +<s3 title="Translets and TrAX"> +<p> +The Translet API has been extended to conform with the JAXP1.1 TrAX model. +This release contains the first implementation of that extension. Two +new classes have been added to the Translet XSLT codebase, they are:</p> +<p>(1) <code>org.apache.xalan.xsltc.runtime.TransformerFactoryImpl</code> -<br/> + the Translet implementation of a SAXTransformerFactory.</p> +<p>(2) <code>org.apache.xalan.xsltc.runtime.TransletTemplates</code> - + the Translet implementation of a Templates object.</p> +<p> +The existing XSLT class 'org.apache.xalan.xsltc.runtime.AbstractTranslet' +that implements the Translet interface is now also extending the +javax.xml.transform.Transformer abstract class. +</p> +<p> +This implementation is only a partial implementation, with many limitations. +These limitations include: +</p> +<ol> +<li>Currently 'StreamSource' and 'StreamResult' are the only + TrAX Sources and Results that are supported.</li> +<li>The translet is compiled everytime a call is made to the<br/> +<code>TransformerFactoryImpl 'newTransformer()'</code> method.</li> +<li>The translet is compiled everytime a call is made to the <br/> +<code>TemplateFactoryImpl 'newTransformer()'</code> method.</li> +<li>Translet are currently not cached. (See (2) and (3)).</li> +<li>Several abstract methods from SAXTransformerFactory still need to +be implemented in the xsltc.runtime.TransformerFactoryImpl class:<br/><br/> +<code> TemplatesHandler newTemplatesHandler()</code><br/> +<code> TransformerHandler newTransformerHandler()</code><br/> +<code> TransformerHandler newTransformerHandler(Source src)</code><br/> +<code> TransformerHandler newTransformerHandler(Templates templates)</code><br/> +<code> XMLFilter newXMLFilter(Source src)</code><br/> +<code> XMLFilter newXMLFilter(Templates templates)</code></li> +<li>Several abstract methods from Transformer still need to be implemented in the +AbstractTranslet class:<br/><br/> +<code> ErrorListener getErrorListener()</code><br/> +<code> void setErrorListener(ErrorListener)</code><br/> +<code> Properties getOutputProperties()</code><br/> +<code> String getOutputProperty(String name)</code><br/> +<code> void setOutputProperties(Properties props)</code><br/> +<code> void setOutputProperty(String name, String value)</code><br/> +<code> URIResolver getURIResolver()</code><br/> +<code> void setURIResolver(URIResolver resolver)</code></li> +<li>Abstract method from Templates still need to be implemented in the TransletTemplates class:<br/><br/> +<code> Properties getOutputProperties()</code></li> +<li>Several abstract methods from TransformerFactory still need to be implemented +in the <code>xsltc.runtime.TransformerFactoryImpl</code> class:<br/><br/> +<code> ErrorListener getErrorListener()</code><br/> +<code> void setErrorListener(ErrorListener listener)</code><br/> +<code> Object getAttribute(String name)</code><br/> +<code> void setAttribute(String name, Object value)</code><br/> +<code> boolean getFeature(String name)</code><br/> +<code> URIResolver getURIResolver()</code><br/> +<code> void setURIResolver(URIResolver resolver)</code><br/> +<code> Source getAssociatedStylesheet(Source src, String media, String title,</code><br/> +<code> String charset)</code><br/> +<code> Templates newTemplates(Source xslSrc)</code><br/> +<code> Transformer newTransformer()</code></li> +<li>Whenever possible, the required methods that are currently unimplemented will throw an +exception if someone tries to call them- this will alert the user that the method is not implemented. +The message is of the form:<br/><br/> +<code> "<Class Name>:<Method Name>( <args> ) not implemented yet."</code> +</li> +</ol> +</s3> </s2>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
