The use of EventListener/EventObject were, in hindsight, completely 
unnecessary. Oh well.

But this is not an issue in real life since there is almost always 
Foundation Profile on CDC which includes those classes.

Also, there is an open request (in the public OSGi bugzilla) for enhancing 
LogService: https://www2.osgi.org/bugzilla/show_bug.cgi?id=7 
Perhaps you can review as propose additional requirements.
-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]

office: +1 386 848 1781
mobile: +1 386 848 3788




Niclas Hedhman <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
2007-05-28 00:14
Please respond to
OSGi Developer Mail List <[email protected]>


To
OSGi Developer Mail List <[email protected]>
cc

Subject
[osgi-dev] LogService inability to run on "pure" CDC







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


_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev

Reply via email to