Yes, they are in different package.. Coz server side project and
client side projects are in different project, thats why they are in
different package.. but the code which are implemented in CList
interface and CListImpl are same as codes... According to your mail,
i should use same package name for both sides, hmmm, or can i copy
the stub to another project as compiled as class file ?
> I suspect you have the CList interface in two packages, so the CList
> that is implemented by CListImplStub is different from the CList the
> client is using. You can't do that. You have to use the *same* remote
> interface class, not a similar one with the same name in a different
> package.
Esmond Pitt - 04 May 2007 04:03 GMT
> Yes, they are in different package.. Coz server side project and
> client side projects are in different project, thats why they are in
> different package.. but the code which are implemented in CList
> interface and CListImpl are same as codes... According to your mail,
> i should use same package name for both sides, hmmm,
I didn't say that at all. I said you had to use the same remote
interface class at both sides and that includes not changing its package
name. How you achieve sharing of that single class between multiple
projects is up to you. That doesn't imply that both entire projects
should be in the same package.