I would say not to, create another quickstart if you feel there's an audience.
I know that at the stage I found the QS Archetype useful, having to remove
Hibernate would not have been a welcome or easy task.
> -Original Message-
> From: Howard Lewis Ship [mailto:hls...@gmail.com]
> Sent:
Why not include the config needed for tapestry-hibernate in the pom, but
comment it out. That way you don't automatically get the cruft if you don't
want hibernate, but if you do it's really easy to figure out how to include
it.
Szemere
I don't think Hibernate should be added in the quickstart. Just having an
in-memory DAO is good enough, and a wiki page on adding t5-hibernate to the
vanilla (plain) quickstart can be added.
On Fri, Jan 23, 2009 at 10:16 AM, Robert, Brice <
brice.rob...@alliancebernstein.com> wrote:
> -- No -- H
-- No -- Hibernate dependency
But sample class using an annotation to access a service DAO that uses
Mock Objects (Using Spring or Juice) would be great.
I use:
- T5 for HTML/CSS/JavaScript,
- SmartGwt (SmartClient / GWT) for AJAX
- Spring for DI (Using Annotations)
- DAO Access through JPA, JM
Yuck. :)
I know hibernate is "all the rage" now, but, honestly, it's not /that/
hard to go add a dependency.
I prefer the cleaner archetype that doesn't make assumptions about
what technology stack you'll be using, other than tapestry.
Robert
On Jan 22, 2009, at 1/226:32 PM , Howard Lewis
On Thu, Jan 22, 2009 at 10:50 PM, Howard Lewis Ship wrote:
> I'm of the opinion that it's easier to remove unwanted stuff than add
> it in.
Tapestry-hibernate, when it is in the classpath, tries to create a
SessionFactory. So, if someone wants the Tapestry archetype without
Hibernate, at first he
I think the archetype is fine as it is. IMHO adding the Hibernate
support would confuse things (what to remove, what to keep), especially
for beginners who are going to use this archetype. I'm developing my 4th
T5 project, and I dont use the archetype any more. So maybe my point of
view (archet
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 a
As dbms choice and database setup (dialect, connection, pool
configuration) are highly individual and need to be done manually either
way, I don't see the need to include a dependency on tapestry-hibernate
in the quickstart just so that a potential user doesn't have to add it
to his POM by hims
I'm of the opinion that it's easier to remove unwanted stuff than add
it in. I really don't want to maintain two archetypes, but the other
developers are beginning to be more active, so maybe my bandwidth
shouldn't be the deciding factor.
On Thu, Jan 22, 2009 at 5:41 PM, Thiago H. de Paula Figuei
Em Thu, 22 Jan 2009 21:32:21 -0300, Howard Lewis Ship
escreveu:
The title says it all. It would be very easy to include
tapestry-hibernate as a dependency, and a minimal hibernate.cfg.xml
file as well. Thoughts?
What about having two quickstarts, one with Hibernate and other with
Hibern
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 thi
12 matches
Mail list logo
