Systems and methods for application view transactions

• US 7,676,538 B2
• Filed: 03/28/2003
• Issued: 03/09/2010
• Est. Priority Date: 05/02/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Potter, Timothy, DeGrande, Rick, Upton, Mitch, Golding, Christa
• Primary Examiner(s): Vaughn, Jr.; William C
• Assistant Examiner(s): Cloud; Joiya M
• Application Number:
  US10/402,825
• Publication Number:
  US 20040019684A1
• Time in Patent Office: 2,538 Days
• Field of Search: 709227-229, 718/101
• US Class Current: 709/200
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

Local transactions are supported by an application view instance that can switch from a stateless session bean to a stateful session bean in order to open a connection for a local transaction. The state that the stateful session bean holds is ten the connection. The stateful session bean can hold the connection open across multiple requests in the local transaction interface allows a user to manage the transaction in the application view, and to switch the application view between a stateless session bean and a stateful session bean. A local transaction interface can contain a local transaction management contract, which enables an application server to provide an infrastructure and run-time environment for management of the transaction.

Claims

1. A system for supporting a local transaction with an application view, comprising:

a computer including one or more processors;

an application view provided at the computer, wherein the application view switches from a stateless session bean to a stateful session bean, opening a connection from a client to an enterprise information system (EIS) for a local transaction, wherein the stateful session bean holds open the connection to the EIS across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

a local transaction interface managing the local transaction at the EIS, for use with the application view; and

wherein

the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used, and

wherein the local transaction interface uses the state information to manage the local transaction at the EIS.

2. A system according to claim 1, further comprising:

a Common Client Interface class through which the local transaction interface can be exposed to a resource adapter client.

3. A system according to claim 1, wherein:

the application view is capable of opening a database connection for a local transaction.

4. A system according to claim 1, further comprising:

a transaction manager adapted to obtain a resource for any connection open for a local transaction.

5. A system according to claim 1, wherein:

the local transaction interface further contains a local transaction management contract.

6. A system according to claim 1, wherein:

the local transaction interface further contains a local transaction management contract adapted to enable an application server to provide an infrastructure and run-time environment for management of the transaction.

7. A system according to claim 1, further comprising:

a plug-in capable of performing a transaction method for the application view.

8. A system according to claim 1, further comprising:

a plug-in capable of creating a new instance of the application view.

9. A system according to claim 1, further comprising:

a plug-in capable of invoking a service within the local transaction.

10. A system according to claim 1, wherein:

the application view is capable of opening a connection for a local transaction against a resource adapter.

21. The system of claim 1, further comprising:

a process management component that invokes the application view, said process management component including an associated transaction,

wherein when the application view begin method is encountered, the transaction associated with the process management component is suspended, and

the transaction associated with the process management component is resumed when the application view commit or rollback method is executed.

22. The system of claim 1, further comprising:

a connector adapted to connect to the EIS, wherein said connector supports one of the following;

only local transactions with user-defined transaction demarcation;

or

only local transactions with transparent and atomic transaction demarcation;

or

only local transactions with no user-defined transaction demarcation.

11. A method for supporting a local transaction with an application view, comprising:

opening a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

enabling management of the local transaction in the EIS by using the application view through a local transaction interface;

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

using the state information by the local transaction interface to manage the local transaction at the EIS.

12. A method according to claim 11, further comprising:

holding the connection open for the duration of the local transaction.

13. A method according to claim 11, further comprising:

exposing a local transaction interface to a resource adapter client.

19. The method of claim 11, wherein:

multiple actions against an EIS for a local transaction are grouped together into a logical unit of work.

20. The method of claim 11, wherein:

a client manages whether the stateless or the stateful bean is used, the client accessing an application view that provides methods including begin ( ), commit ( ) and rollback ( ) for local transaction final use the stateful bean.

14. A system for supporting a local transaction with an application view, comprising:

means for opening a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

means for enabling management of the local transaction in the EIS by using the application view through a local transaction interface;

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

means for using the state information by the local transaction interface to manage the local transaction at the EIS.

15. A computer-readable storage medium, comprising:

means for opening a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

means for enabling management of the local transaction in the EIS by using the application view through a local transaction interface;

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

means for using the state information by the local transaction interface to manage the local transaction at the EIS.

16. A computer program product for execution by a server computer for supporting a local transaction with an application view, comprising:

computer code for opening a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

computer code for enabling management of the local transaction in the EIS by using the application view through a local transaction interface;

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

computer code for using the state information by the local transaction interface to manage the local transaction at the EIS.

17. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

open a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

enable management of the local transaction in the EIS by using the application view through a local transaction interface; and

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

use the state information by the local transaction interface to manage the local transaction at the EIS.

18. A computer-readable storage medium, comprising:

a code segment including instructions to open a connection from a client to an Enterprise Information System (EIS) for a local transaction by switching an application view from a stateless session bean to a stateful session bean, the stateful session bean holding the connection to the EIS open across multiple requests in the local transaction, wherein the stateful session bean stores the connection to the EIS as state information, wherein the application view abstracts specific services and events of the EIS as a set of business functions, and wherein the application view is used by the client to manage the local transaction, thereby bypassing the use of a separate connection class by the client for processing local transactions; and

a code segment including instructions to enable management of the local transaction in the EIS by using the application view through a local transaction interface;

wherein the local transaction functionality is not directly exposed, instead the functionality of the local transaction is provided on an application view interface, the application view providing a set of method functions to support the use of local transactions, including the methods to begin, commit, roll-back, and update the state information for the local transaction, thereby providing the client with local transaction functionality, wherein state is provided in an application view bean, and the application view bean retains a connection for the duration of a single transaction, wherein the application view bean is deployed as both the stateful session bean and the stateless session bean, the client managing which bean is used; and

a code segment including instructions to use the state information by the local transaction interface to manage the local transaction at the EIS.