Re: T5 + Tomcat 7
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. de Paula Figueiredo thiag...@gmail.com wrote: 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 different letter case than the class file. This is a file system issue, isn't it? Tapestry expects the Java class, the template file and the properties to be in the same case. In Linux, mixed case wouldn't work. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5 + Tomcat 7
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* ! and starting it won't work, it's still throwing exceptions.) Also 2 things I stumbled upon: 1. Tapestry needs log4j and I use another framework that needs log4j, that threw exceptions on the startup but I don't think it would've effected tapestry it self. 2. Looks like in jetty, it's ok to use tml\properties file with a different letter case than the class file. Like Login.class, login.properties, login.tml. I had this on jetty running fine. But on tomcat it drove me crazy till I found out whats wrong and the exception message has nothing to do with the problem ! I hope i was clear, I wrote this mail fast..wanna get back to my tapestry baby :D On Wed, Sep 15, 2010 at 7:49 PM, Koka Kiknadze 226...@gmail.com wrote: 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 fact access log says: 0:0:0:0:0:0:0:1 - - [15/Sep/2010:21:46:20 +0400] GET /myAppName HTTP/1.1 302 -[that's start of redirection, right?] 0:0:0:0:0:0:0:1 - - [15/Sep/2010:21:46:20 +0400] GET /myAppName/ HTTP/1.1 404 992 So, has anyone managed to run T5 app on Tomcat 7.0.x? TYA -- *Regards,* *Muhammad Gelbana Java Developer*
Re: T5 + Tomcat 7
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 different letter case than the class file. This is a file system issue, isn't it? Tapestry expects the Java class, the template file and the properties to be in the same case. In Linux, mixed case wouldn't work. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
