|
James Hicks
C.A.D.G. - Application Developer
BERRYDirect
Email: [EMAIL PROTECTED]
Phone: 936.462.4655
Fax:
936.462.4655
Pager:
936.568.4296
I-Pager:
[EMAIL PROTECTED]
Guys
i am always think about the overhead on developer
who is using session-facade design pattern.
in which we will wrap our entity beans with
session bean wrapper which utilize EJBLocalHome and EJBLocalObject interface
of Entity Bean.
To test my Entity Beans functionality by unit
testing i have to create standalone client which uses EJBHome and EJBRemote
interfaces , so i have to deploy entity bean which supports remote call
also.
once my unit testing is over i want to disable or
remove that remote call support in my bean , in my case i will achieve
this my recompiling my bean without EJBHome and EJBRemote.
is their any alternative for this bugging cycle
where i can dynamically disable the remote call support from my
bean..................;-)
hope you guys provide me mast
suggestion.
-Suhel
|
