You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by "Soltysik, Seumas" <Se...@iona.com> on 2007/01/24 19:33:28 UTC
Event Mechanism
In CXF I noticed that you are using a home-grown eventing mechanism that is based upon basic interfaces described in java.util package. However, this infrastructure seems to duplicate much of what already exists in the JMX Eventing classes. Why not simply use JMX Eventing as the internal eventing mechanism? Exposing events to other system would simply be a matter of creating an registering a JMX Listener so you are not tied to only exposing events to JMX systems.
Regards,
Seumas
Re: Event Mechanism
Posted by Daniel Kulp <da...@iona.com>.
On Wednesday 24 January 2007 14:30, Dan Diephouse wrote:
> I don't have any insight into why, but it does seem similar. If we used the
> JMX interfaces would that mean we would have to distribute a JMX jar as
> well? Or would that be a "soft" dependency?
Built into JDK 1.5. Nothing we need to do.
Dan
>
> On 1/24/07, Soltysik, Seumas <Se...@iona.com> wrote:
> > In CXF I noticed that you are using a home-grown eventing mechanism that
> > is based upon basic interfaces described in java.util package. However,
> > this infrastructure seems to duplicate much of what already exists in the
> > JMX Eventing classes. Why not simply use JMX Eventing as the internal
> > eventing mechanism? Exposing events to other system would simply be a
> > matter of creating an registering a JMX Listener so you are not tied to
> > only exposing events to JMX systems.
> > Regards,
> > Seumas
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
Re: Event Mechanism
Posted by Dan Diephouse <da...@envoisolutions.com>.
I don't have any insight into why, but it does seem similar. If we used the
JMX interfaces would that mean we would have to distribute a JMX jar as
well? Or would that be a "soft" dependency?
On 1/24/07, Soltysik, Seumas <Se...@iona.com> wrote:
>
> In CXF I noticed that you are using a home-grown eventing mechanism that
> is based upon basic interfaces described in java.util package. However,
> this infrastructure seems to duplicate much of what already exists in the
> JMX Eventing classes. Why not simply use JMX Eventing as the internal
> eventing mechanism? Exposing events to other system would simply be a matter
> of creating an registering a JMX Listener so you are not tied to only
> exposing events to JMX systems.
> Regards,
> Seumas
>
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog