"Application-platform" pattern issue [message #648196] |
Tue, 11 January 2011 18:14 |
Missing name Missing name Messages: 3 Registered: January 2011 |
Junior Member |
|
|
Hi all,
I stuck with the following design issue, any help or comments would appreciated!
We are about to build an enterprise application platform in a specific business domain, based on OSGi and Virgo.
In concept, every individual platform-applications are packaged as plans or pars, and consumes some common Platform services, its fine. On the other hand, the Platform would have a "Dasboard", reporting the application-states to operational personnel.
For this, my first design approach was that each Platform application should implement an interface and register the implementation in the service-registry:
public interface IApplicationInfo {
public String getApplicationName();
public String getApplicationVersion();
public SystemState querySystemState();
...
}
Then I realized, that "scoping" in Virgo is perfectly well-done, so outside from the applications the registered services could not be seen! Bundles in the platform can not got references to these IApplicationInfo services.
So how could I build up a platform with cooperating applications?
What is the recommended pattern for this application-platform case?
Thx,
Gabor
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02939 seconds