Well, if you wanted us to share annotations, you'd have to have T5 use HM's annotations, because there's no way that HM is going to introduce T5 (or a small part of it) as a dependency. I don't think HM is going to do away with the XML configuration completely. I would definitely vote against that. There are times when you don't have the luxury of source code in which to add the annotations.
The idea I have had in the past would be to create a project that allowed you to use XML files or Annotations or anything else to supply the metadata to your applications, but access the metadata using the same API regardless of the source. I would call it Jakarta Commons Metadata or something. -----Original Message----- From: devel - Fashion Content [mailto:[EMAIL PROTECTED] Sent: Monday, July 31, 2006 6:48 AM To: Tapestry development Subject: IoC handling in T5 What if T5 implemented a strictly annotation based IoC container, and HiveMind supported the same annotations but also supported the current xml based configuration. What if T5 could work together with HiveMind or on it's own depending on wether you need backwards compatibility. Yes I see that it would potentially require a parallel set of annotation classes and parsing methods and some odd glue to merge the two, but wouldn't it be a neat way to achive both objects from the user perspective. Henrik --------------------------------------------------------------------- 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]
