|
There's a bunch of code in Tapestry that could be
reasonably replaced with off-the-shelf code from Jakarta.
I may adopt their logging stuff, as a layer between
Tapestry and Log4J/JDK1.4 ... but still maintain the Inspector.
Also, my implementation of pool is pretty brain
dead, might as well use theirs.
I'm looking around for more of the
same.
|
- Re: [Tapestry-developer] Stripping out utils code Howard M. Lewis Ship
