But sometimes specific combinations of projects give certain problems.
For example, when using Hibernate and proxies, you can't serialize the
Hibernate entities on uninitialized-proxies. The Hibernate session gets
lost and you get a "Lazy Initialization Exception".
But Tapestry usually serializes objects when using Table in a form, so
you start getting Hibernate errors on rewind (and only if the objets
weren't initialized before!) and it's a very hard bug to uncover (just
using the 'converter' parameter solves it, if anyone wants to know ;)).
That's an example of a specific problem caused by integration between
the 2 frameworks. So, of course, Tapestry could have a section for the
*main* frameworks (believed to be main by the community), explaining
some things like this. It's easier for the support guys, too.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Jesse Kuhnert wrote:
P.S. I'm too tired to think too hard about a good response, but I'm still a
little undecided on whether I agree that there shouldn't be content about
specific projects related to tapestry.
Though there are things I don't like about it, I think the current
http://testng.org site is a good example of this. It's pretty darn easy and
clear to understand what other projects support it and how. I like the fact
that they're documented on the site itself.
Tapestry is a much larger beast certainly though, so the examples don't
completely correspond.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
