Just to fan the fires of discussion, I am using the Avalon based hibernate
service that was originally part of Fulcrum, but was moved to the Hibernate
project due to licensing issues.
Having said that, I have a couple files that I use on every project that are
required to use Hibernate.
Specifically I have a servlet filter that opens and closes Hibernate session
object so that queries can be executed during the templating process,
without having the developer manually open and close it.
I also have a ServiceLocator that gives me a singleton interface to the
Hibernate Session object. It is used by the Servlet filter to actually open
and close the hibernate session object.
These classes are based on Hibernate recommeded design, and both I and Eric
Chew managed to cobble versions together that are remarkable similar.
I would like to add this to 2.3 codebase so all Turbine users can reuse
them. Any opinions?
I see:
o.a.t.filters.HibernateFilter The hibernate Filter
o.a.t.util.HibernateSession The singleton interface to the
Hibernate session object.
Thanks all,
Eric
-----Original Message-----
From: Humberto Hernandez Torres [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 11:44 AM
To: Turbine Developers List
Subject: RE: Freemarker support
> -----Original Message-----
> From: Rodrigo Reyes [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:19 AM
> To: Turbine Developers List
> Subject: Re: Freemarker support
>
>
> Hi all
> I've been reading the current posts about Freemaker and I
> think it is
> time to share my point of view.
> I believe Turbine should be "tool-agnostic". What do I
> mean? Turbine
> should (and I think, it does most of the time) provide a
> framework which
> should be able to work with whichever tool I decide to use.
> An example for
> this: OR mapping tools. I know most people around Turbine like Torque.
> Still, I don't. I may change my opinion later, but so far, I
> prefer other
> tools like Hibernator. So I think Turbine should provide a trully
> "tool-agnostic" framework where I could use Hibernator
> without any strings
> attached to Torque.
That is understood and there has been a lot of work on decoupling Torque
from Turbine. I've tried Hibernate with Turbine and it works fine. However,
There are a few things that could be done to make it easier. Eric Pugh has
been working on a HibernateService and that will make it easier. Probably
the strongest dependence on Torque is on the security service.
--
Humberto
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
