Model
ccordenier opened this issue · 12 comments
This includes :
- The design of entities
- The testing of entities
- The design of constraints
with JPA ?
I suggest to use JPA / Tapestry Hibernate / Tapestry beanvalidator
+1
hm
I said +1 but I think there is a problem here.
If we use Tapestry-Hibernate module we have to use hibernate configuration directly
If we use JPA, then there is no point to use Tapestry-Hibernate
I ve checked and Tynamo offers a Tapestry-Jpa integration module. I propose to have a look to this module.
Actually i was more thinking about jpa annotation, let's start with tapestry hibernate if you agree.
Despite on my preferences on JPA API, lets go for tapestry-hibernate
+1
Don't worry this will be for hotel booking second edition :)
Just to be complete and serious, if we use a full JPA/JTA stack then we will have to get all the spring stuffs, then we will lose the focus on Tapestry out-of-the-box contributions.
my suggestion was to use the tapestry-jpa Tynamo library
http://tynamo.org/tapestry-jpa+guide
As we are already going to test tynamo security, and Kalle has joined the project, we could have a real look to this too !
It seems, according to the documentation, that spring won't be necessary.
tapestry-hibernate
+1
ok
tapestry-hibernate +1 ;)
closed