Hi Rahul


>1) 1 Stateful session bean.
>2) 3 Stateless session beans.
>3) 1 session bean
>
>I guess this is too heavy for tomcat.
>Any comments?
>
>
>

Maybe.  If you have a bad feeling then refactor it away !.  Try refactoring
your archictecture so that you have only one or two stateful session
facades for your middle tier servlet to interface to.  Give the new
stateful session bean more business level semantics and delegate the real
work to stateless session beans which of course the servlet need know
nothing about.

There is some excellent discussion of this sort of issue in the
Professional Java Server Programming J2EE Edition which every one on this
list will of course already own ;-)

Regards,

Shaun O'Hagan

Mega Tier Ltd
London UK.

===========================================================================
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".

Reply via email to