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) The entity is persistent
Robert On Mar 14, 2012, at 3/147:28 PM , George Christman wrote: > 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 > use. I was hoping to get away from writing custom value encoders for simple > component implementations like the one stated above. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-jpa-5-3-vs-Tapestry-Hibernate-tp5566580p5566606.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
