Jon Stevens wrote:
>
> on 8/7/01 6:05 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
>
> > Jon Stevens wrote:
> >>
> >> on 7/31/01 5:49 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
> >>
> >>> Those wrappers are minimal.
> >>
> >> What does that have to do with anything? It provides a clean abstraction for
> >> pluggable Logging within Velocity. Since no one is using it, lets get rid of
> >> it and simplify things.
> >
> > I have a client that uses it - they can take the velocity log flow and
> > mix it into their application engine. Works great.
> >
> > geir
>
> The point Jason made earlier is that you can do the same thing with Log4J.
>
> The benefit is that you code your custom logging stuff to the Log4J API's
> and then that way you can move it around to other code instead of having it
> be tied to Velocity's Logging API (which will never be used outside of
> Velocity, I'm sure).
People are using Vel's logging API, which consists of a whopping two
methods...
>
> I see a lot of value in maximum code re-usability. I'm sure you and your
> clients do as well. :-)
And non-specific generality...
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Well done is better than well said - New England Proverb
