Hi, that sounds like the same issue. I'm setting my app up as an unpacked war. I think that should fix it.
Mike On Wednesday, August 03, 2005, at 09:24AM, Adam Greene <[EMAIL PROTECTED]> wrote: >I have been using Jetty for production for over 2 years now with every build >of Tapestry and the only problem I have had is that on Linux, every so often >the temp directory gets swept and the compiled JSPs go missing. > >----- Original Message ----- >From: "Michael Henderson" <[EMAIL PROTECTED]> >To: "Tapestry users" <[email protected]> >Sent: Wednesday, August 03, 2005 11:50 AM >Subject: Tapestry in Jetty > > >> Hi, >> We're deploying a build of our application for a client to preview. >> We're using Jetty as he container and we get the following exception after >> the application has been running for a few days: >> >> Unable to locate asset 'homeStyle' of component Home as >> context:/styles/home.css >> >> A restart fixes the problem. My guess is that this is a Jetty problem. >> >> I'm going to set up Jetty to cycle every night, we're not going into >> production with Jetty and we have done limited performance testing. Has >> anyone else seen a similar issue with using Jetty for Tapestry app >> deployment? >> >> Mike >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
