Actually I'd suggest that the type itself does not implement
ExtendedType, then you avoid all this trouble:
class FooType {
}
class FooExtendedType implements ExtendedType {
}
Andrus
On Jan 21, 2008, at 5:32 PM, Aristedes Maniatis wrote:
On 22/01/2008, at 2:10 AM, Andrus Adamchik wrote:
On Jan 21, 2008, at 5:06 PM, Andrus Adamchik wrote:
but it will be required on the client for any attributes which
implement an extended type.
To clarify, ExtendedType is a *descriptor* of another type. The
type has to be present on the client, while descriptor does not.
Yes, you are right. It just means that I have to compile the
extended type against the cayenne server jar and then include the
compiled class file into the client, which is not what I'm doing
now. It might be a more convenient in my build environment to create
a stub so I can compile it directly in the client application, but
I'll see what is easiest.
Ari
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
