Re: [Proxool-developer] Why embeed external packages?

[Bill H. <bi...@lo...>]

Hi Claudio,

On Sat, 2004-01-10 at 11:02, Claudio Destro wrote:

> On the countrary, proxool-0.8.3 logs messages using its Jdk14Logger; so I get 
> my messages in a text file while proxool messages go to stdout.
> 
> Moreover, setting the org.logicalcobwebs.logging.Log System property
> (with -Dorg.logicalcobwebs.logging.Log=com.tntstudio.log.ConsoleLogger)
> produces the following stack trace:
> 
> Exception in thread "main" java.lang.ExceptionInInitializerError
>         at com.tntstudio.skyware.Skyware.startup(Unknown Source)
>         at com.tntstudio.skyware.Skyware.main(Unknown Source)
> Caused by: org.logicalcobwebs.logging.LogConfigurationException: 
> org.logicalcobwebs.logging.LogConfigurationException: 
> org.logicalcobwebs.logging.LogConfigurationException: Class 
> com.tntstudio.log.ConsoleLogger does not implement Log

We can easily fix the first issue: getting Proxool to use the standard
property value, but that second one is a bit trickier. Of course, you
could make your ConsoleLogger also implement
org.logicalcobwebs.logging.Log but that is a bit clumsy.

I'd like to have this all working transparently, I really would. It is
starting to look like we should switch back to including JCL as a
separate JAR. 

For the record, I have no compulsion to do the same for the concurrent
and collection classes we have. They have no public interaction at all.
Ditto with cglib.

> I think proxool's 
> internal JCL prevents usage of any other org.apache.commons.logging.Log 
> implementation.

Agreed.

Bill