Gang,
I am looking at running a LogService on a CDC, but LogListener extends
EventListener, which AFAICT is not included in the CDC profile (see JSR-218).
I can't envision any reason why we need EventListener as the interface. After
10 years of using the EventListener/EventObject pattern, I have yet to see
when I needed that interface...
Q; Doesn't this hinder the usage of LogService spec for the mobile case?? One
can't just add java.util.EventListener in the LogService bundle, can you?
What can be done about it now?
If we do;
public interface LogServiceListener
{
void logged( LogEvent event );
}
/** @deprecated Use LogServiceListener instead. */
public interface LogListener extends LogServiceListener, EventListener {}
public interface LogReaderService
{
void addLogListener( LogServiceListener listener );
void removeLogListener( LogServiceListener listener );
Enumeration getLog();
}
then 'normal' uses will be compatible, but some reflection cornercases and
possibly serialization issues will surface.
That brings me to the follow up question; Is it time to "Retire" spec 101, and
introduce a new one, perhaps a bit more modern with a separation of "tracing"
vs "log recording"/"audit trail".
Cheers
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
