Author: gvanmatre
Date: Sun Dec 31 12:59:41 2006
New Revision: 491484
URL: http://svn.apache.org/viewvc?view=rev&rev=491484
Log:
SHALE-380
Modified:
shale/framework/trunk/shale-clay/src/site/xdoc/index.xml
shale/framework/trunk/src/site/resources/docs/release-notes-1.0.4.html
Modified: shale/framework/trunk/shale-clay/src/site/xdoc/index.xml
URL:
http://svn.apache.org/viewvc/shale/framework/trunk/shale-clay/src/site/xdoc/index.xml?view=diff&rev=491484&r1=491483&r2=491484
==============================================================================
--- shale/framework/trunk/shale-clay/src/site/xdoc/index.xml (original)
+++ shale/framework/trunk/shale-clay/src/site/xdoc/index.xml Sun Dec 31
12:59:41 2006
@@ -124,7 +124,7 @@
<pre>
<%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h" %>
-<%@ taglib prefix="s" uri="http://struts.apache.org/shale/core"; %>
+<%@ taglib prefix="s" uri="http://shale.apache.org/clay"; %>
<s:token id="token"/>
@@ -273,7 +273,7 @@
page, we have a JSP page that uses that component to process
the HTML. That component
is accessed through a custom tag, like this:</p>
<pre>
-<%@ taglib prefix="sh" uri="http://struts.apache.org/shale/clay-plugin";
%>
+<%@ taglib prefix="sh" uri="http://shale.apache.org/clay"; %>
...
<sh:clay id="loginTemplate" jsfid="/pages/clay-login.html"
managedBeanName="loginPage"/>
@@ -387,6 +387,30 @@
</body>
</html>
</pre></blockquote></p>
+
+ <p>The Clay template parser has a few reserved identifiers that can
be used to remove blocks of markup.
+ These identifiers are in the form of HTML self-contained
comments. Since the markers are comments,
+ they do not interfere with displaying the template in a
browser. The comment blocks behave similarly to
+ the "void" reserved jsfid identifier shown in the previous
markup fragment. Another similar comment identifier
+ is used by the template parser to specify the character set
encoding of the template. Like the start and end
+ remove markers, this comment tag is self-contained. This
marker must be located somewhere near the top
+ of the document.</p>
+
+<p><blockquote><pre>
+<!-- ### clay:page charset="UTF-8" /### -->
+<!-- ### clay:remove ### -->
+<html>
+ <head>
+ <meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+ </head>
+ <body>
+<!-- ### /clay:remove ### -->
+ <p>BEGINNING OF HTML TEMPLATE<br />
+<!-- ### clay:remove ### -->
+ </body>
+</html>
+<!-- ### /clay:remove ### -->
+</pre></blockquote></p>
<p>There are two types of HTML layouts, page fragment and full HTML
layouts. The page fragments
can be pulled into a JSP page using the clay tag. The jsfid is
used to identify the HTML page
@@ -419,6 +443,58 @@
<input type=text [EMAIL PROTECTED] id=city size=20>
<input type=submit value=Save [EMAIL PROTECTED]>
</pre></blockquote></p>
+
+
+ <p>There is yet another option for creating templates using HTML markup.
The Clay parser supports XML namespaces.
+ This option allows you to borrow the JSP tag notations. In
addition to the standard tags, Clay takes it a little further
+ by adding the "extends" attribute which allows you to
inherit characteristics of another component's definitions.
+ Clay also has limited mapping support for JSPX tags allowing
for "lazy reuse" of existing JSPX templates.</p>
+
+<p><blockquote><pre>
+<!-- ### clay:page charset="UTF-8" /### -->
+<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"; version="2.0"
+ xmlns:f="http://java.sun.com/jsf/core";
+ xmlns:h="http://java.sun.com/jsf/html";
+ xmlns:trh="http://myfaces.apache.org/trinidad/html";
+ xmlns:tr="http://myfaces.apache.org/trinidad";
+ xmlns:c="http://shale.apache.org/clay">
+
+ <f:view>
+ <tr:form id="form">
+ <tr:panelPartialRoot id="ajax">
+
+ <tr:treeTable id="treeTable" var="foo" value="[EMAIL
PROTECTED]" summary="Catalog" >
+
+ <f:facet name="nodeStamp">
+ <tr:column>
+ <f:facet name="header">
+ <tr:outputText value="name"/>
+ </f:facet>
+ <tr:commandLink actionListener="[EMAIL PROTECTED]"
+ partialSubmit="true" text="#{foo.name}"/>
+ </tr:column>
+ </f:facet>
+
+ <f:facet name="pathStamp">
+ <tr:commandLink actionListener="[EMAIL PROTECTED]"
+ partialSubmit="true" text="#{foo.name}"/>
+ </f:facet>
+
+ <tr:column>
+ <f:facet name="header">
+ <h:outputText value="description"/>
+ </f:facet>
+ <tr:outputText value="#{foo.description}"/>
+ </tr:column>
+
+ </tr:treeTable>
+ </tr:panelPartialRoot>
+ </tr:form>
+ </f:view>
+</jsp:root>
+</pre></blockquote></p>
+
+
</li>
<li><p>The subtree can also be defined at runtime. The runtime support
allows the view to be defined by data
from the model tier. The Clay component provides a postback
validation method event, shapeValidator,
@@ -453,7 +529,7 @@
<p><blockquote><pre>
<!DOCTYPE view PUBLIC
"-//Apache Software Foundation//DTD Shale Clay View Configuration
1.0//EN"
- "http://struts.apache.org/dtds/shale-clay-config-1_0.dtd">
+ "http://shale.apache.org/dtds/clay-config_1_0.dtd">
<view>
<component jsfid="/rolodex/rolodex.xml" extends="clay">
@@ -482,7 +558,7 @@
definitions have similarities to the JSP tags, but are designed to be more
generic. The same node
structure is used to define a variety of resources.
</p>
-<p>A <code>component</code> is a "top-level" element. In the <a
href="http://struts.apache.org/dtds/shale-clay-config/1_0/";
target="_blank">DTD</a>,
+<p>A <code>component</code> is a "top-level" element. In the <a
href="http://shale.apache.org/dtds/clay-config_1_0.dtd";
target="_blank">DTD</a>,
a <code>component</code> can represent a JSF component, converter,
validator, action listener or value change listener. Only "top-level" elements
can be the root of a clay subtree. The <code>componentType</code>
attribute defines the association to the face's resource. The
<code>jsfid</code>
attribute is a logical unique identifier.
@@ -607,7 +683,7 @@
component properties and how components are assembled within a page. There
is currently a couple sources
to define symbols, XML and HTML. In the future this could be expanded to
other sources.
</p>
-<p>In the clay XML document type definition (<a
href="http://struts.apache.org/dtds/shale-clay-config/1_0/";
target="_blank">DTD</a>),
+<p>In the clay XML document type definition (<a
href="http://shale.apache.org/dtds/clay-config_1_0.dtd";
target="_blank">DTD</a>),
<code>symbols</code> are defined similar to <code>component</code>
<code>attributes</code>. Symbols are
defined within a <code>symbols</code> node versus an
<code>attributes</code> node. Both <code>symbols</code>
and <code>attributes</code> use the same <code>set</code> element
definition but the symbols ignore the
Modified: shale/framework/trunk/src/site/resources/docs/release-notes-1.0.4.html
URL:
http://svn.apache.org/viewvc/shale/framework/trunk/src/site/resources/docs/release-notes-1.0.4.html?view=diff&rev=491484&r1=491483&r2=491484
==============================================================================
--- shale/framework/trunk/src/site/resources/docs/release-notes-1.0.4.html
(original)
+++ shale/framework/trunk/src/site/resources/docs/release-notes-1.0.4.html Sun
Dec 31 12:59:41 2006
@@ -234,16 +234,15 @@
to build unit tests, using the Test Framework, that cater to JSF 1.2
APIs.</p>
- <p><strong>Clay Improvements</strong> - As part of the framework
refactoring,
- we reduced inner shale-clay dependencies to just the shale-core module
thereby
- providing servlet 2.3 compatibility.
- <br/><br/>
- There were several enhancements made to the Clay non-validating markup
parser.
- Clay markup template namespace support was extended to allow a prefix that
- differs from the component's definition. In addition, we added a Clay
template
- directive and a global setting to specify the template encoding. We also
added
- limited support for handing reuse of JSPX tags.
- <br/><br/>
+ <p><strong>Clay Improvements</strong> - As part of the framework
refactoring, we reduced
+ inner shale-clay dependencies to just the shale-core module thereby
providing servlet 2.3 compatibility.
+ There were several enhancements made to the Clay non-validating markup
parser. Clay markup template
+ namespace support was extended to allow a prefix that differs from the
component's "jsfid" definition. In addition,
+ we added a Clay template directive and a global setting to specify the
template encoding. We also added limited
+ support for handling reuse of JSPX tags and the "f:view" tag which
allows assigning properties of the view root.
+ An effort was made to align Clay full view templates more closely with
JSP by changing the inheritance of the Clay
+ component so it no longer is a naming container.<br/>
+ <br/>
Furthermore, we added JSF 1.2 basic support for Clay managed views. The
basic
support covers some new ground into supporting new features such as the
binding
attribute for converters, validators and listeners. This support doesn't
have
