Hello everyone, I figured it's been a while since this topic has been brought
up, so I'd like to come back to it again. I've finally managed to find some
free time to play with my personal project yay, which means I'll be doing
a full rewrite. I'd like to hear what Tapestry-JPA users have to say
Disclaimer: I haven't used tapestry-jpa. :)
But, Tapestry uses value encoders. tapestry-hibernate uses them, tapestry-jpa
uses them.
Tapestry uses them. The only question is whether you need to write custom value
encoders.
tapestry-hibernate will provide default encoders for entities with a
Thanks Robert for your reply. Yes I was referring to custom value encoders,
perhaps I'm misusing them. I seem to be writing custom value encoders for
components like the AjaxAddRow which is nothing more than a single column
pk. The reason I use them is to generate a temp id 's for the component to
Not sure how tapestry-jpa handles un-persisted instances. That is certainly
another area where tapestry-hibernate does not give you a useable ValueEncoder.
To clarify my last post: tapestry-hibernate will give you a functional default
value encoder if:
1) The entity has a single column pk
2)
