Dave,
I think the issue that Brian is refering to is if the 'remote interface' has
changed and not the server side implementation of this interface. If the
interface has changed then I would suspect the stub needs to be
regenerated/recompiled unless you are using dynamic proxies on the client
side.
Brian, I really do not see much of a problem with redeployment since in most
cases its changing for some client purpose which means changes in the front
end which means redeployment in some way. Also there are many ways to manage
redeployment. Have you looked at JavaWebStart?
William Louth
Inprise
www.inprise.com/appserver/
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Dave Wolf
Sent: Tuesday, August 29, 2000 3:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Remote Client Question.
> >Not to mention, if the API changed you'd likely need to
> recompile the client
> >anyways. So whats the advantage? Maybe Im being simply dense.
>
> What I meant was if the API didn't change but
> implementation details
> changed. If the API changed then obviously you'd have to re-compile.
>
> BP
But its just a stub. The implementation of a stub should just about never
ever change. The implementation of the servant bean can change all it wants
with no change in the stub.
So again I dont understand the value.
/dwolf
===========================================================================
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".
