| Re: AW: [geclipse-dev] Remarks and questions to eu.geclipse.info |
Stuempert, Mathias IWR wrote:
Ok.So since nobody else seems to be interested in this discussion and we have 2 +1s (Ariel and me) let's rename eu.geclipse.info to eu.geclipse.core.info and put the ui stuff into eu.geclipse.ui then! I will try to remove the extension point infoservice then. I will get back to you if there is a problem with this.Bad idea! Actually you are bypassing our model with this approach. An info service is a model element. These elements are not defined by themselves but their creators are defined (via eu.geclipse.core.gridElementCreator). The reason for this is that the grid elements most likely do not have standard constructors and a createExecutableExtension(...) will then fail. On the other hand how can an info service have a standard constructor? Does it not at least need an endpoint reference (URL or File or whatever) where to get the info from? Nevertheless, if your only use case is to get the info service for a specific VO then IVirtualOrganization.getInfoService() should do what you want. If you would like to get this for a specific VO query the VO Manager for this VO. Being able to distinguish between glite and gria information is middleware specific as I see it. I can't think of any other reason for a middleware specific filter but a need might arise in the future.Ok, this may make sense. Nevertheless I am still not sure that we really need this. The info viewer is based on a proprietary model (GLUE). So the information there will not really change for other middlewares in the future (I guess there is not extension point for changing the viewers content, right ;-). So that would mean it should be possibly to define all reasonable filters based on GLUE (and our model) without taking any middleware specific stuff into account. Am I wrong? Thanks, Nick. |