Thanks Simon,
Simon Kitching schrieb:
On Wed, 2005-05-18 at 12:20 +0200, David Perez wrote:
You're right, I have changed the commons-logging version to the latest one.
Now I have reverted to commons-logging-1.0.2
I would recommend using commons-logging-1.0.4. After all, that is the
most rec
On Wed, 2005-05-18 at 12:20 +0200, David Perez wrote:
> You're right, I have changed the commons-logging version to the latest one.
> Now I have reverted to commons-logging-1.0.2
I would recommend using commons-logging-1.0.4. After all, that is the
most recent official release.
> >I suggest regi
Hi Simon,
Thanks for your answer.
See my comments below
Simon Kitching wrote:
Firstly, I presume you mean commons-logging-1.0.5-alpha1? Note that this
really is rather experimental; I presume jetty didn't come with this
version of commons-logging?
You're right, I have changed the commons-log
Hi David,
On Wed, 2005-05-18 at 08:56 +0200, David Perez wrote:
> I have created a web app, integrated with a web server called Jetty.
> Both of them use commons-logging 1.5 alpha1.
> There is just one set of jars shared between them.
> The optional package is included, so weak references must
Hi,
This is my 1st message to the list.
I have created a web app, integrated with a web server called Jetty.
Both of them use commons-logging 1.5 alpha1.
There is just one set of jars shared between them.
The optional package is included, so weak references must be active.
I have implemente weba
