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 what jar versions you are using and what parameters and such you are giving to your Shell component. (have you overriden the Shell component and forgotten maybe?) On 6/28/07, spot_ <[EMAIL PROTECTED]> wrote:
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 further help? Thanks Christoph Marcus Schulte wrote: > > do you have the @Shell parameter "dojoPath" set explicitly somewhere, > possibly in an override for the standard Exception -page? > -- View this message in context: http://www.nabble.com/Problem-after-upgrade-to-Tapestry-4.1.2-tf3993336.html#a11349578 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
