> > > Hello, > > > > > > Anyone interested in adding version support for LoggingEvent > > serialization? > > > Currently, the sending side and the receiving side of a LoggingEvent have > > > to have the same fields. If a field is added or if a field is removed in > > > LoggingEvent from one log4j version to the next, if the log4j versions do > > > not match, then serialization does not work. > > > > > > It would be useful if we could gracefully handle *some* changes in > > > LoggingEvent. This is quite a nice software engineering problem. Regards, > > > Ceki
OK, I have this tracked down and the fix is pretty straightforward as long as I know what you want to do and we do it native. It's all field name based. Adding fields should work fine with no code, unless you want a default value set when an older version is read. Let me know any default values you want and I'll code those (EG: NDC to MDC translation, I haven't been using NDC's, so don't know what the "normal" answer would be). Changing field names or classes has to be explicitly handled, but is not a problem. I'll code the patches for category -> logger and priority -> level, then post the results on my site so you can see what you think. Bob -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
