Any plan to support per class scope for Introduction in the near future ?
Thx Claude
FYI.,what Aspectwerkz does in this area :
introduction-def name=mixin
interface=examples.introduction.Mixin
implementation=examples.introduction.MixinImpl
Not anytime soon, but come to think of it you could probably implement it with
the current mechanisms, but you'd have to do it yourself...
|
constructionSomeIntroductionFactory.yourPerClassAspect(this.getClass())/construction
|
| |
| | Get me?
| |
| | Bill
View the
1) If you want a singleton mixin, then you can put anything you want in the
construction XML element. So, the mixin reference can be set by calling a method or
setting it to a singleton field of some class.
2) Are you applying the introduction twice? How does C++ work? I want to model
1/OK for the workaround.
Do u think that the scope for a Mixin class could not be supported
at the infrastructure level ?(future version of JBOSS-AOP)
2/ Thx .It does work...FYI ,the full expression for my user-case.
View the original post :
!class($instanceof{org.jboss.aspects.jmx.ReflectedMBean}) AND (has(*
*-@org.jboss.aspects.jmx.ManagedResource(..)) OR
class(@org.jboss.aspects.jmx.ManagedMBean))
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3845764#3845764
Reply to the post :
1) PER-VM and PER-Instance are supported. It would be per-class that would have to be
supported.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3845766#3845766
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3845766
