On Wed, Feb 28, 2001 at 01:18:54PM -0700, David Geary wrote:
> I see template screens as a first step towards Cedric's Components. Template
> screens provide the foundation necessary for Components: Programmatically
> defining screens.
>
Slightly off-topic but relates to the template tags. I've raised this problen
before - maybe we have to big traffic. In this scenario...
a.jsp
--------------------------------------------------------------------
...
<html:form action="..." >
...
<template:get content="x" /> <!-- x points to b.jsp -->
...
</html:form>
--------------------------------------------------------------------
b.jsp
--------------------------------------------------------------------
...
<html:text property="..."> <!-- etc. don't mind the syntax
...
--------------------------------------------------------------------
... the servlet will crash because Struts feels that <html:text> was
defined outside an <html:form>. I think configuring forms with templates
is a major usecase of the template library, and it is _very_ annoying
that in b.jsp you had to use native HTML input tags instead of the
struts family (half of the dessigne work has gone). I think this
can be resolved only if struts taglibs were more closely coupled though
ee what would be the best way to it. Thanks incze
