Actually, that's not how it works in Tapestry; the annotations override the XML, not the other way around.
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. On 11/1/05, Kevin Menard <[EMAIL PROTECTED]> wrote: > In a recent blog post, Howard mentioned that in Tapestry 4 annotation > values can be overridden via XML too. Has anyone been able to get this to > work? I've found that in a few cases, I'd prefer to use annotations since > they get inherited and can be easily overridden by subclasses. However, I > tend to have that odd page that really doesn't need a page class, so I'd > like to just use a page spec (indeed, I may already have a page spec for > that page). The page spec defines the page class as my base class, so > within the spec, I'd like to be able to override the annotation value. > Thus far, I haven't been able to do it without Tapestry complaining that > the property in question already exists. > > So, have I just been doing something wrong? The blog posts seems to > indicate that I ought to be able to do this. > > Thanks, > Kevin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [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]
