Oh yeah, you obviously don't need the Hibernate code there.
Angelo Chen wrote:
>
> Hi Martin,
>
> Can you share some portion of the code ? I'd like to test it if I can
> speed up my app? Thanks.
>
> A.C.
>
>
> Martin_S wrote:
>>
>>
ike to test it if I can
> speed up my app? Thanks.
>
> A.C.
>
>
> Martin_S wrote:
>>
>> I have chosen quick-and-dirty for now. like
>> http://www.hibernate.org/114.html, I used a ServletContextListener to
>> detect deployment. For our particular objectiv
onentClassResolver would need
>> a
>> > method that could provide the names of all pages. It knows, but
>> doesn't
>> > currently have an API to share that information.
>> >
>> > Armed with the page names, you would just have to make a bunch of c
Hi Howard, I have found both ApplicationInitializer and ComponentSource only
available by injection within a page which is already instantiated. What I
was looking for is a way to create all pages (or even just one) before a
user request would hit.
Also, could you give just a little bit more deta
Tapestry 5 currently is slow when a user hits a page for the first time.
Does anyone know how to make T5 create all page instances at deploy time in
Tomcat? For example, the Hibernate project suggests using a
ServletContextListener to create a SessionFactory. Something similar would
be great in T5
