Browse Prior Art Database

Solution Level aspects

IP.com Disclosure Number: IPCOM000032445D
Original Publication Date: 2004-Nov-05
Included in the Prior Art Database: 2004-Nov-05
Document File: 1 page(s) / 41K

Publishing Venue

IBM

Abstract

Cross-cutting of concerns has been analysed for some period of time. However, until now people have only looked at the cross-cutting of programming concerns i.e. they only tackle it from the bottom up. What is discussed here is a way to raise this up to a higher level of abstraction, where you can talk about 'solution-level' artifacts instead of 'code-level' artifacts.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 1

Solution Level aspects

Cross-cutting of concerns has been analysed for some period of time. However, until now people have only looked at the cross-cutting of programming concerns i.e. they only tackle it from the bottom up. This is known as aspect oriented programming.

    This is not acceptable from a business users point of view. They have no knowledge of programming languages and low-level constructs. They only speak at a much higher level e.g. "audit trails" or "business events".

    In addition to this issue, the programming language is not a good way to consider aspects as we move forward into the solution space. A solution is made of many different artifacts e.g. EJBs, database accesses, Queue accesses, C code, Java code, VB script etc. Current aspect technologies do not try to interact in this multi-environment space.

    Proposed is a combination of a language to define the aspects and an engine that understands (parses) that language to create the new aspect "code" for the given solution. The engine can then work in one of four ways:
1.It can manipulate the solution artifacts in order to place the generated aspect "code" into the artifacts (thereby creating new artifacts with "inline code" that represent the aspect function).

OR
2) It can manipulate the solution artifacts and add in "exit" points to newly created aspect artifacts. This is subtly different from 1)

OR
3) The engine can create entirely new artifacts which can be published with the solution. These artifacts can sit in strategic areas of the solution platform an...