Eclipse Community Forums: M2T (model-to-text transformation) » difference between 'transform' and 'deployedTransforms' extension points

Home » Modeling » M2T (model-to-text transformation) » difference between 'transform' and 'deployedTransforms' extension points

Show: Today's Messages :: Show Polls :: Message Navigator

difference between 'transform' and 'deployedTransforms' extension points [message #43090]

Fri, 14 March 2008 15:21

Felix Dorner

Messages: 676
Registered: July 2009

Senior Member

Hey, I am a plugin-newbie so if you have general comments feel free..

I have a single plugin that does realize a jet transformation. In my
plugin I also have an action that executes that transformation on a
selected file. Until now, I just used the "transform" extension point,
and in my action I call JET2Platform.tranform...(mypluginID,...)
I now see, that "clients should not use this extension point". As for
now my approach works fine, so why should I not use it? Should I switch
to use the "deployedTransforms" exension point? What is the difference?

Felix

Report message to a moderator

Re: difference between 'transform' and 'deployedTransforms' extension points [message #43643 is a reply to message #43090]

Wed, 26 March 2008 14:15

Paul Elder

Messages: 849
Registered: July 2009

Senior Member

Felix:

The transform extension point registers information about your
transformation to the JET runtime. It is necessary to successfully load and
execute your transformation.

The deployedTransforms extension point registers a JAR (containing an
exported JET transformation project using the Export deployable plug-ins
wizard). You do not need to use this. In many cases, just deploying your JET
project as a normal plug-in is all you need.

Paul

"Felix Dorner" <felix_do@web.de> wrote in message
news:fre54q$b34$1@build.eclipse.org...
> Hey, I am a plugin-newbie so if you have general comments feel free..
>
> I have a single plugin that does realize a jet transformation. In my
> plugin I also have an action that executes that transformation on a
> selected file. Until now, I just used the "transform" extension point, and
> in my action I call JET2Platform.tranform...(mypluginID,...)
> I now see, that "clients should not use this extension point". As for now
> my approach works fine, so why should I not use it? Should I switch to use
> the "deployedTransforms" exension point? What is the difference?
>
> Felix

Report message to a moderator

Previous Topic:	UserRegion in non Java artifacts?
Next Topic:	UserRegion Does not work... Please help

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 04:37:13 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter