I think your confusing the commons IO submission with the Struts
SessionObject submission, but no big deal, I know which your talking
about :)
My thoughts are this... if an object could ever be put in session, it
should be serializable unless you have a real good reason not to. The
reson is t
On Sun, 26 Dec 2004 21:33:14 +0100, Paul Libbrecht <[EMAIL PROTECTED]> wrote:
> But now, the problem is that the method TagScript.getTag() should be
> either:
> - suppressed but that's really a big change in the API, I'd just
> deprecate it
> - pulling the context from such a static method as
> Je
On Dec 26, 2004, at 3:33 PM, Paul Libbrecht wrote:
In order to kill the evil caching bug, it looks like putting all
script-to-tag storage in the JellyContext is the cleanest idea.
That means that TagScript.getTag() should become
TagScript.getTag(JellyContext currentContext).
But now, the problem
> -Original Message-
> From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 26, 2004 11:24 AM
> To: commons-dev@jakarta.apache.org
> Subject: commons-logging auto-detection WAS: [logging]
> Enterprise Common Logging... dare we say 2.0?
>
>
> Simon et al.
>
> Log4j is slo
Simon Kitching <[EMAIL PROTECTED]> wrote on 12/25/2004 06:25:51
PM:
> On Mon, 2004-12-20 at 18:28 +0100, Ceki Gülcü wrote:
> > In my last message, I failed to emphasize the brittleness of the
> > "break into interfaces" hypothesis. Even if at a high-level of
> > abstraction two API
Hi,
In order to kill the evil caching bug, it looks like putting all
script-to-tag storage in the JellyContext is the cleanest idea.
That means that TagScript.getTag() should become
TagScript.getTag(JellyContext currentContext).
But now, the problem is that the method TagScript.getTag() should be
Simon et al.
Log4j is slowly migrating to a model where there will be only a single
log4j.jar installed per Application Server. This single copy will be
installed under the ./common/lib or ./lib/ directories. See [1, 2, 3] for
further details.
Consider the case of single log4j.jar placed in ./commo
Rory -
Congratulations. I don't know how I missed the announcement of 1.3.
Well, yes, actually, I do see. It didn't have a [net] in the title
which is what my filter is looking for. Anyway, thanks for your hard work.
I'm not finished yet, but it really doesn't look hard, once you sink
your te
Hi Steve,
I pushed out 1.3 in December - I think we agreed back then that the date
formatting issue would be sufficiently large to necessitate waiting for a later
release.
Coincidentally, I made a start at the extensible date parser as well, using a
solution based on a SimpleDateFormat object
