1.4 logging API for 1.3.1 ??

Thread view:

Sasha - 23 Jul 2003 17:35 GMT

Hi there,

I've developed an application server which requires J2SDK 1.4 -- it uses the
logging facilities new in that version.

However, I now have to integrate some (closed-source) code into my app,
which doesn't work under 1.4, only 1.3.1. The software vendor acknowledges
the problem, but refuses to support anything but 1.3.1. The problem is
something to do with SSL authentication.

Given that finding a new vendor isn't an option -- and that getting this
project underway fast is a priority -- what are my options? Will I have to
re-code my logging stuff? I'm not keen on that idea, to tell the truth, but
if it's what I have to do... then that's what I have to do.

Thanks,

Sasha.

Reply to this Message

Mike Schilling - 23 Jul 2003 19:42 GMT

> Hi there,
>
[quoted text clipped - 10 lines]
> re-code my logging stuff? I'm not keen on that idea, to tell the truth, but
> if it's what I have to do... then that's what I have to do.

Look at http://javalogging.sourceforge.net/. This is Lumberjack, an open
source implementation of the 1.4 logging API.

Reply to this Message

Minh Tran-Le - 23 Jul 2003 23:03 GMT

> Hi there,
>
[quoted text clipped - 10 lines]
> re-code my logging stuff? I'm not keen on that idea, to tell the truth, but
> if it's what I have to do... then that's what I have to do.

I have been using Log4J that is available here:
http://jakarta.apache.org/log4j/

It works with both jdk1.3.x and jdk1.4.x the newer version have interface
that is closer to the logging facilities available in jdk1.4.x.

Minh Tran-Le.

Reply to this Message

Joseph Millar - 23 Jul 2003 23:07 GMT

> I've developed an application server which requires J2SDK 1.4 -- it uses the
> logging facilities new in that version.
[quoted text clipped - 3 lines]
> the problem, but refuses to support anything but 1.3.1. The problem is
> something to do with SSL authentication.

I sympathize. You have a decision to make. In my opinion,
this vendor who refuses to upgrade to 1.4.x is saying they
have a lack of commitment to their product and that it may
well not be supported in the near future. Any vendor who
does not upgrade their products on newer base platforms
is forcing their customers to look at other options.

So you need to decide, stay with them and submit to their
control, or look elsewhere for less restrictive product
that allows you to grow and upgrade. I have no idea how
easy or hard it will be to find another solution, that's
something you have to determine, which is best in this
situation.

> Given that finding a new vendor isn't an option -- and that getting this
> project underway fast is a priority -- what are my options? Will I have to
> re-code my logging stuff? I'm not keen on that idea, to tell the truth, but
> if it's what I have to do... then that's what I have to do.

There are a number of other logging api's available for
Java by thrid parties, both open source and purchased. A
simple search in google will find a number of them.

Good luck.

--Joe

Reply to this Message

1.4 logging API for 1.3.1 ??

Free Magazines