Carsten Ziegeler schrieb:
> Karl Pauls wrote:
>> On 8/20/07, Karl Pauls <[EMAIL PROTECTED]> wrote:
>>> Hm, extending the eventadmin sounds wrong to me. Why can't you just
>>> package your own bundle based on the eventadmin? Then you can just add
>>> your own Activator... Unless I'm missing something?
> Yes, I thought about this as well - but it comes with the cost of
> duplicating the activator code - it's not that much but still not that
> nice :)
> 
>> On second thought, I guess I'm just unable to see the use case. Could
>> you give an example of what you are trying to do that you need to
>> extend the eventadmin for?
> 
> Sure :) One idea is to add clustering possibilities which means that
> events are send to other nodes in the cluster as well.
> 
Ok, looking at the code again, I think we could change the Activator
code a little
bit and factor out the object creation in the start() method to separate
method (like createEventAdminImpl(...)) - so I could easily provide my
own activator which extends the existing one.

Carsten


-- 
Carsten Ziegeler
[EMAIL PROTECTED]

Reply via email to