uot;Tom Coleman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 10, 2002 4:50 PM
Subject: Re: [JBoss-user] ServiceLocator pattern and the connection pool in
JBoss
>
>
> The ServiceLocator pattern is interesting and can probably prove
> useful in comple
The ServiceLocator pattern is interesting and can probably prove
useful in complex applications, but I think that's where the
decision to implement it belongs, in the application.
Incidently, if you review Sun's code, there are two flavors of
ServiceLocator (SL) - one for the Web tier, the oth
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 10, 2002 3:57 PM
Subject: Re: [JBoss-user] ServiceLocator pattern and the connection pool in
JBoss
Personally I think this pattern is slightly silly.
However, AFAIK, you should be looking up datasources from your SL not
connections, or at least
Personally I think this pattern is slightly silly.
However, AFAIK, you should be looking up datasources from your SL not
connections, or at least getting connections from a ds whenever you ask for
one. This should work. If it doesn't please provide details. Caching
connections themselves wont w
Hi to the jboss users
Some time ago I came across the ServiceLocator pattern as a J2EE design
pattern.
The pattern says that you can use it to manage your resources like the local
or remote interfaces of your EJBs. It is implemented as a Singleton and
should
cache your instances.
Actually the patt
