1. Testing. 2. Hmm, have you looked into a <load-on-startup> tag for web.xml? I'm not 100% sure it would work with Tapestry but, since Tapestry does have a Servlet, i would guess that it would.
4. I find that the servlet loading takes the longest, about 8 seconds the first time. After that, it's hard to determine if the server was restarted, all the pages load rather quickly. -Greg -----Original Message----- From: Patrick Moore [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 10:06 PM To: Tapestry users Subject: Re: Is there a way to pregenerate Component/Page classes? 1. So that I know that there are no problems with any component or page. Otherwise how do I know a customer isn't going to find a problem on the production site? 2. So that no user experiences any delay after a server restart. 3. So that in a cluster the bytecode generation is only done once. 4. So if the server restarts it is not obvious to any user. Considering how slow it can be to generate new components and pages why would I want it done while a customer is trying to use the site? --- "hv @ Fashion Content" <[EMAIL PROTECTED]> wrote: > Uh, what?? > > You sure you are are referring to Tapestry? Why would you want generate a > class file? > > "Patrick Moore" <[EMAIL PROTECTED]> skrev i en meddelelse > news:[EMAIL PROTECTED] > > Is there a way to have Tapestry walk the component/page packages and > > generate > > the .class files? > > > > I would like to do this to make sure that in production there are no > > errors at > > the basic component/page definition level. > > > > Otherwise it seems like I am force to have a script that walks every > > page/component just to get the byte code generated. > > > > I don't know if there is a mvn plugin that will do this for me but if > > there is > > please let me know. > > > > -Pat > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
