I highly doubt ant JPA is the source of your problem. Of course as Thiago says you can use it in such a way that could cause the problem. I would start looking at your own code and how you use JPA.
On Dec 19, 2012, at 5:17 AM, "John" <[email protected]> wrote: > Hi, > > I've converted a legacy JSP webapp over to Tapestry5+JPA and I suspect the > JPA layer may be slowing down some query responses because of the overhead of > building collections in the JPA or DAO layers. > > I am wondering if it's feasible to have a mixin or alter a loop/grid > component so that it loops over the result set directly and avoids the above > problem? Are there any components like this already, or would it be easy to > accomplish by modifying an existing compnenent? > > Your thoughts would be appreciated. > > John --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
