+1
I Guess this is a marketing decision - what is the magor target group of
tapestry and what are its constraints. it also depends whre howard and
others see tapestry going in this respect.
For us, 1.5 is fine, but I doubt if we fit into this target, being very
flexible, and currently fixed on Tapestry.
Cheers,
Ron
Kent Tong wrote:
Howard Lewis Ship <hlship <at> gmail.com> writes:
Now, we would hope that 4.1 will not have as long a life cycle as 4.0,
which was 50% too long. I would hope for a final 4.1 by Q3 2006.
One thing that I, personally, would like would be to start re-working
the APIs to make use of JDK 1.5 annotations and generics. Unlike the
add-one annotation support in Tapestry 4.0, this would MANDATE JDK 1.5
for development and production.
I'd suggest that we check the product roadmap of the major J2EE
containers (eg, Tomcat, JBoss, WebLogic, WebSphere, OC4J, ...) to
see if their then current products at Q3 2006 will still support
JDK 1.4 or not. Then just go with their decision.
--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
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]
