[aspectwerkz-dev] [jira] Deleted: (AW-152) aspect reuse is bogus when named pc is only def in xml

     [ http://jira.codehaus.org/browse/AW-152?page=3Dcom.atlassian.jira.plu=
gin.system.issuetabpanels:all-tabpanel ]

[email protected] deleted AW-152:
---------------------------------


> aspect reuse is bogus when named pc is only def in xml
> ------------------------------------------------------
>
>                 Key: AW-152
>                 URL: http://jira.codehaus.org/browse/AW-152
>             Project: AspectWerkz
>          Issue Type: Bug
>            Reporter: Alexandre Vasseur
>            Assignee: Alexandre Vasseur
>          Time Spent: 1 hour
>  Remaining Estimate: 0 minutes
>
> Alex wrote:
> >if pointcut are defined in XML but advice is not
> >so only with named pc like
> >
> >MyAspect:
> >Aspect {
> >@Around(somePC)
> >.. theAdviceMethod(..) {..}
> >}
> >xml:
> ><aspect ...>
> >  <pointcut name=3DsomePC expression=3D../>
> >  <!-- no binding there -->
> ></aspect>
> >
> >then what should we do (how should we fail / ignore / warn) when a named
> >pointcut is "still not defined" ?
> > =20
> >
> Well semantically speaking if would mean we've got a pointcut but=20
> nothing to do when reaching the
> pointcut... I do not really see anything wrong with that. Probably a=20
> warning would be nice 'cause
> this would probably be due to a lazy programmer mistake.
> Otherwise how can I easily write re-usable aspects?
> BTW, do the attributes are "inherited" betweens hierarchies of aspects?=
=20
> I mean if I have some
> attributes on abstract aspect A, do aspect B extending A "inherit" the=20
> attributes definitions?
> J=E9r=F4me.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email