Hanenberg, S.; Costanza, P.: Connecting Aspects in AspectJ: Strategies vs. Patterns, First Workshop on Aspects, Components, and Patterns for Infrastructure Software at 1st International Conference on AspectOriented Software Development (AOSD), Enschede, April, 2002. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Implementing Known Concepts in AspectJ - Schmidmeier, Hanenberg, Unland (2003) Self-citation (Hanenberg) (Correct)
....AspectJ using introductions AspectJ has a mechanism which is quite similar to mixins. Introductions which are defined within an aspect permit to introduce members or ancestor to a target class or interface. If members are introduced to an interface (that means the container introduction idiom [8] is used) all classes implementing this interface will receive the new introduced members. Figure 2 illustrates the usage of mixins in AspectJ in correspondence to figure 1. An aspect introduces methods to an interface M. The classes implementing receive the method definitions ....
.... the usage of AspectJ mixins permits an non invasive change of the classes to whose inheritance hierarchy the mixins should be applied to: the implementsrelationship between a class and an interface does not need to be defined within the class declaration, but can be introduced by an aspect (see [8] for further discussion) 2.2 Multiple Dispatching In contrast to programming languages like e.g. Cecil [5] which provide multi dispatching Java provides single dispatching: the method to be invoked depends only on the runtime type of the target object. Nevertheless, there are situations where ....
Hanenberg, S.; Costanza, P.: Connecting Aspects in AspectJ: Strategies vs. Patterns, First Workshop on Aspects, Components, and Patterns for Infrastructure Software at 1st International Conference on AspectOriented Software Development (AOSD), Enschede, April, 2002.
Idioms for Building Software Frameworks in AspectJ - Hanenberg, Schmidmeier (2003) (2 citations) Self-citation (Hanenberg) (Correct)
....language designer to become a serious student of the details of the design process [2, p. 460] In this paper we continue to describe idioms which turned out to be used in good designed AspectJ applications and try in this way to encourage the usage of AspectJ in large scale applications. In [4] we already proposed some idioms which were closely related to the language features of AspectJ. Here we propose idioms which seem to be somehow more advanced. The idioms where successfully used in a large scale AspectJ project on Enterprise Application Integration (EAI) systems [9] In [4] we ....
....In [4] we already proposed some idioms which were closely related to the language features of AspectJ. Here we propose idioms which seem to be somehow more advanced. The idioms where successfully used in a large scale AspectJ project on Enterprise Application Integration (EAI) systems [9] In [4] we already discussed the relationship between the proposed idioms and patterns. One of the major points in this discussion was, that the proposed idioms did not have the pattern format. However, in this paper we still neglect to put the idioms in such a format because of two reasons. First, we ....
[Article contains additional citation context not shown here]
Hanenberg, S.; Costanza, P.: Connecting Aspects in AspectJ: Strategies vs. Patterns, First Workshop on Aspects, Components, and Patterns for Infrastructure Software at AOSD'01, Enschede, April, 2002
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC