> 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. >
It's kind of evolutionary; the annoation logic adds additional information to the parsed component specification, adding in objects as if they were in the XML. There's conflict checking logic in there already, so you can mix and match but each property must be either in the XML or in an annotation; doing both will cause a runtime error. -- 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]
