So far, I'm really liking the annotations. I've started taking an
approach similar to to your blog entry of having several interfaces
which I implement to mix in various bits. One example is I have a
Validatable interface with a getValidationDelegate which has my
custom IValidationDelegate injected (though, a little documentation
on the new Validator system would be nice. I understand that it's
still in flux, but there doesn't seem to be a way to check if a
component is required anymore).
There is one place where I still like the XML though. I have several
components which don't require full blown classes because they have
no actual logic in them. But they do need either a property or two
to store temporary variables for template rendering or, in the case
of my border component, it needs a parameter which I use as a pass
through to set the title on Shell. So I'm using the XML
specification to "enhance" BaseComponent and add extra properties I
need without having to create a sub class which would have nothing
but abstract methods and the associated annotations. I'm sure you
could end up with the same situation with a Page, though I haven't
needed it there yet.
--Chris
On Jun 22, 2005, at 11:15 AM, Howard Lewis Ship wrote:
so, how are you liking the annotations? I may not be going back to
XML in the future!
On 6/22/05, Chris Conrad <[EMAIL PROTECTED]> wrote:
The fix seems to have resolved my issue as well.
Thanks,
--Chris
On Jun 21, 2005, at 5:19 AM, Howard Lewis Ship wrote:
I found one bug in InjectPage and just checked in the fix.
I don't know why you page would be processed more than once.
On 6/21/05, Chris Conrad <[EMAIL PROTECTED]> wrote:
When using @InjectPage I'm getting an ApplicationRuntimeException.
Specifically, it's happening on line 674 of
org.apache.tapestry.spec.ComponentSpecification. The error message
is "Property loginPage has already been accounted for by the
element
at unknown location."
From running it through a debugger, it looks like my page is being
processed twice and it's during the second processing that the
exception is thrown. There is only one reference to the loginPage
property and that's the abstract accessor method. My .page has
nothing named loginPage in it.
Any ideas?
--Chris
-------------------------------------------------------------------
--
To unsubscribe, e-mail: tapestry-user-
[EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
