Go figure.  I didn't even think to look there since my searches led me to
believe there was a specific search component.  That looks to be exactly
what I'm looking for.. and good thing because I was about to start writing
some sort of simple registry of my own and was dreading it. :)  Thanks!!

On Jan 7, 2008 2:48 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

> The usual way is to use the JBI api from the component.  You need to
> access
> the ComponentContext object which is given to the component by the JBI
> container.  From this object, you can perform queries on activated
> endpoints:
>
>
> http://java.sun.com/integration/1.0/docs/sdk/api/javax/jbi/component/ComponentContext.html
>
> On Jan 4, 2008 4:13 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
>
> > I've been refactoring my services to be able to achieve more dynamic
> > operation and communications between my services.  I'm wondering if
> there
> > is
> > some functionality that can be accessed by a service that will allow it
> to
> > get a list of the registered endpoints in the system.  Basically I would
> > like to implement some sort of simple service registry that can be used
> to
> > figure out which services have been registered (so that which services
> are
> > deployed can be customized).  Really I want one service to be able to
> > figure
> > out what capabilities are available by being able to find other services
> > that have been deployed with a custom interface.  I saw there is a
> > ComponentRegistry in servicemix, is this what I would want to look at?
>  Is
> > there a better way to do this?  I don't want to reinvent the wheel,
> since
> > I'm sure Servicemix already has a capability like this to some extent.
> >
> > I found this open-esb component which looks like it's along the lines of
> > what I'm looking for, I don't know if there is an equivalent in
> > servicemix?
> >
> > http://wiki.open-esb.java.net/Wiki.jsp?page=JBIRegistry
> >
> > Ryan
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>

Reply via email to