Originally, I have a Tapestry5 DateField component in a page tml and it is
also specified in the corresponding
page Java class.
tml file :
<t:DateField t:id="startDate" validate="required"
format="literal:dd MMM yyyy" value="bean.startDate"
style="width:7em" />
Java class:
@Component
private DateField startDate; // DateField from tapestry 5 corelib
package
When I switch to using the DateField component from Tapx
(http://tapestry.formos.com/nightly/tapx/tapx-datefield/ ),
I only changed the namespace of DateField from t to tx in the template, and
forgot to
update DateField in the Java class to refer to the one in Tapx package.
However, the page rendered without error, but with DateField component from
Tapestry 5 being rendered.
It has taken me awhile to figure out it is caused by the embedded DateField
component in the page Java class
still referring to the Tapestry 5 DateField component.
It would be great if an error message is shown when the namespace of the
embedded component
in the tml is inconsistent with the java package of the embedded component in
the page Java class.
Shing
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
