And yet another solution :) is to package Person in an entirely separate jar that is distributed to the client and server, a pattern which decouples the design of datatransfer from that of the client...
Type: Posts; User: copeg
And yet another solution :) is to package Person in an entirely separate jar that is distributed to the client and server, a pattern which decouples the design of datatransfer from that of the client...
Norm's advice will solve the compilation time errors, but you may still receive runtime exceptions if client and server are packaged separately since you still need to let the one without Person know...
They are in different packages, may be the same in content but the different in practice. Norm has the correct method if you import them...here's a simple example which will result in a compile time...
What does this mean...does this mean there is a server.Person and client.Person class? If so, there's your problem.