Abstract: Embodiments of the present invention address deficiencies of the art in respect to cut and paste object processing for instant messaging and provide a method, system and computer program product for clipboard object sharing for instant messaging. In an embodiment of the invention, a method for clipboard object sharing in an instant messaging session can include requesting transfer of a clipboard object from a source instant messaging client to a target instant messaging client in an instant messaging session, determining whether or not the target instant messaging client supports a format of the clipboard object, and transferring the clipboard object to the target instant messaging client only if the target instant messaging client supports the format of the clipboard object.

Abstract: A data warehouse is constructed using the relational mapping of a transactional database without reconstructing the data relationships of the transactional database. First, an application programmer analyzes an object model in order to describe facts and dimensions using the objects, attributes, and paths of the object model. Each of the dimensions has an identifier that correlates an item in the transactional database to a dimension record in the data warehouse. The fact and dimension descriptions are saved to a description file. Second, a Data Warehouse Engine (DWE) then access the description file and uses the object model, fact and dimension descriptions, and object-relational mapping to map transactional data to the data warehouse.

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, 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: Methods, apparatus and computer instructions for a container managed persistent support architecture that meets the Enterprise Java Bean (EJB) Specification are disclosed. The support architecture provides application programmers a model for balancing generated components with runtime code to better optimize flexibility and efficiency of applications. Six generated components: concrete bean, bean adaptor binding, injector, extractor, data cache entry and function set, are used in combination with runtime code to perform typical operations of CMP entity beans.

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 and system for maintaining originality-related information about elements in an editable object. It is determined that an element has been edited in the editable object. The originality-related information about the element, including the element's creator, is identified and recorded by embedding the originality-related information in the editable object, storing the originality-related information in an attached file, or storing the originality-related information in association with the element in a repository configured to be shared by different editable objects and further configured to be queried for elements of the different editable objects in association with originality-related information pertaining to the elements of the different editable objects.

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 data warehouse is constructed using the relational mapping of a transactional database without reconstructing the data relationships of the transactional database. First, an application programmer analyzes an object model in order to describe facts and dimensions using the objects, attributes, and paths of the object model. Each of the dimensions has an identifier that correlates an item in the transactional database to a dimension record in the data warehouse. The fact and dimension descriptions are saved to a description file. Second, a Data Warehouse Engine (DWE) then access the description file and uses the object model, fact and dimension descriptions, and object-relational mapping to map transactional data to the data warehouse.

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: Middleware application for managing communication between a client and a web service so that changes in the web service information, such as a change in the web service location, are addressed by the middleware application is disclosed. A developer registers web services in a repository. The middleware application generates a web service proxy based on web service information entered in the repository, and generates a new web service proxy when the web service information changes. The developer can then write code for client applications without the need to change code when changes are made in the web service information. Responsive to a client request, the middleware application accesses the repository to match the request with a web service. The middleware application transmits the request through the web service proxy to the web service.

Abstract: A method for embedding behavior tags in a source code so that a computer can choose the appropriate implementation technology to execute the source code comprising a Configuration Program (CP) and a Deployment Program (DP). The CP allows a user to define and modify a plurality of behavior tags in the behavior tag definitions. The CP also allows the user to define and modify the preferences as to the implementation technologies in an implementation technology preference list. The user then creates the source code with embedded behavior tags. The DP reads the source code and automatically selects the appropriate implementation technology based on the behavior tags. The DP gives preference to implementation technologies according to the implementation technology preference list. The result is that the user does not have to specify the implementation technology for the source code or configure the behavior tags to a specific implementation technology.

Abstract: A method and system for maintaining originality-related information about elements in an editable object. It is determined that an element has been edited in the editable object. The originality-related information about the element, including the element's creator, is identified and recorded by embedding the originality-related information in the editable object, storing the originality-related information in an attached file, or storing the originality-related information in association with the element in a repository configured to be shared by different editable objects and further configured to be queried for elements of the different editable objects in association with originality-related information pertaining to the elements of the different editable objects.

Abstract: The present invention provides methods, apparatus and computer instructions for a container managed persistent support architecture that meets the Enterprise Java Bean (EJB) Specification. The support architecture provides application programmers a model for balancing generated components with runtime code to better optimize flexibility and efficiency of applications. Six generated components: concrete bean, bean adaptor binding, injector, extractor, data cache entry and function set, are used in combination with runtime code to perform typical operations of CMP entity beans.

Abstract: The universal, Web browser-based Enterprise JavaBean (EJB) test client is itself a Java 2 Enterprise Edition (J2EE) application packaged in a Web archive file. This archive, when extracted, consists of a set of files that are installed on a target application server. The installation makes it possible for a user of a Web browser on a workstation remote from the application server to perform a number of tests on, and invoke, methods in EJB beans that are installed on the staging, or even production, servers. It is also possible to perform tests in real time under real conditions.

Abstract: An apparatus, method, and system for generating semi-deployed enterprise java beans is provided. The apparatus, method and system make use of metadata to identify an intended deployment of an undeployed enterprise java bean. The metadata may be packaged with the undeployed enterprise java bean into a java archive file which is provided to a deployment tool either on the same computing device or a different computing device. The deployment tool may make use of the metadata when generating deployment classes for the undeployed enterprise java bean. However, if the deployment tool is unable to recognize the metadata or the use of the metadata is not wanted, the deployment tool may also deploy the undeployed enterprise java bean in a conventional manner.

Abstract: The universal, Web browser-based Enterprise JavaBean (EJB) test client is itself a Java 2 Enterprise Edition (J2EE) application packaged in a Web archive file. This archive, when extracted, consists of a set of files that are installed on a target application server. The installation makes it possible for a user of a Web browser on a workstation remote from the application server to perform a number of tests on, and invoke, methods in EJB beans that are installed on the staging, or even production, servers. It is also possible to perform tests in real time under real conditions.

Abstract: A method, system, and computer program product for improving the performance of distributed object systems. A remote object is replicated to the node of the distributed system from which it is accessed. The scope of the replication is a transaction. Thereafter, method invocations on the object occur locally, avoiding the performance overhead of frequent round trips to the remote persistent object store. Changes made to a replicated object by a transaction are represented using a tree structure that is internally managed by the application. When an application or application user has made modifications to a replicated object and requests to commit the modifications, a determination is first made as to whether committing the modifications will result in an unacceptable data conflict. If no unacceptable data conflict will occur, and after resolution of those conflicts that can be resolved, the modifications are committed.

Abstract: A technique for providing a transaction management subsystem for an enterprise computing environment in which multiple concurrent and/or nested transactions may access the same Enterprise JavaBeans (EJBs) simultaneously. The transaction management subsystem provides a view for each transaction which includes an independent version of an EJB's business logic and its instance data. When an application or application user has made modifications to an EJB version and requests to commit the modifications, a determination is first made as to whether committing the modifications will result in an unacceptable data conflict with other versions of the same EJB. If no unacceptable data conflict will occur, and after resolution of those conflicts that can be resolved, the modifications are committed. The management subsystem also supports nested transactions, where each subtransaction may have an independent view of an EJB. Subtransactions may commit or roll back independently.

Abstract: A technique for maintaining the integrity of data maintained in an object in a persistent store of objects. When a modification event is initiated during a transaction to modify an object, a copy of the object is created. Modifications are made to the copy of the object, and the original object remains available to be accessed with its original value. The modifications to the copy of the object can be reviewed, or further modifications can be made to the copy before the modifications are committed and the changes to the copy applied to the original object and thus available to all users of the persistent store. Alternatively, the modification event can be canceled prior to commitment and never be made available via the persistent store.