|Using ECF as an Enterprise service Bus framework? [message #581338]
||Mon, 16 May 2005 10:14
| Bob Balfe
Registered: July 2009
This is a multi-part message in MIME format.|
A couple of questions. According to the documentation it appears this =
framework could be used for communication between plugins (within the =
same process), is that true?
Also, has anyone talked about using this framework as an Enterprise =
Service Bus? Integrating all of these other services into one bus could =
provide a service bus for problem resolution.
IBM Software Group
Workplace Client Technology Platform, Rich Edition
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<META http-equiv=3DContent-Type content=3D"text/html; =
<META content=3D"MSHTML 6.00.2800.1498" name=3DGENERATOR>
<DIV><FONT face=3DArial size=3D2>A couple of questions. According =
documentation it appears this framework could be used for communication =
plugins (within the same process), is that true?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Also, has anyone talked about using =
as an Enterprise Service Bus? Integrating all of these other =
one bus could provide a service bus for problem resolution.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>-- <BR>Bob<BR>IBM Software =
Client Technology Platform, Rich Edition</FONT></DIV></BODY></HTML>
|Re: Using ECF as an Enterprise service Bus framework? [message #581947 is a reply to message #581806]
||Wed, 01 June 2005 16:20
| Scott Lewis
Registered: July 2009
Bob Balfe wrote:
> Actually I do.
> What I am looking at is the possibility of using views and plugins wired
> together using XML, kind of like a property broker. The idea is to create a
> property broker where components (views, plugins, services, etc) can publish
> properties and others can listen for them and their changes. The XML comes
> into play where a developer or administrator can "wire" two components
> together. So imagine one plugin has a UI to "name" and another plugin or
> view on the screen wants to use the value stored in "name" to do a customer
> lookup. The developer can wire these views components together and
> essentially any time the name property changes the views data is refreshed.
> So what happened there is a wire engine linked the components together and
> the components know nothing about each other. The only thing they know
> about is the property broker API's.
This would be eminently doable...starting with either the 'test'
container implemented by Peter Nehrer, your own implementation, an
existing 'message bus' system, the OSGI 'wire' service, etc.
Please let us know if we can be of help in this.
Powered by FUDForum
. Page generated in 0.01658 seconds