Abstract: The invention, which may be a kind of annotations processor, detects zero or more tagsets turned on or selected at runtime. The annotations adapter reads an abstract unit from a java file, and if an annotation of the abstract unit has a tag that is among the tags of a turned on tagset, then the annotations adapter may generate an artifact showing the influence of the annotation. Such a process may continue until there are no more abstract units to process. Comments or annotations that fail to be tagged with a tag of a selected tagset may, nevertheless, be mentioned with a kind of ‘place-holder’ indicating that such comments exist.

Abstract: A method, an apparatus, and computer instructions are provided for extending operations of an application in a data processing system. A primary operation is executed. All extended operations of the primary operation are cached and pre and post operation identifiers are identified. For each pre operation identifier, a pre operation instance is created and executed. For each post operation identifier, a post operation instance is created and executed.

Abstract: A method, an apparatus, and computer instructions are provided for extending operations of an application in a data processing system. A primary operation is executed. All extended operations of the primary operation are cached and pre and post operation identifiers are identified. For each pre operation identifier, a pre operation instance is created and executed. For each post operation identifier, a post operation instance is created and executed.

Abstract: A situation object instantiator (SOI) receives a request from a client including a typekey. Available situations are retrieved. For a retrieved situation, a call to an evaluator is made. If the situation is active a check is made to see if an instantiator exists for the typekey and situation. If so, the object instantiator is called, it returns an instance to the SOI, and the SOI returns the instance to the client. If not, more situations are retrieved until the situations are exhausted, and such is communicated to the client.

Abstract: A method, apparatus, and computer instructions for defining queries in terms of data objects. A simplified query syntax is introduced for querying across a set of data objects which does not require the duplication of data object shape information. A data object is first defined by providing a name for the data object. Attribute and relationship information is added to the data object, wherein the information defines the shape of the data object. When a query is created, it is defined in terms of data objects. The query is processed, wherein processing the query includes extracting the shape of the data objects using the attribute information in the query. The query is expanded by adding additional syntax to the query based on relationship information defined for the data objects and then executed in its expanded form.

Abstract: A method and apparatus for generating a service data object based service pattern for an EJB model is provided. Definitions of session bean façade, SDOs, and queries are defined in entity beans. When the definitions are processed, SDOs, related SDOs, and queries for SDOs are added to the session bean façade. At run time, a client may manipulate the SDOs and apply changes to the SDOs via a mediator obtained from a mediator cache. The mediator persists the SDOs to a data graph without interfering the entity bean.

Abstract: A method, an apparatus, and computer instructions are provided for implementing dynamic function groups in a data processing system. An extensible framework is provided, which provides function groups to amalgamate extended sets of functionality by either vendor or purpose and allows the function groups to be dynamically enabled or disabled within a software application. A user may specify which extended sets of functionality are relevant and when to enable them. With the use of function groups, third party vendors may integrate added functionalities with existing ones in a software application, and indicate when these functionalities should be available to end-users without the need to duplicate code. The invention allows for the construction of other extensible frameworks including wizards, editors, and operations may also be extended with the use of function groups.

Abstract: A method and apparatus is provided for annotation-based behavior extensions. A primary contributor is identified based on a first attribute. Behaviors from a secondary contributor are linked to the primary contributor once a second attribute is examined. Finally, one or more files are generated using the linked behaviors from the primary and secondary contributors.

Abstract: A method and system for incrementally processing program annotations is provided. A source model, a doclet model and a semantic model are used to represent and transform annotations incrementally. The source model represents actual types, fields, and methods that contain annotations. The doclet model includes doclet objects representing tags and attributes for a type, field, and method for a given namespace. Tag handlers registered for the given namespace detect changes in annotations and create or update doclet objects based on the changes. Changes in the doclet model are then transformed into the semantic model and may be persisted for restoration.

Abstract: A method, an apparatus, and computer instructions are provided for extending operations of an application in a data processing system. A primary operation is executed. All extended operations of the primary operation are cached and pre and post operation identifiers are identified. For each pre operation identifier, a pre operation instance is created and executed. For each post operation identifier, a post operation instance is created and executed.

Abstract: A method, an apparatus, and computer instructions are provided for extending operations of an application in a data processing system. A primary operation is executed. All extended operations of the primary operation are cached and pre and post operation identifiers are identified. For each pre operation identifier, a pre operation instance is created and executed. For each post operation identifier, a post operation instance is created and executed.