On Tue, 01 Nov 2005 10:26:03 -0500, Howard Lewis Ship <[EMAIL PROTECTED]>
wrote:
Actually, that's not how it works in Tapestry; the annotations
override the XML, not the other way around.
Ahh, do they actually override or simply complement? While the semantics
may be different than I thought they were, I still seem to get an error
when having both an XML entry and an annotation for the the same property.
I was discussing a more general case of frameworks where annotations
define configuration values (such as the name of a table) without
providing recourse to override that value for a particular deployment
environment. Those frameworks need a way to override the annoation
values, such as an auxillary XML file.
Okay. I thought your primary beef was that while changes to annotation
values require a recompilation, allowing the values to be overridden by
XML makes that point moot. Seems I was off a bit there.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
