I've uploaded the final 1.1 release. Tomorrow, I'll update the jakarta web site.
Can't believe 1.1 stretched out over a year! I hope 1.2 will be more focused and faster. And yet ... Still thinking about reducing XML in favor of code (annotations and conventions). What happens if we start to require JDK 1.5 for HiveMind 1.2? It means Tapestry 4.1 may need 1.5 as well. I'm OK with that. Imagine a builder that used annotations on the implementation class to determine what to inject and how. Image a convention of tacking "Impl" onto the service id to form the default implementation class. -- 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]
