Home » Archived » M2M (model-to-model transformation) » [ATL] New vs Old Launch Configurations and Ganymede Missing Features
| [ATL] New vs Old Launch Configurations and Ganymede Missing Features [message #85220] |
Wed, 25 June 2008 22:50  |
Eclipse User |
|
|
|
Originally posted by: ttonelli.uwaterloo.ca
Hi,
I am quite new to ATL, but I searched the documentation and the newsgroups trying to understand these problems. I hope I
haven't miss anything and that my questions are relevant.
I am using the Ganymede Modeling Tools distribution that was out today.
First, what is the difference between the New and Old Launch Configurations in Eclipse? I saw that most examples use the
Old launcher. Should I use the new instead?
Second, when I use the new launcher and a target model file does not exist, I get a null pointer exception. Note that
the transformation keeps going and creates the file (apparently correctly). Subsequent launches don't raise the
exception (or if I create a dummy target file before the 1st launch). This happens only with the new launcher, and here
is the exception:
java.lang.NullPointerException
at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.getSourceMode ls(AtlRegularVM.java:150)
at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:304)
at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:426)
at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.launch(AtlReg ularVM.java:398)
at org.eclipse.m2m.atl.adt.launching.AtlLaunchConfigurationDele gate.launch(AtlLaunchConfigurationDelegate.java:42)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:764)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:614)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:880)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlu gin.java:1083)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Also, I noticed that some features are missing in my installation, although the plugins are there (and I checked in
Eclipse's configuration details that they were loaded without errors). Specifically, I am not seeing the menu to inject
KM3 files into an Ecore model (when I click with the right button on a KM3 file), and I am not being able to use the
debugger (cannot add breakpoints nor run in debug mode). Am I missing something? Do I have to configure something to be
able to use these features?
Bests,
Thiago
|
|
|
| Re: [ATL] New vs Old Launch Configurations and Ganymede Missing Features [message #85235 is a reply to message #85220] |
Thu, 26 June 2008 08:06  |
 William Piers
Messages: 301
Registered: July 2009 |
Senior Member |
|
|
Hello,
Thiago Tonelli Bartolomei a écrit :
> Hi,
>
> I am quite new to ATL, but I searched the documentation and the newsgroups trying to understand these problems. I hope I
> haven't miss anything and that my questions are relevant.
>
> I am using the Ganymede Modeling Tools distribution that was out today.
>
> First, what is the difference between the New and Old Launch Configurations in Eclipse?
The main difference is that old configurations used an old-defined id
which was incompatible with the correct plugins id... only a technical
issue.
We left the old configurations in order to allow users to migrate them
to the new ones, using the "Compatibility" menu.
> I saw that most examples use the
> Old launcher. Should I use the new instead?
>
> Second, when I use the new launcher and a target model file does not exist, I get a null pointer exception. Note that
> the transformation keeps going and creates the file (apparently correctly). Subsequent launches don't raise the
> exception (or if I create a dummy target file before the 1st launch). This happens only with the new launcher, and here
> is the exception:
>
> java.lang.NullPointerException
> at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.getSourceMode ls(AtlRegularVM.java:150)
> at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:304)
> at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:426)
> at org.eclipse.m2m.atl.adt.launching.AtlRegularVM.launch(AtlReg ularVM.java:398)
> at org.eclipse.m2m.atl.adt.launching.AtlLaunchConfigurationDele gate.launch(AtlLaunchConfigurationDelegate.java:42)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:764)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:614)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:880)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlu gin.java:1083)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
>
I didn't encounter that bug... if possible, could you attach more
details about your example ? Thanks in advance.
> Also, I noticed that some features are missing in my installation, although the plugins are there (and I checked in
> Eclipse's configuration details that they were loaded without errors). Specifically, I am not seeing the menu to inject
> KM3 files into an Ecore model (when I click with the right button on a KM3 file),
In fact, KM3 is a GMT project which is not part of the ATL project. The
menus you mention are provided by the AM3 plugins.
> and I am not being able to use the
> debugger (cannot add breakpoints nor run in debug mode). Am I missing something? Do I have to configure something to be
> able to use these features?
>
The ATL debugger is quite incomplete, the add breakpoints you still must
position them in the outline.
Best regards,
William
|
|
|
| Re: [ATL] New vs Old Launch Configurations and Ganymede Missing Features [message #85311 is a reply to message #85235] |
Thu, 26 June 2008 17:44 |
| Eclipse User |
|
|
|
Originally posted by: ttonelli.uwaterloo.ca
Hi William,
thanks for the answers. I am now being able to use the debugger. The thing is that by following the documentation it
seemed that there was a specific ATL Debug perspective, when in fact I am using the regular Debug perspective. And
thanks for pointing out that I need AM3 plugins, I had missed that.
Regarding the exception, it was actually a problem in my input model. The ATL EMF driver was throwing an exception when
it was not able to read the model, and then later the getSourceModels would fail.
It's not really a bug, but it would be nice if getSourceModels could test for the models and fail gracefully...
Cheers,
Thiago
William Piers wrote:
> Hello,
>
> Thiago Tonelli Bartolomei a écrit :
>> Hi,
>>
>> I am quite new to ATL, but I searched the documentation and the
>> newsgroups trying to understand these problems. I hope I
>> haven't miss anything and that my questions are relevant.
>>
>> I am using the Ganymede Modeling Tools distribution that was out today.
>>
>> First, what is the difference between the New and Old Launch
>> Configurations in Eclipse?
>
> The main difference is that old configurations used an old-defined id
> which was incompatible with the correct plugins id... only a technical
> issue.
> We left the old configurations in order to allow users to migrate them
> to the new ones, using the "Compatibility" menu.
>
>> I saw that most examples use the
>> Old launcher. Should I use the new instead?
>>
>> Second, when I use the new launcher and a target model file does not
>> exist, I get a null pointer exception. Note that
>> the transformation keeps going and creates the file (apparently
>> correctly). Subsequent launches don't raise the
>> exception (or if I create a dummy target file before the 1st launch).
>> This happens only with the new launcher, and here
>> is the exception:
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.getSourceMode ls(AtlRegularVM.java:150)
>>
>> at
>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:304)
>>
>> at
>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:426)
>>
>> at
>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.launch(AtlReg ularVM.java:398)
>>
>> at
>> org.eclipse.m2m.atl.adt.launching.AtlLaunchConfigurationDele gate.launch(AtlLaunchConfigurationDelegate.java:42)
>>
>> at
>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:764)
>>
>> at
>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:614)
>>
>> at
>> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:880)
>>
>> at
>> org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlu gin.java:1083)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>
> I didn't encounter that bug... if possible, could you attach more
> details about your example ? Thanks in advance.
>
>> Also, I noticed that some features are missing in my installation,
>> although the plugins are there (and I checked in
>> Eclipse's configuration details that they were loaded without errors).
>> Specifically, I am not seeing the menu to inject
>> KM3 files into an Ecore model (when I click with the right button on a
>> KM3 file),
>
> In fact, KM3 is a GMT project which is not part of the ATL project. The
> menus you mention are provided by the AM3 plugins.
>
>> and I am not being able to use the
>> debugger (cannot add breakpoints nor run in debug mode). Am I missing
>> something? Do I have to configure something to be
>> able to use these features?
>>
>
> The ATL debugger is quite incomplete, the add breakpoints you still must
> position them in the outline.
>
>
> Best regards,
>
> William
|
|
|
| Re: [ATL] New vs Old Launch Configurations and Ganymede Missing Features [message #85328 is a reply to message #85311] |
Thu, 26 June 2008 19:13 |
| Eclipse User |
|
|
|
Originally posted by: ttonelli.uwaterloo.ca
BTW,
in debug mode, I cannot see the variables, I don't know why...
Cheers,
Thiago
ps - using Ganymede Modeling Tools and JRE 1.6.0_10 on Linux
Thiago Tonelli Bartolomei wrote:
> Hi William,
>
> thanks for the answers. I am now being able to use the debugger. The thing is that by following the documentation it
> seemed that there was a specific ATL Debug perspective, when in fact I am using the regular Debug perspective. And
> thanks for pointing out that I need AM3 plugins, I had missed that.
>
> Regarding the exception, it was actually a problem in my input model. The ATL EMF driver was throwing an exception when
> it was not able to read the model, and then later the getSourceModels would fail.
>
> It's not really a bug, but it would be nice if getSourceModels could test for the models and fail gracefully...
>
> Cheers,
> Thiago
>
> William Piers wrote:
>> Hello,
>>
>> Thiago Tonelli Bartolomei a écrit :
>>> Hi,
>>>
>>> I am quite new to ATL, but I searched the documentation and the
>>> newsgroups trying to understand these problems. I hope I
>>> haven't miss anything and that my questions are relevant.
>>>
>>> I am using the Ganymede Modeling Tools distribution that was out today.
>>>
>>> First, what is the difference between the New and Old Launch
>>> Configurations in Eclipse?
>> The main difference is that old configurations used an old-defined id
>> which was incompatible with the correct plugins id... only a technical
>> issue.
>> We left the old configurations in order to allow users to migrate them
>> to the new ones, using the "Compatibility" menu.
>>
>>> I saw that most examples use the
>>> Old launcher. Should I use the new instead?
>>>
>>> Second, when I use the new launcher and a target model file does not
>>> exist, I get a null pointer exception. Note that
>>> the transformation keeps going and creates the file (apparently
>>> correctly). Subsequent launches don't raise the
>>> exception (or if I create a dummy target file before the 1st launch).
>>> This happens only with the new launcher, and here
>>> is the exception:
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.getSourceMode ls(AtlRegularVM.java:150)
>>>
>>> at
>>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:304)
>>>
>>> at
>>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.runAtlLaunche r(AtlRegularVM.java:426)
>>>
>>> at
>>> org.eclipse.m2m.atl.adt.launching.AtlRegularVM.launch(AtlReg ularVM.java:398)
>>>
>>> at
>>> org.eclipse.m2m.atl.adt.launching.AtlLaunchConfigurationDele gate.launch(AtlLaunchConfigurationDelegate.java:42)
>>>
>>> at
>>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:764)
>>>
>>> at
>>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:614)
>>>
>>> at
>>> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:880)
>>>
>>> at
>>> org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlu gin.java:1083)
>>>
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>
>>>
>> I didn't encounter that bug... if possible, could you attach more
>> details about your example ? Thanks in advance.
>>
>>> Also, I noticed that some features are missing in my installation,
>>> although the plugins are there (and I checked in
>>> Eclipse's configuration details that they were loaded without errors).
>>> Specifically, I am not seeing the menu to inject
>>> KM3 files into an Ecore model (when I click with the right button on a
>>> KM3 file),
>> In fact, KM3 is a GMT project which is not part of the ATL project. The
>> menus you mention are provided by the AM3 plugins.
>>
>>> and I am not being able to use the
>>> debugger (cannot add breakpoints nor run in debug mode). Am I missing
>>> something? Do I have to configure something to be
>>> able to use these features?
>>>
>> The ATL debugger is quite incomplete, the add breakpoints you still must
>> position them in the outline.
>>
>>
>> Best regards,
>>
>> William
|
|
|
Goto Forum:
Current Time: Fri Apr 19 13:07:39 GMT 2024
Powered by FUDForum. Page generated in 0.02453 seconds |
] 
Search
Help
Register
Login
Home
