Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-users] must be obvious
Yes, it does. It seems that your aspects are simply not weavering your classes in your new project structure. If you are using maven to compile the whole project, it must be something related to this compilation. When you use Eclipse to compile your classes AJDT takes care of applying aspect weavering automatically. Reviewing your compilation process might help. 



From: "Conrad CRAMPTON PSE 52704" <conrad.crampton@xxxxxxxxxxxxxxxxxx>
Reply-To: aspectj-users@xxxxxxxxxxx
To: <aspectj-users@xxxxxxxxxxx>
Subject: RE: [aspectj-users] must be obvious
Date: Fri, 27 Oct 2006 13:29:45 +0100
thanks for the response, but the shared classes don't necessarily have the
aspects on them when used by other projects so I don't want to impose that on other uses of the shared classes. The core functionality of the shared classes is the only thing that should be available. The actual aspects (in original project) are advising sub classes of the shared classes. 

e.g.

Orignal Project 1
class A
class B extends A

aspect --
pointcut login(HttpServletRequest request, ActionForm form):
execution(ActionForward *.process(ActionMapping, ActionForm, 
HttpServletRequest, HttpServletResponse)) // actually refers to class A

  && target(B)
  && args(*, form, request, *);
I have moved the common class A to a jar file (along with other common 
classes) with pointcut remaining the same.


Does this help with diagnosis??
Thanks
Conrad


>>> akira_in_tokyo@xxxxxxxxxxx 27/10/06 13:21:33 >>>
I guess what is happening is that you are exporting your classes to 
another

project but you are not exporting the aspects with them. I assume you are
creating a new AspectJ project since you did not report any error in your
new Eclipse project. So I guess just copying aspects will do the job.

A possible reason for this to happen is the following difference:

Scenario 1 ) Original project: Struts classes use classes altered by
aspects.
Scenario 2 ) New project structure: Struts classes use non-altered 
classes.


>From: "Conrad CRAMPTON PSE 52704" <conrad.crampton@xxxxxxxxxxxxxxxxxx>
>Reply-To: aspectj-users@xxxxxxxxxxx
>To: <aspectj-users@xxxxxxxxxxx>
>Subject: [aspectj-users] must be obvious
>Date: Fri, 27 Oct 2006 12:48:14 +0100
>
>Hi,
>I have a struts application which has some common artifacts with other
>projects which have some aspects configures to advise on some of these
>methods - all is fine when I have these common objects in the project
>(Eclipse) as source files. However, I have just extracted these out of
>my project into a new project in order to build a jar file of them
>(using Maven). The application still works in itself but the aspects
>that advise the extracted object methods no longer work.
>
>I can't understand why this is so - can anyone explain this?
>
>Thanks
>Conrad


>_______________________________________________
>aspectj-users mailing list
>aspectj-users@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/aspectj-users

_________________________________________________________________
MSN$(B*T[*` *ヘ Live Search *ノi*サ*オ*ワ*キ http://get.live.com/search/overview

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users






_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users


_________________________________________________________________
MSNサーチ は Live Search に進化します http://get.live.com/search/overview

Back to the top