Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread spot_
Hi Jesse, gant thank you very much! After deleting the whole "/var/cache/tomcat5/Catalina/localhost/MyApp" dir recursively on the server machine everything works fine. Cheers Christoph Jessek wrote: > > I don't know Maybe it's not a tomcat version issue at all but more of > a > library ve

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread gant
may be you should clear the tomcat caches which are in tomcat temp directory. - Original Message - From: "spot_" <[EMAIL PROTECTED]> To: Sent: Friday, June 29, 2007 1:32 PM Subject: Re: Problem after upgrade to Tapestry 4.1.2 Hello Jesse thanks for help. Bu

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread Jesse Kuhnert
I don't know Maybe it's not a tomcat version issue at all but more of a library version issue. Somehow that server machine has an old version of tapestry somewhere. On your server go to wherever the root path of tomcat is (I never install any java related software with apt/yum) and do: find

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread spot_
Hello Jesse thanks for help. But no, I have not overriden the Shell component. I searched all project files for the terms 'dojoPath' and 'Shell' with no result (except of Border.html where it belongs to). But what about this: The WebApp works fine on my development machine! It's WinXP/Tomcat 5.5.

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread Jesse Kuhnert
The exception message saying its missing classpath resource "'/dojo/'." sounds suspicious. This was the old parameter given and shouldn't be something Tapestry would reference by default in the current release. I think Marcus was on to something there.You may want to check very carefully wha

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread spot_
Hi Marcus no, I didn't set it explicitly anywhere in the code. This is the first time, I recognize this parameter. I also tried to fix the problem using this parameter and set it to dojoPath="classpath:/dojo-0.4.3/" as I saw it in the tapestry 4.2.1 jar file, but with the same results. Any furth

Re: Problem after upgrade to Tapestry 4.1.2

2007-06-28 Thread Marcus Schulte
do you have the @Shell parameter "dojoPath" set explicitly somewhere, possibly in an override for the standard Exception -page? 2007/6/28, spot_ <[EMAIL PROTECTED]>: Hi all I have a problem after upgrading to Tapestry 4.1.2. Here is the stack trace: org.apache.hivemind.ApplicationRuntimeExc