on 2/21/01 5:44 AM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> Jon Stevens wrote:
>>
>> Martin Poeschl wrote:
>>
>>> the pool.jar includes util.Log but it doesn't include services.logging.
> *
>>>
>>> should the logging-service be included??
>>>
>>> martin
>>
>> Ug. Yucky *necessary* dependencies. I'm starting to feel like the
>> pool.jar cannot be abstracted from Turbine any longer. That bugs
>> me and I don't know a solution other than to disable logging in
>> the pool. After all of the discussion on general@jakarta, I'm
>> starting to feel like no one in J2EE land is interested in this
>> pool any longer anyway. Anyone have other ideas, suggestions or
>> comments?
>
>
> Either:
>
> 1) We need to make the abstraction for logging independent of Turbine and a
> Jakarta "standard".
>
> 2) Standardize Jakarta on a single concrete implementation
> (jakarta-log4j?).
>
> or
>
> 3) as you stated, not do logging in reusable components. (YUCK).
>
> I'm copying the library-dev mailing list as the people there will obviously
> need to grapple with these types of issues.
>
> - Sam Ruby
Or, #4. Excuse my French: F*ck it.
Getting a connection from a Connection pool really is a thing of the past in
Turbine land (and potentially other lands when people finally get a clue
(tm)).
The reason is that tools like Turbine's Peer model completely abstract the
necessity of getting a Connection to a database and the need to return it.
It becomes something that the developer never has to worry about because the
underlying system takes care of it for you.
Therefore, it really does not matter how or where you get the
connection...just that the Peer object can get a connection. The
"old-non-j2ee" style that we are currently using in Turbine works perfectly
fine and even if we do need to plug in a different connection mechanism in
the future, it simply means changing some auto generated code. Not a big
deal. I don't see a reason at this point to change it or even switch to
something else. I really don't see the need to have JNDI or Container
managed connections.
Prove me wrong.
thanks,
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
