On Thu, 12 Feb 2015 08:45:34 -0200, Poggenpohl, Daniel
<daniel.poggenp...@isst.fraunhofer.de> wrote:
Hello,
Hi!
I have described a problem I'm having on
http://stackoverflow.com/questions/28473491/tapestry-5-3-8-jetty-hibernate-4-3-5-xampp-1-8-3-idclass-uses-derived
When posting a question on this mailing list, please include here the
details.
. At the moment I'm trying to find out
- if the above problem has a solution
Yes: don't use compound (non-integer, non-database-generated) primary keys
unless you're dealing with legacy databases. It's a lot of pain and
decreased performance for no gain. It really amazes me how people still
use it. tapestry-hibernate doesn't support compound primary keys
out-of-the-box. Another recommendation: avoid using @Persist, even more in
components.
- if properties containing entities can be used as component parameters
Yes.
- why the entities are detached when I click the button
Form submissions and event links are processed in another request, which
is another thread, so the original Hibernate session was already closed.
- why the app is trying to persist the entities although they are
detached
You're invoking session.merge().
Any ideas?
Regards,
Daniel Poggenpohl
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
