[EMAIL PROTECTED] wrote:
>
> 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.
Absolutely agree!
>
> 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
Exactly!
>
> 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.
>
Right, I'm using this pattern in my application.
Client doesn't have any Home&Remote interfaces and download
them blindly during lookup. It works perfectly when
NamingService & JBoss are in the same VM
When I connect the second jboss (from another computer) to
the same NamingService client is unable to lookup any beans
from the second container without having their Home/Remote
interfaces. Don't ask me why (I postponed the investigation
for a while, but I'll do that soon).
> By the way why is the mailing list so sloooooowww. My messages take up to
> half a day to appear on the list !!
I sent a test message to prove it 2 (TWO!) days ago. But
it hasn't came up in the list yet.
--
__________________________________________________
Alexander Kogan PTC www.ptc.com
[EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
