Help required in Txn management

Question

we are using Struts for client side and stateless Session bean as the server side component, we have a situation for which we need to manage transaction across multiple client request
for example
Step 1: From client we call "MethodA" in Stateless Session Bean which does certain database activities like insert, update.... and returns back to the client
Step 2: Depending upon the user input for the second request we call stateless session bean "MethodB" which does few more inserts and updates
     and should commit/rollback the record.
We need to maintain MethodA and MethodB Calls in single transaction, Please suggest us with the possible ways to handle this situation.

Answer 1

I found this in a thread written by Gerhard Djuracek from SAP, perhaps it will help you:
We distinguish 3 categories of addresses.
Addresscategory 1, address for organisations
Addresscategory 2, address for persons
Addresscategory 3, address on a relationship.
The address on a relationship is built of an address from an organisation. But it's not the whole address from that specific organisation, it's only, let's call it the postal part. Things like street, city, postal code and so on. The name part is taken from the person, which is involved in that relationship.
So we have here a mixture of Addresscategory 1 and Addresscategory 2. The communication data, we have only 3 communication categories on a
relationship, phone, fax and E-Mail address, is not taken from the organisation or the person's address. The communication data used on a relationship, is that one, which you can maintain in the section address data after having assigned an address to the relationship.
Any changes on any comm data of the organisation, will have no effect on the comm data of the relationship. Only changes on the address of the organisation, which will effect those fields, we called above the postal part of an address, will be taken into account for the address on the relationship.
In CRM, the contact person is a business partner of type person and can have many addresses of type 2, but only the standard address is
exchanged with the home address in the R/3 system.  If you create a relationship of category 'contact person', you can have an address of type 3 for every address of the customer, but only the standard address of type 3 is exchanged with the contact person's address of type 3 in R/3.
The concept of the business address does not exist in CRM. If a contact person is working for different customers, you create different relationships of category 'contact person' instead of creating a business address.
Hope this information is helpful.
Regards, Gerhard