Christian Edward Gruber wrote:
If you're going to do that, you should probably include a basic value
object with a sample property and a DAO configured as a T5 service to
allow someone to know what you're talking about. Just wiring up
Hibernate isn't as helpful. Though we're starting to talk about a
jump-start-esque thing at this point.
By no means am I suggesting don't do it, but it could be more
confusing if you did it without the last little pieces. Really it
sounds like a different archetype to me.
I also agree with that. For now, I never use T5-hibernate in any
project. I'm perhaps a special case, but I dealt with a T5-LDAP project
(no hibernate), a T5 front-end on top of a Spring-based
busines/persistence layer (hibernate was used, but handled by spring), a
T5-JCR project (again, hibernate wasn't in the scope of T5).
So, that's my first argument : T5-hibernate isn't a common dependency
for every one.
Secondly, has Christian said, if all the matter is to have the
dependency in the pom, I think it's just useless. It's kind of five
lines to add in a file.
At contrario, if the aim is to demonstrate in the quickstart app HOW
(simply) T5-hibernate works, the goal seems _really_ interesting: it
demonstrates common idioms, bring best practices into ligth, etc. But in
this case, the quickstart should be able to really demonstrate the use
of T5-hibernate, and so comes we the full stack (a domain object, a dao
service or the direct entity persistence strategy, and a DB). But that
is more and more looking like a small tutorial...
So, to sum up:
- I don't see the point at ONLY having T5-hibernate in the POM ;
- I clearly see the advantage at having a full persistence example ;
- I thing, but I'm almost certainly biased here, that having
T5-hibernate in a project is not the vast majority of T5 project, and so
should not be in the simplest quickstart.
At this point, I'm thinking again at what I just say... And in fact, I
use quickestart only for test / demo app, in a bigger project, I almost
always build the app from strach, and just copy/past what part of the
pom I need. So perhaps it just doesn't matter to have to remove
T5-Hibernate in a really, more-than-five-minutes-spent project, and I
may be a good plus for a demo/test (but I maintain that I would like to
be able to really use persistence as soon the quickstart is finished)
So, it seems that I have no definitive idea on the subject... Best
solution: 2 quickstart, a ligth and a full-stack ; but I could see why
having only the second one is OK.
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
http://fanf42.blogspot.com
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
