The 4.0.x versions were ripe enough for that. I don't use page spec files
at all in my applications, especially with Tapestry-Autowire.
-Original Message-
From: Ken nashua [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 1:10 PM
To: users@tapestry.apache.org
Subject: RE
You're defining your component in both places. Take it out of the page spec
file and see what happens.
-Original Message-
From: Ken nashua [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 1:17 PM
To: users@tapestry.apache.org
Subject: RE @Component whoas... Tap-4.1.1 help
You don't have to be a 4.x expert to recognize this one; I told you
before. :)
You're trying to implicitly and explicitly define the same component,
and tapestry is complaining.
There are two types of component definitions in tapestry: explicit, and
implicit.
Implicit definitions define the
1. Autowire is a feature that I implemented as a separate library and was
integrated into the 4.1 branch. Basically, it allows you to declare an
abstract getter for a type of a HiveMind service. For example, you can do
this:
public abstract HttpServletRequest getHttpServletRequest();
And,
