Eclipse Community Forums: M2T (model-to-text transformation)

Help

Home

Home » Modeling » M2T (model-to-text transformation) » How to debug java extensions?

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

How to debug java extensions? [message #511854]

Wed, 03 February 2010 09:04

Marco

Messages: 216
Registered: August 2009

Senior Member

Hi,

I had to add quite a lot of java code to my Xpand project to manipulate the model before output generation and to facilitate processing while output generation. My problem is the debugging does not work for a workflow, therefore not for Xpand, and not for the java extensions called.

Not even a stack trace shows useable information since it does not go below the level of Xpand declarations. So if e.g. my extension throws a NullPointerException in the third sub routine I get no information where it happened and how it got there.

Is there a way to overcome this shortcoming?

Best regards,
Marco

Report message to a moderator

Re: How to debug java extensions? [message #511889 is a reply to message #511854]

Wed, 03 February 2010 10:31

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

There's a 'java debug' flag in the workflow launch configuration, which
you need to enable.

Sven

arco schrieb:
> Hi,
>
> I had to add quite a lot of java code to my Xpand project to manipulate
> the model before output generation and to facilitate processing while
> output generation. My problem is the debugging does not work for a
> workflow, therefore not for Xpand, and not for the java extensions called.
>
> Not even a stack trace shows useable information since it does not go
> below the level of Xpand declarations. So if e.g. my extension throws a
> NullPointerException in the third sub routine I get no information where
> it happened and how it got there.
>
> Is there a way to overcome this shortcoming?
>
> Best regards,
> Marco

--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Re: How to debug java extensions? [message #512075 is a reply to message #511889]

Wed, 03 February 2010 19:48

Marco

Messages: 216
Registered: August 2009

Senior Member

Sven, thanks for the advice. Now my code can be traced in the debugger.

But still there is no hint where an exception was thrown. The top line of the stack trace just names the extension without information what happened below.

How can I best track down such problems?

br
m

Report message to a moderator

Re: How to debug java extensions? [message #512219 is a reply to message #512075]

Thu, 04 February 2010 12:40

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

I consider it a bug, that exceptions thrown in Java extensions are not
logged properly (please file a bugzilla).

Is that what you're are missing?

Sven

Marco schrieb:
> Sven, thanks for the advice. Now my code can be traced in the debugger.
>
> But still there is no hint where an exception was thrown. The top line
> of the stack trace just names the extension without information what
> happened below.
>
> How can I best track down such problems?
>
> br
> m

--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Re: How to debug java extensions? [message #512260 is a reply to message #512219]

Thu, 04 February 2010 09:26

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

You'll have to call it by its qualified name.
<<EXPAND my::path::TemplateFile::plop FOR this.onePlop>>

Sven

Sven Efftinge schrieb:
> I consider it a bug, that exceptions thrown in Java extensions are not
> logged properly (please file a bugzilla).
>
> Is that what you're are missing?
>
> Sven
>
> Marco schrieb:
>> Sven, thanks for the advice. Now my code can be traced in the debugger.
>>
>> But still there is no hint where an exception was thrown. The top line
>> of the stack trace just names the extension without information what
>> happened below.
>>
>> How can I best track down such problems?
>>
>> br
>> m
>
>

--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Re: How to debug java extensions? [message #512262 is a reply to message #512260]

Thu, 04 February 2010 09:26

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

Sorry wrong thread :-)

Sven Efftinge schrieb:
> You'll have to call it by its qualified name.
> <<EXPAND my::path::TemplateFile::plop FOR this.onePlop>>
>
> Sven
>
> Sven Efftinge schrieb:
>> I consider it a bug, that exceptions thrown in Java extensions are not
>> logged properly (please file a bugzilla).
>>
>> Is that what you're are missing?
>>
>> Sven
>>
>> Marco schrieb:
>>> Sven, thanks for the advice. Now my code can be traced in the debugger.
>>>
>>> But still there is no hint where an exception was thrown. The top
>>> line of the stack trace just names the extension without information
>>> what happened below.
>>>
>>> How can I best track down such problems?
>>>
>>> br
>>> m
>>
>>
>
>

--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Report message to a moderator

Previous Topic:	Neebee question: XMLBeautifier
Next Topic:	[Xpand] Advices not applied

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 23:10:39 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter