Geoff describes it here http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/onactivateandonpassivate/3 Basically you shouldn't do db lookups in onActivate() and should use onPrepare() instead. For this same reason, I think it's a bad idea to use @PageActivationContext with a hibernate entity
- Possible n+1 hibernate bug with tapestry cru... George Christman
- Re: Possible n+1 hibernate bug with tap... Thiago H. de Paula Figueiredo
- Re: Possible n+1 hibernate bug with... George Christman
- Re: Possible n+1 hibernate bug ... Thiago H. de Paula Figueiredo
- Re: Possible n+1 hibernate ... Lance Java
- Re: Possible n+1 hiber... George Christman
- Re: Possible n+1 h... Thiago H. de Paula Figueiredo
- Re: Possible n... George Christman
- Re: Possible n... Thiago H. de Paula Figueiredo