jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
AspectWerkz
  • AspectWerkz
  • AW-257

privileged aspect

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: cool-ideas
  • Component/s: core
  • Labels:
    None
  • Number of attachments :
    0

Description

privileged aspect

PAspect {
@Privileged
@Target | @This
int m_field;

@Priviledged
@Target | @This
int foo()

{return <fakeReturned>;}

//could be abstract + abstract aspect and removal of abstraction
// thru aspect weaving

@Around(pc)
... myAdvice(..)

{ m_field = 3; foo(...); }

}

We change the aspect bytecode to change the field access and method access instruction to call them on target or this instead.
We may need wrapper for private stuff in both caller and callee then.
So we need to match pc from both a caller and callee side point of view.

note: what if modifier in aspect fake method / field are not the same as in target / this class ?
note: what if method does not EXIST in targt / this class [silly user but..]

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Alexandre Vasseur
Vote (0)
Watch (0)

Dates

  • Created:
    10/Sep/04 6:06 AM
    Updated:
    17/Nov/04 6:25 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.