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" wrote:
> Hi,
>
> I've converted a legacy JSP webapp over t
On Wed, 19 Dec 2012 06:47:29 -0200, John wrote:
Hi,
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.
Believe me, when you think JPA
Here's a first attempt (not compiled or tested so handle with caution).
https://gist.github.com/4335583
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/loop-components-that-use-result-sets-tp5718831p5718838.html
Sent from the Tapestry - User mailing list archi
not, I might have a go myself since it sounds
like fun!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/loop-components-that-use-result-sets-tp5718831p5718836.html
Sent from the Tapestry - User mailing list archive at Nabble.com
/tapestry5/apidocs/src-html/org/apache/tapestry5/jpa/JpaGridDataSource.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/loop-components-that-use-result-sets-tp5718831p5718834.html
Sent from the Tapestry - User mailing list archive at
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
