RE: [m2t-dev] M2T backend update

["Bernd Kolb" <b.kolb@xxxxxxxxxxx>]

>From my point, yes the next version should definitely be designed for osgi.
It makes a lot of things easier, we can reuse existing pde tooling for
managing dependencies and a user will most likely not even notice.
This does not mean it can only run in an osgi env. The thing here is that
osgi is much stricter with respect to class loading. So when designing this
we have to keep the stricter environment in mind. The way Arno designed it
now is capable for running inside and outside osgi.


Bernd



Mit freundlichen Grüßen
Bernd Kolb
(b.kolb@xxxxxxxxxxx)
http://www.kolbware.de

--
KolbWare
(Beratung & Coaching)
Bernd Kolb
Frühlingstr 20
73033 Göppingen

Mobil: 0163/7321605   

> -----Original Message-----
> From: m2t-dev-bounces@xxxxxxxxxxx [mailto:m2t-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Arno Haase
> Sent: Wednesday, February 27, 2008 3:54 PM
> To: Model to Text
> Subject: Re: [m2t-dev] M2T backend update
> 
> Hi Sven,
> 
> thanks for the feedback. "We" in this case was Bernd and me, arguably a
> somewhat small subset of the M2T developers ;-)
> 
> Anyway, that's why I raised the question here.
> 
> @Bernd: IIRC you said that the next version of the workflow engine
> would definitely be OSGi based - this is at odds with Sven's
> assessment.
> What's the status there?
> 
> - Ano
> 
> 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/M2TBackend
> >>
> >> Another 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