| Extending the JDT debugger [message #255424] |
Mon, 04 August 2008 10:35  |
Eclipse User |
|
|
|
Originally posted by: pschoenb.gmx.de
Hi,
in a MDSD context, we would like to extend the JDT debugger as follows:
We have some tracing information that tells us which generated Java
method has been generated by which metaclass of the model. Now, we would
like to set a breakpoint in the model editor at a metaclass which shows
a textual representation of the model. When setting this breakpoint, a
breakpoint should be set at every Java method that has been generated
from this metaclass. However, when code execution reaches the
breakpoint, we would like our model to be shown, not the Java source.
Is it possible to extend the JDT debugger like this? If so, are there
any documentation sources that explain how to extend the JDT debugger?
--
Regards,
Patrick
|
|
|
| Re: Extending the JDT debugger [message #255446 is a reply to message #255424] |
Tue, 05 August 2008 03:31  |
| Eclipse User |
|
|
|
Morgen Patrick,
We were in a very similar situation, having written an Eclipse Debugger
implementation for a langauge which is compiled to Java bytecode.
We, however, did not take your approach, rather we drive the Java
debugging agent directly using JDI/JDWP. We therefore have no JDT
dependency, but the quantity of work required to implement everything,
and the sheer complexity of the source is 'quite significant'. But
having written an implementation of Eclipse debugging, we are able to
finely control the source code display, breakpoints, watches, exceptions
etc.
I don't know if it's possible to extend the JDT debugger in this way -
though if it does (and it provides all the extension points you need),
then I would recommend doing it this way. But I suspect you'll come
across some corner case that doesn't quite work and you might end up in
the Do-It-Yourself method anyway.
In any case: good luck.
MfG,
-John
Patrick Schoenbach wrote:
> Hi,
>
> in a MDSD context, we would like to extend the JDT debugger as follows:
> We have some tracing information that tells us which generated Java
> method has been generated by which metaclass of the model. Now, we would
> like to set a breakpoint in the model editor at a metaclass which shows
> a textual representation of the model. When setting this breakpoint, a
> breakpoint should be set at every Java method that has been generated
> from this metaclass. However, when code execution reaches the
> breakpoint, we would like our model to be shown, not the Java source.
>
> Is it possible to extend the JDT debugger like this? If so, are there
> any documentation sources that explain how to extend the JDT debugger?
>
|
|
|
| Re: Extending the JDT debugger [message #257714 is a reply to message #255424] |
Mon, 08 December 2008 15:50 |
| Eclipse User |
|
|
|
Originally posted by: misiak7.gmail.com
Patrick Schoenbach wrote / napísal(a):
> Hi,
>
> in a MDSD context, we would like to extend the JDT debugger as follows:
> We have some tracing information that tells us which generated Java
> method has been generated by which metaclass of the model. Now, we would
> like to set a breakpoint in the model editor at a metaclass which shows
> a textual representation of the model. When setting this breakpoint, a
> breakpoint should be set at every Java method that has been generated
> from this metaclass. However, when code execution reaches the
> breakpoint, we would like our model to be shown, not the Java source.
>
> Is it possible to extend the JDT debugger like this? If so, are there
> any documentation sources that explain how to extend the JDT debugger?
>
Hi Patrick,
I have a similar objective to include some java classes to classes
generated from metamodel. Did you do some progress in extending of
original java debugger with your issue? Thanks.
Michal Antolik
|
|
|
Powered by
FUDForum. Page generated in 0.03518 seconds
Home