-
assigned issue to
Operation(s) not woven again when class mapped multiple times
Issue #112
resolved
Steps to reproduce:
- Create new aspect
- Create two classes
- Instantiate Command
- Map Command to both classes
- Weave
Expected Result:
Both classes have the execute method.
Actual Result:
Only one of them has the execute method.
It worked in v2.1.0 and is broken in v2.2.1.
Comments (2)
-
reporter -
reporter - changed status to resolved
Resolved in commit 7e9d167. Due to previous changes in the mappings, when trying to weave an operation a second time (because the class is mapped), there is a mapping already and the operation is not woven again.
Now instead the weaving information is used and made sure that if the operation was woven, the containing class also matches.
- Log in to comment