Update of /cvsroot/freemarker/docgen/src
In directory sc8-pr-cvs1:/tmp/cvs-serv27450/src
Modified Files:
app_versions.xml ref_directives.xml xgui_imperative.xml
Log Message:
- Version history update for Pre15.
- Minor fixes
Index: app_versions.xml
===================================================================
RCS file: /cvsroot/freemarker/docgen/src/app_versions.xml,v
retrieving revision 1.164
retrieving revision 1.165
diff -C2 -d -r1.164 -r1.165
*** app_versions.xml 10 Nov 2003 14:17:28 -0000 1.164
--- app_versions.xml 16 Dec 2003 20:48:24 -0000 1.165
***************
*** 159,162 ****
--- 159,171 ----
<sect2>
+ <title>Differences between the Preview 15 and Preview 14 releases</title>
+ <itemizedlist mark="bullet">
+ <listitem><para>Bugfix: The new default template cache storage (<markup>MruCacheStorage</markup>) has started to continually fail with <markup>NullPointerException</markup> from a random point of time, usually when the memory usage was high in the JVM.</para></listitem>
+
+ <listitem><para>Bugfix: In error messages, when the quoted FTL directive had nested content, that was quoted as well, so the quotation could be very long and expose nested lines needlessly.</para></listitem>
+ </itemizedlist>
+ </sect2>
+
+ <sect2>
<title>Differences between the Preview 14 and Preview 13 releases</title>
<itemizedlist mark="bullet">
Index: ref_directives.xml
===================================================================
RCS file: /cvsroot/freemarker/docgen/src/ref_directives.xml,v
retrieving revision 1.96
retrieving revision 1.97
diff -C2 -d -r1.96 -r1.97
*** ref_directives.xml 29 Aug 2003 18:08:45 -0000 1.96
--- ref_directives.xml 16 Dec 2003 20:48:24 -0000 1.97
***************
*** 938,942 ****
<programlisting role="template"><![CDATA[
! <#assign x ="Hello ${user}!">
]]></programlisting>
--- 938,942 ----
<programlisting role="template"><![CDATA[
! <#assign x="Hello ${user}!">
]]></programlisting>
Index: xgui_imperative.xml
===================================================================
RCS file: /cvsroot/freemarker/docgen/src/xgui_imperative.xml,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** xgui_imperative.xml 10 Nov 2003 14:03:54 -0000 1.40
--- xgui_imperative.xml 16 Dec 2003 20:48:24 -0000 1.41
***************
*** 568,572 ****
<para>When you apply one of the above special keys on a node sequence that contains more than 1 or 0 nodes, then for each node in the sequence (where the special key does make sense, e.g. text nodes will be skipped for key <markup>*</markup> or <markup>@foo</markup>), the special key will be applied as it was explained for single nodes, and the results will be concatenated to form the final result. The results will be concatenated in the order as the corresponding nodes occur in the node sequence. The concatenation means string or sequence concatenation depending on the type of the results. If the special key would result in a string for a single node, then for multiple nodes the result is a single string too (the results for the single nodes concatenated), and if the special key would return a sequence for a single node, then for multiple nodes the result is a single sequence too. If there are 0 nodes in the sequence you apply the special key on, the string result is an empty string or an empty sequence respectively.</para>
! <para>XPath expressions can be used with node sequences that contain 0 or more than 1 nodes too. However, for 0 or more than 1 nodes it will work only if you use Jaxen instead of Xalan, because of the limitations of the Xalan XPath implementation.</para>
</sect2>
--- 568,572 ----
<para>When you apply one of the above special keys on a node sequence that contains more than 1 or 0 nodes, then for each node in the sequence (where the special key does make sense, e.g. text nodes will be skipped for key <markup>*</markup> or <markup>@foo</markup>), the special key will be applied as it was explained for single nodes, and the results will be concatenated to form the final result. The results will be concatenated in the order as the corresponding nodes occur in the node sequence. The concatenation means string or sequence concatenation depending on the type of the results. If the special key would result in a string for a single node, then for multiple nodes the result is a single string too (the results for the single nodes concatenated), and if the special key would return a sequence for a single node, then for multiple nodes the result is a single sequence too. If there are 0 nodes in the sequence you apply the special key on, the string result is an empty string or an empty sequence respectively.</para>
! <para>XPath expressions can be used with node sequences. However, for 0 or more than 1 nodes it will work only if you use Jaxen instead of Xalan, because of the limitations of the Xalan XPath implementation.</para>
</sect2>
|