You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Robert Bushman <bo...@traxel.com> on 2001/12/03 01:59:01 UTC

Version Safe LoggingEvent Serialization

Hi,

Here's the latest source for the version safe LogginEvent
and the unit test.

http://traxel.com/java/log4j/

You'll also need UnitTestProxy.java, which has to be
included in the jar with the current version of Log4j.

You must have a copy of UnitTestLoggingEvent.class in
a seperate directory or jar file from everything else
for the test to work. Set your classpath to junit.jar
and the structure that contains UnitTestLoggingEvent
all by itself, and you're ready to run.

Bob

-------------------------------------------------------------------
  Who owns your data?
    Proprietary protocols and file formats are dangerous.
-------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Version Safe LoggingEvent Serialization

Posted by Ceki Gulcu <ce...@yahoo.com>.
Robert,

I think contacting JavaWorld before writing the
article is a good idea. First, they will tell you if
they are interested in topic to begin with. Second,
they will set a deadline which makes it a priority
project, not some item on your todo list. Regards,
Ceki

--- Robert Bushman <bo...@traxel.com> wrote:
> On Wed, 5 Dec 2001, Ceki Gulcu wrote:
> 
> >
> > Robert,
> >
> > I will look at your code as soon as I have some
> time.
> > I also encourage you write an article about the
> > subject. We can write it together if you wish.
> Would
> > you like me to contact JavaWorld? Regards, Ceki
> 
> No worries on time constraints, I know how you feel.
> I'm definitely going to write an article, and will
> forward the first draft to you so you can revise it,
> will be great to have you coauthor it!
> 
> Is the best approach to contact JavaWorld before or
> after the article is ready?
> 
> Bob
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> 


__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Version Safe LoggingEvent Serialization

Posted by Robert Bushman <bo...@traxel.com>.
On Wed, 5 Dec 2001, Ceki Gulcu wrote:

>
> Robert,
>
> I will look at your code as soon as I have some time.
> I also encourage you write an article about the
> subject. We can write it together if you wish. Would
> you like me to contact JavaWorld? Regards, Ceki

No worries on time constraints, I know how you feel.
I'm definitely going to write an article, and will
forward the first draft to you so you can revise it,
will be great to have you coauthor it!

Is the best approach to contact JavaWorld before or
after the article is ready?

Bob



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Version Safe LoggingEvent Serialization

Posted by Ceki Gulcu <ce...@yahoo.com>.
Robert,

I will look at your code as soon as I have some time.
I also encourage you write an article about the
subject. We can write it together if you wish. Would
you like me to contact JavaWorld? Regards, Ceki

--- Robert Bushman <bo...@traxel.com> wrote:
> The latest version of LoggingEvent includes
> commentary,
> a fix of a forward compatibility bug (not reading
> unexpected primitives), and a switch statement in
> the place of an if(char) else if (char).
> 
> http://traxel.com/java/log4j/LoggingEvent.java
> 
> On Sun, 2 Dec 2001, Robert Bushman wrote:
> 
> > In reading this post, I find it very confusing.
> > A simpler explanation is:
> >
> > 1. Compile all three classes and add them to your
> 1.2 jar file.
> > 2. Create a jar containing *only*
> UnitTestLoggingEvent.class
> >    called "unit-test.jar".
> > 3. export CLASSPATH=unit-test.jar:junit.jar
> >    NOTE: Do not add "." or log4j.jar to your
> classpath.
> > 4. java org.apache.log4j.test.UnitTestLoggingEvent
> >
> >
> > On Sun, 2 Dec 2001, Robert Bushman wrote:
> >
> > > Hi,
> > >
> > > Here's the latest source for the version safe
> LogginEvent
> > > and the unit test.
> > >
> > > http://traxel.com/java/log4j/
> > >
> > > You'll also need UnitTestProxy.java, which has
> to be
> > > included in the jar with the current version of
> Log4j.
> > >
> > > You must have a copy of
> UnitTestLoggingEvent.class in
> > > a seperate directory or jar file from everything
> else
> > > for the test to work. Set your classpath to
> junit.jar
> > > and the structure that contains
> UnitTestLoggingEvent
> > > all by itself, and you're ready to run.
> > >
> > > Bob
> >
> >
> > --
> > To unsubscribe, e-mail:  
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
> 
>
-------------------------------------------------------------------
>   Who owns your data?
>     Proprietary protocols and file formats are
> dangerous.
>
-------------------------------------------------------------------
> 
> 
> --
> To unsubscribe, e-mail:  
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> 


__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Version Safe LoggingEvent Serialization

Posted by Robert Bushman <bo...@traxel.com>.
The latest version of LoggingEvent includes commentary,
a fix of a forward compatibility bug (not reading
unexpected primitives), and a switch statement in
the place of an if(char) else if (char).

http://traxel.com/java/log4j/LoggingEvent.java

On Sun, 2 Dec 2001, Robert Bushman wrote:

> In reading this post, I find it very confusing.
> A simpler explanation is:
>
> 1. Compile all three classes and add them to your 1.2 jar file.
> 2. Create a jar containing *only* UnitTestLoggingEvent.class
>    called "unit-test.jar".
> 3. export CLASSPATH=unit-test.jar:junit.jar
>    NOTE: Do not add "." or log4j.jar to your classpath.
> 4. java org.apache.log4j.test.UnitTestLoggingEvent
>
>
> On Sun, 2 Dec 2001, Robert Bushman wrote:
>
> > Hi,
> >
> > Here's the latest source for the version safe LogginEvent
> > and the unit test.
> >
> > http://traxel.com/java/log4j/
> >
> > You'll also need UnitTestProxy.java, which has to be
> > included in the jar with the current version of Log4j.
> >
> > You must have a copy of UnitTestLoggingEvent.class in
> > a seperate directory or jar file from everything else
> > for the test to work. Set your classpath to junit.jar
> > and the structure that contains UnitTestLoggingEvent
> > all by itself, and you're ready to run.
> >
> > Bob
>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>

-------------------------------------------------------------------
  Who owns your data?
    Proprietary protocols and file formats are dangerous.
-------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Version Safe LoggingEvent Serialization

Posted by Robert Bushman <bo...@traxel.com>.
In reading this post, I find it very confusing.
A simpler explanation is:

1. Compile all three classes and add them to your 1.2 jar file.
2. Create a jar containing *only* UnitTestLoggingEvent.class
   called "unit-test.jar".
3. export CLASSPATH=unit-test.jar:junit.jar
   NOTE: Do not add "." or log4j.jar to your classpath.
4. java org.apache.log4j.test.UnitTestLoggingEvent


On Sun, 2 Dec 2001, Robert Bushman wrote:

> Hi,
>
> Here's the latest source for the version safe LogginEvent
> and the unit test.
>
> http://traxel.com/java/log4j/
>
> You'll also need UnitTestProxy.java, which has to be
> included in the jar with the current version of Log4j.
>
> You must have a copy of UnitTestLoggingEvent.class in
> a seperate directory or jar file from everything else
> for the test to work. Set your classpath to junit.jar
> and the structure that contains UnitTestLoggingEvent
> all by itself, and you're ready to run.
>
> Bob


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>