V
veera maria
Hi,
I have a following situation. I should make stateless session bean as
a interface to stored procedures which are stored in database. Session
bean should call one stored procedure and that procedure might call
also another stored procedure to handle database actions and then
return resultset to session bean.
So, my questions are:
- is stateless session bean suitable for this kind of usage?
- session bean should handle transactions, so what kind of transaction
type
it should use? Some that is handled by container or JTA based?
- as I mentioned, there could be a 'chain' of stored procedure calls
after
session bean has called the first stored procedure, so can session
bean's transaction type handle this kind of chained stored procedure
calls or how to handle commits or rollbacks?
Br
Vera
I have a following situation. I should make stateless session bean as
a interface to stored procedures which are stored in database. Session
bean should call one stored procedure and that procedure might call
also another stored procedure to handle database actions and then
return resultset to session bean.
So, my questions are:
- is stateless session bean suitable for this kind of usage?
- session bean should handle transactions, so what kind of transaction
type
it should use? Some that is handled by container or JTA based?
- as I mentioned, there could be a 'chain' of stored procedure calls
after
session bean has called the first stored procedure, so can session
bean's transaction type handle this kind of chained stored procedure
calls or how to handle commits or rollbacks?
Br
Vera