Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » Debugging AspectJ Compiled Code
Debugging AspectJ Compiled Code [message #23021] Wed, 04 June 2003 19:19 Go to next message
Eclipse UserFriend
Originally posted by: achoi.celeres.biz

Hi All,

When I attempt to debug my AspectJ woven and compiled Java code my Eclipse
IDE shows the incorrect source location of my breakpoint and code
execution.

I understand this is due to the fact that Aspect is weaving additional
code, thus my compiled classes do not match my original source (before
AOP).

I did read somewhere that if I include the "-XnoInline" Aspect compiler
option then this may help me to generate classes that will match closer to
my original source code. However, I'm using Ant 1.5.1 and I have not
found any information on how to code this Aspect compiler option for the
<iajc> tag in my build.xml Ant script.

I'm hoping that I would not have to resort to using Sytem.out or a Logging
API to help me to debug my AOP code.

As a bigger question how are Aspect Technology implementors and
Programmers addressing this debugging issue?

Thanks.
Re: Debugging AspectJ Compiled Code [message #23064 is a reply to message #23021] Wed, 04 June 2003 21:10 Go to previous messageGo to next message
George Harley is currently offline George HarleyFriend
Messages: 70
Registered: July 2009
Member
Hi Alex,

Have you seen what the AJDT FAQ says about debugging AspectJ programs from
within Eclipse ?

http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
type=text/html&cvsroot=Technology_Project#q:debug

With regards to passing the noInline option to the iajc ant task, there is
some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
the Development Guide that ships with the latest AspectJ release.

Best regards,
George

On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
wrote:

> Hi All,
>
> When I attempt to debug my AspectJ woven and compiled Java code my
> Eclipse
> IDE shows the incorrect source location of my breakpoint and code
> execution.
>
> I understand this is due to the fact that Aspect is weaving additional
> code, thus my compiled classes do not match my original source (before
> AOP).
>
> I did read somewhere that if I include the "-XnoInline" Aspect compiler
> option then this may help me to generate classes that will match closer
> to
> my original source code. However, I'm using Ant 1.5.1 and I have not
> found any information on how to code this Aspect compiler option for the
> <iajc> tag in my build.xml Ant script.
>
> I'm hoping that I would not have to resort to using Sytem.out or a
> Logging
> API to help me to debug my AOP code.
>
> As a bigger question how are Aspect Technology implementors and
> Programmers addressing this debugging issue?
>
> Thanks.
>
>

--
George
Re: Debugging AspectJ Compiled Code [message #23187 is a reply to message #23064] Thu, 05 June 2003 18:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: achoi.celeres.biz

Hi George,

Thank you for your helpful reply.

I checked out link that you mentioned and the AspectJ Ant Tasks. I found
the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
somewhere that the AspectJ docs are not bundled with the current 1.1.2
release.

I found out to pass the -XnoInline AspectJ compiler option through Ant is
by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
hope this helps anyone else who may have the same question.

I proceeded with building, and deploying my J2EE application with the
applied (generated) Aspect code. I used the -XnoInline option to allow
me to debug my code. But when I debug my code I see that Eclipse (my
version is 2.1) is not stepping through my source correctly. At this
point I\'m thinking that the -XnoInline option is not working. As a
double-check I decompile my class that I want to debug twice, one without
and with the -XnoInline. In both cases the decompile code is the same.
So it looks like this no line Aspect compiler option does not work (for me
at least). In the past I can use Eclipe to debug non-Aspect Oriented code
running in the Servlet and EJB container without problems. Maybe there is
something else I set somewhere.

I hope someelse may have any other suggestions.

Thanks everyone.



George Harley wrote:

> Hi Alex,

> Have you seen what the AJDT FAQ says about debugging AspectJ programs from
> within Eclipse ?

>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> type=text/html&cvsroot=Technology_Project#q:debug

> With regards to passing the noInline option to the iajc ant task, there is
> some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
> the Development Guide that ships with the latest AspectJ release.

> Best regards,
> George

> On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> wrote:

> > Hi All,
> >
> > When I attempt to debug my AspectJ woven and compiled Java code my
> > Eclipse
> > IDE shows the incorrect source location of my breakpoint and code
> > execution.
> >
> > I understand this is due to the fact that Aspect is weaving additional
> > code, thus my compiled classes do not match my original source (before
> > AOP).
> >
> > I did read somewhere that if I include the \"-XnoInline\" Aspect compiler
> > option then this may help me to generate classes that will match closer
> > to
> > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > found any information on how to code this Aspect compiler option for the
> > <iajc> tag in my build.xml Ant script.
> >
> > I\'m hoping that I would not have to resort to using Sytem.out or a
> > Logging
> > API to help me to debug my AOP code.
> >
> > As a bigger question how are Aspect Technology implementors and
> > Programmers addressing this debugging issue?
> >
> > Thanks.
> >
> >

> --
> George
Re: Debugging AspectJ Compiled Code [message #23220 is a reply to message #23187] Thu, 05 June 2003 19:10 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: achoi.celeres.biz

I like to add another comment. I understand that when the future version
of Eclipse implements JSR-45 then this will resolve my issue and every
AspectJ Programmer. In the meantime is there way to use Eclipse or any
other easy to use visual source Java debugger tool to debug an Aspect Java
code?

Thanks.


Alex choi wrote:

> Hi George,

> Thank you for your helpful reply.

> I checked out link that you mentioned and the AspectJ Ant Tasks. I found
> the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
> somewhere that the AspectJ docs are not bundled with the current 1.1.2
> release.

> I found out to pass the -XnoInline AspectJ compiler option through Ant is
> by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
> hope this helps anyone else who may have the same question.

> I proceeded with building, and deploying my J2EE application with the
> applied (generated) Aspect code. I used the -XnoInline option to allow
> me to debug my code. But when I debug my code I see that Eclipse (my
> version is 2.1) is not stepping through my source correctly. At this
> point I\'m thinking that the -XnoInline option is not working. As a
> double-check I decompile my class that I want to debug twice, one without
> and with the -XnoInline. In both cases the decompile code is the same.
> So it looks like this no line Aspect compiler option does not work (for me
> at least). In the past I can use Eclipe to debug non-Aspect Oriented code
> running in the Servlet and EJB container without problems. Maybe there is
> something else I set somewhere.

> I hope someelse may have any other suggestions.

> Thanks everyone.



> George Harley wrote:

> > Hi Alex,

> > Have you seen what the AJDT FAQ says about debugging AspectJ programs from
> > within Eclipse ?

> >
>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> > type=text/html&cvsroot=Technology_Project#q:debug

> > With regards to passing the noInline option to the iajc ant task, there is
> > some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
> > the Development Guide that ships with the latest AspectJ release.

> > Best regards,
> > George

> > On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> > wrote:

> > > Hi All,
> > >
> > > When I attempt to debug my AspectJ woven and compiled Java code my
> > > Eclipse
> > > IDE shows the incorrect source location of my breakpoint and code
> > > execution.
> > >
> > > I understand this is due to the fact that Aspect is weaving additional
> > > code, thus my compiled classes do not match my original source (before
> > > AOP).
> > >
> > > I did read somewhere that if I include the \"-XnoInline\" Aspect compiler
> > > option then this may help me to generate classes that will match closer
> > > to
> > > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > > found any information on how to code this Aspect compiler option for the
> > > <iajc> tag in my build.xml Ant script.
> > >
> > > I\'m hoping that I would not have to resort to using Sytem.out or a
> > > Logging
> > > API to help me to debug my AOP code.
> > >
> > > As a bigger question how are Aspect Technology implementors and
> > > Programmers addressing this debugging issue?
> > >
> > > Thanks.
> > >
> > >

> > --
> > George
Re: Debugging AspectJ Compiled Code [message #23263 is a reply to message #23220] Thu, 05 June 2003 23:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: achoi.celeres.biz

Debugging Aspect code using Eclipse works for me!

I placed the <iajc> X option in the correct location. I can use Eclipse
IDE to trace through my code. There is a minor annoyance that the Eclipse
debugger jumps around a few lines (depending on the size of the woven
Aspect code) when an Aspect code is being trace through. Eclipse is sync
with your source once it hits your code again.

Thanks you for your help.

Alex Choi wrote:

> I like to add another comment. I understand that when the future version
> of Eclipse implements JSR-45 then this will resolve my issue and every
> AspectJ Programmer. In the meantime is there way to use Eclipse or any
> other easy to use visual source Java debugger tool to debug an Aspect Java
> code?

> Thanks.


> Alex choi wrote:

> > Hi George,

> > Thank you for your helpful reply.

> > I checked out link that you mentioned and the AspectJ Ant Tasks. I found
> > the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
> > somewhere that the AspectJ docs are not bundled with the current 1.1.2
> > release.

> > I found out to pass the -XnoInline AspectJ compiler option through Ant is
> > by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
> > hope this helps anyone else who may have the same question.

> > I proceeded with building, and deploying my J2EE application with the
> > applied (generated) Aspect code. I used the -XnoInline option to allow
> > me to debug my code. But when I debug my code I see that Eclipse (my
> > version is 2.1) is not stepping through my source correctly. At this
> > point I\'m thinking that the -XnoInline option is not working. As a
> > double-check I decompile my class that I want to debug twice, one without
> > and with the -XnoInline. In both cases the decompile code is the same.
> > So it looks like this no line Aspect compiler option does not work (for me
> > at least). In the past I can use Eclipe to debug non-Aspect Oriented code
> > running in the Servlet and EJB container without problems. Maybe there is
> > something else I set somewhere.

> > I hope someelse may have any other suggestions.

> > Thanks everyone.



> > George Harley wrote:

> > > Hi Alex,

> > > Have you seen what the AJDT FAQ says about debugging AspectJ programs
from
> > > within Eclipse ?

> > >
> >
>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> > > type=text/html&cvsroot=Technology_Project#q:debug

> > > With regards to passing the noInline option to the iajc ant task, there
is
> > > some information on setting -X options in chapter 2 (AspectJ Ant Tasks)
of
> > > the Development Guide that ships with the latest AspectJ release.

> > > Best regards,
> > > George

> > > On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> > > wrote:

> > > > Hi All,
> > > >
> > > > When I attempt to debug my AspectJ woven and compiled Java code my
> > > > Eclipse
> > > > IDE shows the incorrect source location of my breakpoint and code
> > > > execution.
> > > >
> > > > I understand this is due to the fact that Aspect is weaving additional
> > > > code, thus my compiled classes do not match my original source (before
> > > > AOP).
> > > >
> > > > I did read somewhere that if I include the \"-XnoInline\" Aspect
compiler
> > > > option then this may help me to generate classes that will match
closer
> > > > to
> > > > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > > > found any information on how to code this Aspect compiler option for
the
> > > > <iajc> tag in my build.xml Ant script.
> > > >
> > > > I\'m hoping that I would not have to resort to using Sytem.out or a
> > > > Logging
> > > > API to help me to debug my AOP code.
> > > >
> > > > As a bigger question how are Aspect Technology implementors and
> > > > Programmers addressing this debugging issue?
> > > >
> > > > Thanks.
> > > >
> > > >

> > > --
> > > George
Re: Debugging AspectJ Compiled Code [message #23985 is a reply to message #23263] Mon, 23 June 2003 15:15 Go to previous message
Eclipse UserFriend
Originally posted by: skadam.us.nomura.com

Alex,
I am trying to use aspect in my EJB and Servlet, I don't even see my
aspect getting executed.
Can you please tell me what i have to do in term of the App Server.

I have included the .class generated from Aspect in my .ear file and
running
the app server with aspectjrt.jar in the classpath too.

Thanks
Sal
Re: Debugging AspectJ Compiled Code [message #568166 is a reply to message #23021] Wed, 04 June 2003 21:10 Go to previous message
George Harley is currently offline George HarleyFriend
Messages: 70
Registered: July 2009
Member
Hi Alex,

Have you seen what the AJDT FAQ says about debugging AspectJ programs from
within Eclipse ?

http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
type=text/html&cvsroot=Technology_Project#q:debug

With regards to passing the noInline option to the iajc ant task, there is
some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
the Development Guide that ships with the latest AspectJ release.

Best regards,
George

On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
wrote:

> Hi All,
>
> When I attempt to debug my AspectJ woven and compiled Java code my
> Eclipse
> IDE shows the incorrect source location of my breakpoint and code
> execution.
>
> I understand this is due to the fact that Aspect is weaving additional
> code, thus my compiled classes do not match my original source (before
> AOP).
>
> I did read somewhere that if I include the "-XnoInline" Aspect compiler
> option then this may help me to generate classes that will match closer
> to
> my original source code. However, I'm using Ant 1.5.1 and I have not
> found any information on how to code this Aspect compiler option for the
> <iajc> tag in my build.xml Ant script.
>
> I'm hoping that I would not have to resort to using Sytem.out or a
> Logging
> API to help me to debug my AOP code.
>
> As a bigger question how are Aspect Technology implementors and
> Programmers addressing this debugging issue?
>
> Thanks.
>
>

--
George
Re: Debugging AspectJ Compiled Code [message #568335 is a reply to message #23064] Thu, 05 June 2003 18:54 Go to previous message
Eclipse UserFriend
Originally posted by: achoi.celeres.biz

Hi George,

Thank you for your helpful reply.

I checked out link that you mentioned and the AspectJ Ant Tasks. I found
the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
somewhere that the AspectJ docs are not bundled with the current 1.1.2
release.

I found out to pass the -XnoInline AspectJ compiler option through Ant is
by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
hope this helps anyone else who may have the same question.

I proceeded with building, and deploying my J2EE application with the
applied (generated) Aspect code. I used the -XnoInline option to allow
me to debug my code. But when I debug my code I see that Eclipse (my
version is 2.1) is not stepping through my source correctly. At this
point I\'m thinking that the -XnoInline option is not working. As a
double-check I decompile my class that I want to debug twice, one without
and with the -XnoInline. In both cases the decompile code is the same.
So it looks like this no line Aspect compiler option does not work (for me
at least). In the past I can use Eclipe to debug non-Aspect Oriented code
running in the Servlet and EJB container without problems. Maybe there is
something else I set somewhere.

I hope someelse may have any other suggestions.

Thanks everyone.



George Harley wrote:

> Hi Alex,

> Have you seen what the AJDT FAQ says about debugging AspectJ programs from
> within Eclipse ?

>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> type=text/html&cvsroot=Technology_Project#q:debug

> With regards to passing the noInline option to the iajc ant task, there is
> some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
> the Development Guide that ships with the latest AspectJ release.

> Best regards,
> George

> On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> wrote:

> > Hi All,
> >
> > When I attempt to debug my AspectJ woven and compiled Java code my
> > Eclipse
> > IDE shows the incorrect source location of my breakpoint and code
> > execution.
> >
> > I understand this is due to the fact that Aspect is weaving additional
> > code, thus my compiled classes do not match my original source (before
> > AOP).
> >
> > I did read somewhere that if I include the \"-XnoInline\" Aspect compiler
> > option then this may help me to generate classes that will match closer
> > to
> > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > found any information on how to code this Aspect compiler option for the
> > <iajc> tag in my build.xml Ant script.
> >
> > I\'m hoping that I would not have to resort to using Sytem.out or a
> > Logging
> > API to help me to debug my AOP code.
> >
> > As a bigger question how are Aspect Technology implementors and
> > Programmers addressing this debugging issue?
> >
> > Thanks.
> >
> >

> --
> George
Re: Debugging AspectJ Compiled Code [message #568377 is a reply to message #23187] Thu, 05 June 2003 19:10 Go to previous message
Alex Choi is currently offline Alex ChoiFriend
Messages: 4
Registered: July 2009
Junior Member
I like to add another comment. I understand that when the future version
of Eclipse implements JSR-45 then this will resolve my issue and every
AspectJ Programmer. In the meantime is there way to use Eclipse or any
other easy to use visual source Java debugger tool to debug an Aspect Java
code?

Thanks.


Alex choi wrote:

> Hi George,

> Thank you for your helpful reply.

> I checked out link that you mentioned and the AspectJ Ant Tasks. I found
> the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
> somewhere that the AspectJ docs are not bundled with the current 1.1.2
> release.

> I found out to pass the -XnoInline AspectJ compiler option through Ant is
> by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
> hope this helps anyone else who may have the same question.

> I proceeded with building, and deploying my J2EE application with the
> applied (generated) Aspect code. I used the -XnoInline option to allow
> me to debug my code. But when I debug my code I see that Eclipse (my
> version is 2.1) is not stepping through my source correctly. At this
> point I\'m thinking that the -XnoInline option is not working. As a
> double-check I decompile my class that I want to debug twice, one without
> and with the -XnoInline. In both cases the decompile code is the same.
> So it looks like this no line Aspect compiler option does not work (for me
> at least). In the past I can use Eclipe to debug non-Aspect Oriented code
> running in the Servlet and EJB container without problems. Maybe there is
> something else I set somewhere.

> I hope someelse may have any other suggestions.

> Thanks everyone.



> George Harley wrote:

> > Hi Alex,

> > Have you seen what the AJDT FAQ says about debugging AspectJ programs from
> > within Eclipse ?

> >
>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> > type=text/html&cvsroot=Technology_Project#q:debug

> > With regards to passing the noInline option to the iajc ant task, there is
> > some information on setting -X options in chapter 2 (AspectJ Ant Tasks) of
> > the Development Guide that ships with the latest AspectJ release.

> > Best regards,
> > George

> > On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> > wrote:

> > > Hi All,
> > >
> > > When I attempt to debug my AspectJ woven and compiled Java code my
> > > Eclipse
> > > IDE shows the incorrect source location of my breakpoint and code
> > > execution.
> > >
> > > I understand this is due to the fact that Aspect is weaving additional
> > > code, thus my compiled classes do not match my original source (before
> > > AOP).
> > >
> > > I did read somewhere that if I include the \"-XnoInline\" Aspect compiler
> > > option then this may help me to generate classes that will match closer
> > > to
> > > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > > found any information on how to code this Aspect compiler option for the
> > > <iajc> tag in my build.xml Ant script.
> > >
> > > I\'m hoping that I would not have to resort to using Sytem.out or a
> > > Logging
> > > API to help me to debug my AOP code.
> > >
> > > As a bigger question how are Aspect Technology implementors and
> > > Programmers addressing this debugging issue?
> > >
> > > Thanks.
> > >
> > >

> > --
> > George
Re: Debugging AspectJ Compiled Code [message #568444 is a reply to message #23220] Thu, 05 June 2003 23:36 Go to previous message
Alex Choi is currently offline Alex ChoiFriend
Messages: 4
Registered: July 2009
Junior Member
Debugging Aspect code using Eclipse works for me!

I placed the <iajc> X option in the correct location. I can use Eclipse
IDE to trace through my code. There is a minor annoyance that the Eclipse
debugger jumps around a few lines (depending on the size of the woven
Aspect code) when an Aspect code is being trace through. Eclipse is sync
with your source once it hits your code again.

Thanks you for your help.

Alex Choi wrote:

> I like to add another comment. I understand that when the future version
> of Eclipse implements JSR-45 then this will resolve my issue and every
> AspectJ Programmer. In the meantime is there way to use Eclipse or any
> other easy to use visual source Java debugger tool to debug an Aspect Java
> code?

> Thanks.


> Alex choi wrote:

> > Hi George,

> > Thank you for your helpful reply.

> > I checked out link that you mentioned and the AspectJ Ant Tasks. I found
> > the AspectJ Ant Tasks documentation in the AspectJ 1.0.6 bundled. I read
> > somewhere that the AspectJ docs are not bundled with the current 1.1.2
> > release.

> > I found out to pass the -XnoInline AspectJ compiler option through Ant is
> > by the X=\"<option 1>,<option 2>,...\" attribute in the <iajc> tag. I
> > hope this helps anyone else who may have the same question.

> > I proceeded with building, and deploying my J2EE application with the
> > applied (generated) Aspect code. I used the -XnoInline option to allow
> > me to debug my code. But when I debug my code I see that Eclipse (my
> > version is 2.1) is not stepping through my source correctly. At this
> > point I\'m thinking that the -XnoInline option is not working. As a
> > double-check I decompile my class that I want to debug twice, one without
> > and with the -XnoInline. In both cases the decompile code is the same.
> > So it looks like this no line Aspect compiler option does not work (for me
> > at least). In the past I can use Eclipe to debug non-Aspect Oriented code
> > running in the Servlet and EJB container without problems. Maybe there is
> > something else I set somewhere.

> > I hope someelse may have any other suggestions.

> > Thanks everyone.



> > George Harley wrote:

> > > Hi Alex,

> > > Have you seen what the AJDT FAQ says about debugging AspectJ programs
from
> > > within Eclipse ?

> > >
> >
>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.ajdt/faq.html?rev=1.2&content-
> > > type=text/html&cvsroot=Technology_Project#q:debug

> > > With regards to passing the noInline option to the iajc ant task, there
is
> > > some information on setting -X options in chapter 2 (AspectJ Ant Tasks)
of
> > > the Development Guide that ships with the latest AspectJ release.

> > > Best regards,
> > > George

> > > On Wed, 4 Jun 2003 19:19:56 +0000 (UTC), Alex Choi <achoi@celeres.biz>
> > > wrote:

> > > > Hi All,
> > > >
> > > > When I attempt to debug my AspectJ woven and compiled Java code my
> > > > Eclipse
> > > > IDE shows the incorrect source location of my breakpoint and code
> > > > execution.
> > > >
> > > > I understand this is due to the fact that Aspect is weaving additional
> > > > code, thus my compiled classes do not match my original source (before
> > > > AOP).
> > > >
> > > > I did read somewhere that if I include the \"-XnoInline\" Aspect
compiler
> > > > option then this may help me to generate classes that will match
closer
> > > > to
> > > > my original source code. However, I\'m using Ant 1.5.1 and I have not
> > > > found any information on how to code this Aspect compiler option for
the
> > > > <iajc> tag in my build.xml Ant script.
> > > >
> > > > I\'m hoping that I would not have to resort to using Sytem.out or a
> > > > Logging
> > > > API to help me to debug my AOP code.
> > > >
> > > > As a bigger question how are Aspect Technology implementors and
> > > > Programmers addressing this debugging issue?
> > > >
> > > > Thanks.
> > > >
> > > >

> > > --
> > > George
Re: Debugging AspectJ Compiled Code [message #569226 is a reply to message #23263] Mon, 23 June 2003 15:15 Go to previous message
Eclipse UserFriend
Originally posted by: skadam.us.nomura.com

Alex,
I am trying to use aspect in my EJB and Servlet, I don't even see my
aspect getting executed.
Can you please tell me what i have to do in term of the App Server.

I have included the .class generated from Aspect in my .ear file and
running
the app server with aspectjrt.jar in the classpath too.

Thanks
Sal
Previous Topic:1.1.3 installation broken on linux
Next Topic:Newbie Eclipse AJDT Install Question
Goto Forum:
  


Current Time: Tue Mar 19 11:16:21 GMT 2024

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

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

Back to the top