Holger included a link to a WO document which included this example:
<%@ taglib uri="/WOtaglib" prefix="wo" %>
<HTML>
<HEAD>
<TITLE>Using Two Components</TITLE>
</HEAD>
<BODY>
<wo:component className="Hello">
</wo:component>
<P><P>
<wo:component className="FavoriteFood" bodyContentOnly="true">
<wo:binding key="visitorName" value='<%= "Worf" %>' />
<wo:binding key="favoriteFood" value='<%= "gagh" %>' />
</wo:component>
</BODY>
</HTML>
what if it were twisted this way:
<%@ taglib uri="/TapestryTaglib" prefix="tapestry" %>
<HTML>
<HEAD>
<TITLE>Using Two Components</TITLE>
</HEAD>
<BODY>
<tapestry:component id="Hello" type="Hello">
</tapestry:component>
<P><P>
<tapestry:component id="FavoriteFood" type="FoodComponent">
<tapestry:static-binding name="visitorName"><%= "Worf"
%></tapestry:static-binding>
<tapestry:static-binding name="favoriteFood"><%= "gagh"
%></tapestry:static-binding>
</tapestry:component>
</BODY>
</HTML>
This definitely perverts the tapestry way of separating static from dynamic
content, but it would be a way to get JSP developers feet in the door.
Geoff
Geoffrey Longman
Intelligent Works Inc.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
