Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » M2T (model-to-text transformation) » debugging one's custom tags
debugging one's custom tags [message #41414] Wed, 06 February 2008 17:57 Go to next message
Edoardo Comar is currently offline Edoardo ComarFriend
Messages: 102
Registered: July 2009
Senior Member
I was hoping to launch my usual transformation in 'debug' mode rather
than 'run' and to be able to set breakpoints in my custom tags code.

I can't see a way to do this.
Am I missing something ?
What do the JET developers do ?

Edoardo
Re: debugging one's custom tags [message #41517 is a reply to message #41414] Thu, 07 February 2008 16:20 Go to previous messageGo to next message
Paul Elder is currently offline Paul ElderFriend
Messages: 849
Registered: July 2009
Senior Member
Edoardo:

No, there is no debug mode. (Are there any volunteers to write a JET
debugger?)

If, as your subject line suggests, you are debugging custom tags, launch a
'runtime' workbench (in debug), and put break points in the JET tag handler
methods you are working on. Then run a JET transformation from that runtime
workbench. Note that the JET transformation can be in you development
workbench - it is a plug-in, and can be included in the runtime workbench as
any other.

Other things I do for debugging are:

1) use <c:log></c:log> to write debug messages in my templates.

2) In the jet launch config, set the logging level to trace or debug - this
generates a whole lot more information on the execution consule. (The
utility of that information may be debated.)

It has been several years since I have put breakpoints directly in the Java
code generated from a template (but then, I never write in-line Java
scriptlets or expressions).

Paul

"Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
news:focsdl$kpi$1@build.eclipse.org...
>I was hoping to launch my usual transformation in 'debug' mode rather than
>'run' and to be able to set breakpoints in my custom tags code.
>
> I can't see a way to do this.
> Am I missing something ?
> What do the JET developers do ?
>
> Edoardo
Re: debugging one's custom tags [message #41642 is a reply to message #41517] Fri, 08 February 2008 12:43 Go to previous message
Edoardo Comar is currently offline Edoardo ComarFriend
Messages: 102
Registered: July 2009
Senior Member
Thanks I managed to debug!

Paul Elder wrote:
> Edoardo:
>
> No, there is no debug mode. (Are there any volunteers to write a JET
> debugger?)
>
> If, as your subject line suggests, you are debugging custom tags, launch a
> 'runtime' workbench (in debug), and put break points in the JET tag handler
> methods you are working on. Then run a JET transformation from that runtime
> workbench. Note that the JET transformation can be in you development
> workbench - it is a plug-in, and can be included in the runtime workbench as
> any other.
>
> Other things I do for debugging are:
>
> 1) use <c:log></c:log> to write debug messages in my templates.
>
> 2) In the jet launch config, set the logging level to trace or debug - this
> generates a whole lot more information on the execution consule. (The
> utility of that information may be debated.)
>
> It has been several years since I have put breakpoints directly in the Java
> code generated from a template (but then, I never write in-line Java
> scriptlets or expressions).
>
> Paul
>
> "Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
> news:focsdl$kpi$1@build.eclipse.org...
>> I was hoping to launch my usual transformation in 'debug' mode rather than
>> 'run' and to be able to set breakpoints in my custom tags code.
>>
>> I can't see a way to do this.
>> Am I missing something ?
>> What do the JET developers do ?
>>
>> Edoardo
>
>
Previous Topic:ANT Task for JET
Next Topic:Any JET2 sample with Java object input ?
Goto Forum:
  


Current Time: Tue Apr 23 09:32:33 GMT 2024

Powered by FUDForum. Page generated in 0.03990 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top