Subclass TapestryFilter, map your class instead of Tapestry's in web.xml
and override destroy(Registry registry).
There you can use something like:
DbShutdown dbShutdown = registry.getService(DbShutdown.class);
// add this new method and close the database there
dbShutdown.shutdownDatabase();
Overriding the filter might look ugly, but it was designed for that; see
the comments on destroy() and destroy(Registry registry).
You might find it less ugly to have a ServletContextListener and do the
cleanup in contextDestroyed.
The real solution would be to have a
for everyone. Once your ICLA is on file you may start
contributing to the documentation.
Uli
[1] http://www.apache.org/licenses/icla.pdf
Am 22.11.2010 10:37, schrieb Javier Molina:
I haven't explored the site thoroughly, but here are some comments:
- in general, the new site looks prettier
: Please file an ICLA [1] with secret...@apache.org and I'll
grant you write access to the wiki.
The same holds for everyone. Once your ICLA is on file you may start
contributing to the documentation.
Uli
[1] http://www.apache.org/licenses/icla.pdf
Am 22.11.2010 10:37, schrieb Javier Molina:
I
I haven't explored the site thoroughly, but here are some comments:
- in general, the new site looks prettier
- it doesn't look good to have a Tapestry 5.2.3 -- canceled post on
the front page. It's scary and you have to read the rest to know that
it's just a release that didn't pass the
You might want to contribute to the registry startup and initialize
things there:
http://tapestry.apache.org/tapestry5/tapestry-ioc/startup.html
Benny Law escribió:
Thanks Ben, this looks reasonably clean to me. Unless somebody else offers a
better idea, I will probably go with this
spaway escribió:
many thanks,
I am using netbeans IDE and have updated netbeans.conf file in my home user
netbeans/6.1/etc folder as follows:
-J-Xss2m -J-Xms32m -J-XX:PermSize=64m -J-XX:MaxPermSize=1024m
That will only affect Netbeans itself, not the tomcat server your
application runs on,
I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14 and 6.0.16). Automatic
class reloading doesn't work for pages (there are no components yet in this test
application, so I haven't checked that). Jetty 6 works fine and does autoreload pages.
Is this a known issue? Do I have to
not working for me
Hi,
Due to the way class loaders work in Tomcat you have to jar your classes
etc. and put the jar into WEB-INF/lib.
http://tapestry.apache.org/tapestry5/tomcat.html
-Filip
On 2008-04-16 13:42, Javier Molina wrote:
I'm working with Tapestry 5.0.11 and Tomcat 6 (tested on 6.0.14
