Jazz, here's a lightweight package that so far has met all of my needs:
http://butterfly.jenkov.com/ ...
I'll be sure to take a look.
Thanks for the response.
Jazz
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.o
Jazz, here's a lightweight package that so far has met all of my needs:
http://butterfly.jenkov.com/ ...
Cheers, Bill*
*
On Thu, Jan 7, 2010 at 4:30 PM, Jasvinder S. Bahra <
bbdl21...@blueyonder.co.uk> wrote:
> I'll echo the Spring suggestion. It simplifies Action-level programming by
>> quite a
I'll echo the Spring suggestion. It simplifies Action-level programming
by
quite a bit.
On the flip side, it requires some extra XML configuration, but IMO it's a
good tradeoff.
Spring seems to be quite popular here. I'm somewhat reluctant because
Spring provides a lot more than just Databa
Good luck, and let us know how it goes.
(*Chris*)
On Thu, Jan 7, 2010 at 3:44 PM, Jasvinder S. Bahra <
bbdl21...@blueyonder.co.uk> wrote:
> We use Spring (and Spring-LDAP) for that layer. It works great, manages
>> all
>> our DAO's and their resources, and then injects them into the Actions as
So want your DAO's to be singletons?
You would have to make them Thread-safe (or synchronize and kill
performance), beware that database connections are not thread-safe.
Please note that i'm using using the database connection pooling
facilities provided by the Servlet Container (Apache Tomcat)
We use Spring (and Spring-LDAP) for that layer. It works great, manages
all
our DAO's and their resources, and then injects them into the Actions as
needed.
Chris,
At the moment, i'm trying to reaquaint myself with the ins and out of Struts
(I haven't touched it for several years), so I dont
I'll echo the Spring suggestion. It simplifies Action-level programming by
quite a bit.
On the flip side, it requires some extra XML configuration, but IMO it's a
good tradeoff.
-Brian
On Thu, Jan 7, 2010 at 12:18 PM, Chris Pratt wrote:
> We use Spring (and Spring-LDAP) for that layer. It wo
>
> Instantiating the DAO in the execute() method of each of my action's
> however, seems a little inefficient. Does Struts provide any way to
> instantiate the object once and then make it available for the lifetime of
> the container (in a way that my Actions can access it)?
>
So want your DAO'
We use Spring (and Spring-LDAP) for that layer. It works great, manages all
our DAO's and their resources, and then injects them into the Actions as
needed.
(*Chris*)
On Thu, Jan 7, 2010 at 10:06 AM, Jasvinder S. Bahra <
bbdl21...@blueyonder.co.uk> wrote:
> Does anyone know of any techniques t
Does anyone know of any techniques that would allow a Database Access Object
(DAO) to be used from the various actions that make up a Struts application?
I have a DAO which, when instantiated, acquires a data source from the
servlet container (in this case, Apache Tomcat). Thereafter, I can ex
10 matches
Mail list logo