Piyush Nigam wrote:
>
> Hi,
> I have a scenario where seven forms are submitted to complete a
> transaction. My options are to :
> 1) maintain all the values from each form in the HttpSeession and on the
> final submission call a stateless session bean to manage my transaction.
> This ensures fewer remote calls
> 2) Reach values submitted by each form to a stateless session bean and keep
> passing its handle in the HttpSession. This reduces remote calls but places
> the session management responsibility on a less efficient framework.
>
> What do you think is the better choice?
(1) If you use HTTPSession for the data it will travel up and down the wire each
time. This could create a possible security problem and could create a possibly
worse performance problem than using a Session Bean.
(2) If you use a Stateless Session Bean you'll need to save the partially
complete (and maybe never-to-be-completed) data on a database.
(3) So I'd say use a Stateful Session Bean.
cheers... Ian
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
