Well guys I finally understand the do's and dont's of Dynamic classloading.
DONT - Reference the class that you want to distrubute dynamically
DIRECTLY in the client code
DO - Access your DYNAMICALLY distributable class via a interface or
abstract base class.
After all as CASTRO, DAVID correctly states
>Dynamic classloading is useful primarily when you dont know at compile
time
>what classes you will be dealing with - in which case you have to use
reflection anyway
CONSEQUENCES OF THE ABOVE STATEMENTS ARE.
Assemble your Entity/Session beans plus whatever serverside logic you have
into a bussiness module which implements some <bussinesslogicexecution
interface> which you load dynamically. You can the invoke some well-defined
method to execute the whole shabang.
By the way this allows for a componentizing your logic...which some would
say is unecessary because J2EE already allows for componentizing your
logic.
Just my 0.02$ worth
Thanx for a great thread (Enjoyed it)
By the way why is the mailing list so sloooooowww. My messages take up to
half a day to appear on the list !!
Ivanhoe Abrahams
______________________________________________________________________
Ernst & Young South Africa - http://www.ey.com/southafrica
WARNING: this e-mail contains confidential information and any
unauthorised use or interception is illegal.
If this e-mail is not intended for you, you may not copy, distribute
or disclose the contents to anyone nor
take any action in reliance on the content. If you receive this in
error, please contact the sender and
delete the material from any computer.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
