You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Aristedes Maniatis <ar...@ish.com.au> on 2008/01/21 15:49:58 UTC
[M3 issue] extended type on ROP
There might be a packaging problem.
org.apache.cayenne.access.types.ExtendedType is not in the client ROP
jar, but it will be required on the client for any attributes which
implement an extended type. It isn't used directly on the client, so
maybe some sort of stub would do the trick?
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
Re: [M3 issue] extended type on ROP
Posted by Andrus Adamchik <an...@objectstyle.org>.
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
>
>
>
Re: [M3 issue] extended type on ROP
Posted by Aristedes Maniatis <ar...@ish.com.au>.
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
Re: [M3 issue] extended type on ROP
Posted by Andrus Adamchik <an...@objectstyle.org>.
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.
Andrus
Re: [M3 issue] extended type on ROP
Posted by Andrus Adamchik <an...@objectstyle.org>.
Yes, this is packaging, as we filter out the entire "access" package
and subpackages. But why would you want an ExtendedType on the client?
Andrus
On Jan 21, 2008, at 4:49 PM, Aristedes Maniatis wrote:
> There might be a packaging problem.
> org.apache.cayenne.access.types.ExtendedType is not in the client
> ROP jar, but it will be required on the client for any attributes
> which implement an extended type. It isn't used directly on the
> client, so maybe some sort of stub would do the trick?
>
> 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
>
>
>