> Actually, what I have is a bean, say PersonBean with remote interface
> Person. The implementation is up and running in some nice EJB server and I
> have nice clients doing fun stuff with Persons (playing twister or
> whatever).
>
> Now, here comes the notion of killing all stupid persons. So, I have the
> KillStupidThingsWithAGun third party software that I bought from some
> stranger on the street. The third party software expects Stupid objects,
> an
> interface provided by the vendor.
>
> So to use the KillStupidThingsWithAGun program I want to implement Stupid
> in PersonBean, and extend Person and Stupid into StupidPerson (or having
> the spec make it possible to have both of them as possible interfaces to
> the bean, making Person the default to let the old clients work without
> changes).
>
> The question is; can I keep the clients the way they are, re-deploying
> StupidPerson beans as Person and casting it to Stupid when the new client
> wants to run them through the KillStupidThingsWithAGun program?
[Chip Wilson]
Theoretically, yes. Re-deploy the bean with StupidPerson as the
remote interface. The proxies should resolve to either Person or Stupid
types. I'm not sure if PortableRemoteObject currently supports this, but it
should.
> Do the old
> clients have to know about Stupid and/or StupidPerson?
[Chip Wilson]
No.
> /Kalle
>
> ==========================================================================
> =
> 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".
