[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] Re: Eclipse RFC 0003/platform-core-dev submission
|
Thanks for your comments. Note that this logging mechanism is intended to
be just a simple means of recording errors in Eclipse, it is not meant to
be a general mechanism for serializing arbitrary objects. The logging API
is only in terms of IStatus objects, so we only need to be concerned with
serializing the state contained within an IStatus, and nothing further. As
you noted, the JDK will be providing a complete logging infrastructure as
described in JSR 47, so there is no need for us to duplicate that
functionality in an Eclipse logging mechanism.
I will be updating the RFC today, and will extend the comment period for a
couple more days to get feedback before asking for a vote.
paules@xxxxxxxxxx
Sent by: To: platform-core-dev@xxxxxxxxxxx
platform-core-dev-admin@e cc:
clipse.org Subject: [platform-core-dev] Re: Eclipse RFC
0003/platform-core-dev submission
12/20/2001 10:47 AM
Please respond to
platform-core-dev
Please accept this submission to the platform-core-dev mailing list:
It has been proven by the proposal of RFC 0003 and XML's utility and
maturity that XML is the most appropriate format for log records. Plain
text logs are often difficult to read, query and negotiate
programmatically. To carry forward the progress and success of XML as a
data transport in the logging arena, an open format of capturing any log
message wrapped in XML is necessary. The existing XML infrastructure
permits static data structure (i.e. DOM) and/or event driven (i.e. SAX)
<snipped remaining submission>
