Since the session bean methods mean a remote call, all arguments(passed
by value) are anyway serialized, putting all arguments in an object is
better and the only overhead is the RecordBean object creation. I feel
there may be many more areas where there is enough scope to take care of
performance rather than compromise on good design.
-----Original Message-----
From: BELOUALI Amine [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 04, 2000 3:06 PM
To: [EMAIL PROTECTED]
Subject: Design vs Performance question
Hi all,
I would like to create a service method in a Stateless Session Bean wich
call some BMP to insert a Record in the database.
I have 2 choices :
1. I put all of the values the session bean need as parameters of the
method, I will have something like :
myMethod(Type1 val1, ..., Typen valn)
It seems to be better from the performance point of view but harder to
code
and to maintain.
2. I create some java bean in the client side (servlet in my case) where
I
populate all the necessary values and pass it as a parameter of the
method.
I will have something like this :
myMethod(RecordBean rb)
It seems to be better from the design point of view but I am afraid
about
the performance issues.
any comments or suggestions will be very appreciated
Thanks in advance
Amine Belouali
========================================================================
===
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".
===========================================================================
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".
