Also,
org/apache/tapestry/Framework.library
org/apache/tapestry/pages/StaleLink.page
org/apache/tapestry/pages/StaleSession.page
, the wml components and many contrib components
still use the 3.0 spec.
Would they need to get changed to 4.0 (for completeness) ?
Andreas Andreou wrote:
Howard Lewis Ship wrote:
I believe we are getting very close to the 4.0 end game.
I still have a few bugs I really want to fix,
I don't know why the Checkbox component is still missing its
displayName property
http://issues.apache.org/jira/browse/TAPESTRY-652
and some more
documentation and tutorials that *should* get written.
, and there are also some corrections to the docs that need to be
included, i.e.
http://issues.apache.org/jira/browse/TAPESTRY-693
http://issues.apache.org/jira/browse/TAPESTRY-459
But nothing
that can't wait for a 4.0.1 bug fix release or a 4.1 release.
I would encourage developers to take a look at the open bug list and
see what's pending.
How many people are using 4.0 in a production environment right now?
Or ramping up to a production environment?
My biggest concern is runtime performance. My gut feeling is that
outside of startup time, 4.0 is equal to or better performing than
3.0.
Not that I've run any specific benchmark, but it's also my feeling that
the runtime performance has improved.
I've been troubled by some concerns on the web about memory
leeks possibly related to Javassist class creation (but I suspect
those people are running with caching disabled and just don't know it,
or won't admit it).
I've had those "problems" only when caching was disabled.
I'm hoping that beta-12 will be the last beta, and we can call a vote
for a release candidate after that. However, release working software
is more important than keeping to a schedule.
We're all looking forward to an RC release.
Well done!!!
--
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]
---------------------------------------------------------------------
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]
