@Persist("entity") will store the id in the HttpSession and then lookup the
entity from the db any time it's required. In 99% of cases, you can avoid
HttpSession usage all together. By using @PageActivationContext or
onActivate() / onPassivate() you can pass the id in the URL and avoid
HttpSession
Thanks. I found this post that solve the problem.
http://stackoverflow.com/questions/1390008/delete-a-hibernate-entity-with-tapestry5-gives-a-different-object-with-the-sa
Using
@Persist( "entity" )
Persists the hibernate object when the input comes back to the user.
On Thu, Sep 12, 2013 at 9:12
I think the issue is because mOrder is not connected to the hibernate
session.
It looks like you are only saving the entity when the user clicks "accept".
I'm guessing that at some stage before you are submitting a form and
storing mOrder on the HttpSession?
If I were you, I'd try to remove HttpS
proxy passed to save()
It looks like I made a common error done by Tapestry 5 newbies, but I
could not find exiting threads on this issue.
It's not a Tapestry error at all. If you looked at the stack trace you
didn't provide (and you always should when posting errors to a mailing
lis
ept action link, I get the error:
uninitialized proxy passed to save()
It looks like I made a common error done by Tapestry 5 newbies, but I could
not find exiting threads on this issue.
Thanks for any help
