Well, right now I'm running T5 apps with Tomcat 7 without problems. I'm not
sure what did the trick - in fact I don't remember whether I did succeeded
at all with Tap 5.0.18 + Tomcat 7.02beta, but right now with current 5.2.6 +
7.0.16 all works fine,
On Tue, Sep 27, 2011 at 6:31 PM, Thiago H.
When I first faced your case just today, I checked the logs, you'll find
some exceptions, start from there and eliminate these exceptions because
tapestry manager does not start your application because of these exceptions
(check tomcat manager for your application's state, it should be *stopped*
On Tue, 27 Sep 2011 11:25:21 -0300, Muhammad Gelbana m.gelb...@gmail.com
wrote:
Also 2 things I stumbled upon:
1. Tapestry needs log4j
This isn't quite correct. Tapestry user SLF4J, which can use log4j
underneath.
2. Looks like in jetty, it's ok to use tml\properties file with a
I tried to migrate two apps to Tomcat 7.0.2 beta, one is using Tap 4.0.2,
another Tap 5.0.18.
I just dropped working WAR files from my Tomcat 6.0.x to 7.0.2 webapps.
Tap 4.0.2 seems to work fine.
Tomcat manager shows that Tap 5.0.18 app is also running, but I get 404 when
I try to access it. In
