Community
Participate
Working Groups
The extension point eu.geclipse.core.gridElementCreator is used by many external implementations (e.g. GliteJobCreator), but it is not used in internal implementations like GridConnectionCreator. Eat-your-own-dog-food... is there any reason NOT to use the extension point internally? If there is no reason, we should use the extension point internally as well and remove the direct calls.
Or let me comment on that... in our code is an implicit hierarchy: First external creators, then (if none is found) internal creators. Is this really what we want -- or more precise: What happens if more than one creator is available for a specific type?
Yes, this behaviour is on purpose. The point is that if the internal implementations should catch all causes where no explicitely defined "third-party" creator could be found since they implement "standard behaviours" like ordinary files and folders. That means that they have to be applied at the very end of the creation process when all other possibilities to create a Grid element failed. If they would be part of the extension point mechanism it would not be sure that they would be queried at the very end of the process. The result would be that for instance jobs would maybe not be created as jobs but as ordinary folders.
Markus, is this explanation satisfactory for you. Can we close that bug or would you like to leave it open for further discussion?
I am closing this issue. It's neither critical, nor does it break anything.
Closed with the M3 release
