| Re: [m2t-dev] M2T backend update |
Hi all,based on Sven's feedback, the OSGi dependency is now optional - there is a MiddleEnd factory with two methods, one of which initializes contributions based on OSGi registration and one of which initializes the middle end with explicitly passed LanguageSpecificMiddleEnd instances.
This gives users the option, which is the best way to go for a fundamental library like the back end.
- Arno Sven Efftinge schrieb:
Hi Arno, in the wiki you wrote "Using extension points means that the middle end will always require both an OSGi container, and the Eclipse registry plugin. That is a significant increase in footprint, and it adds to configuration management complexity. The rationale that led to the decision is that the next version of the workflow engine will be built on top of OSGi anyway, and the Eclipse registry is not a big increase beyond that. The benefit of using extension points here on the other hand significantly simplifies the programming model."I think we didn't yet decide that the next version of workflow will be OSGI-based, did we? IMHO it is a vital requirement to be able to run workflows without OSGi, which does not mean that we cannot support workflow execution within OSGi optionally.The same applies to the backend: Maybe we should support execution within OSGI, but should also allow to use it without it.OSGi adaption should therefore be located in it's own plugin.I noticed that you introduced a priority field in order to specify preceedings using extension points. Although it seems that there is no better mechanism to do this, I don't like it.I'ld always prefer to explicitely configuring the factories up-front.This might be a matter of taste, but would be cool if my taste is supported ;-)keep up the really good work, Sven On Feb 27, 2008, at 13:32 , Arno Haase wrote:Hi everybody,work on the backend has been progressing nicely, and I felt like sharing the progress with you.The most generally interesting new feature is that the actual interoperability interface between languages is now in place. It is implemented using extension points, a design decision we did not take lightly and which we will be happy to discuss since it has significant impact on the overall architecture.Details are in the Wiki: http://wiki.eclipse.org/M2TBackendAnother notable new feature is the support for AOP which is also in place.As always, feedback and suggestions are welcome (and probably also necessary ;-) )- Arno -- Arno Haase Langemarckstr. 16 53227 Bonn Mobil: +49 160 98525085 Tel: +49 228 9654443 Fax: +49 228 9654448 _______________________________________________ m2t-dev mailing list m2t-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/m2t-dev
-- Arno Haase Langemarckstr. 16 53227 Bonn Mobil: +49 160 98525085 Tel: +49 228 9654443 Fax: +49 228 9654448
Attachment:
signature.asc
Description: OpenPGP digital signature