I've got a Tapestry 5 page which seems to reload as often as needed as I
change it.  I'm injecting a DAO into it using tapestry-spring (but not
tapestry-hibernate, since I want Spring to control Hibernate).  As I change
the DAOs and the page, the page reloads, but it seems as if the DAOs do not
-- my application will complain that the DAO doesn't contain a method, for
instance.  As soon as I bounce the application server, the page picks up the
change in the DAO.

Is there any secret to getting Tapestry-Spring and live class reloading
working well together?

  - Geoffrey
-- 
Geoffrey Wiseman
http://www.geoffreywiseman.ca/

Reply via email to