db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From e...@jpox.org
Subject Re: Non-serializable object id classes
Date Thu, 20 Oct 2005 10:02:29 GMT
Michael,

JPOX raises InvalidPrimaryKeyException if the id class is not Serializable. Your
class should not get enhanced and the cause is logged (log4j). If you want,
enable log4j to write to the console.

Quoting Michael Watzek <mwa.tech@spree.de>:

> Craig,
>
> I am unsure about chapter "5.4.1 Application (primary key) identity" in
> the spec (version 9/9/2005). That chapter requires "... JDO object id
> has all of the characteristics of an RMI remote object, ...". One
> sentence further the spec specifies:
>
> "A5.4.1-3 REMOVE THIS ASSERTION [...]"
>
> Part of that assertion is the requirement on object id classes to be
> serializable.
>
> The TCK does not implement this assertion. Does this mean, that it is
> valid to specify non-serializable object id classes?
>
> Andy, Erik,
>
> if I call the JPOX enhancer for a class (among others) having
> application identity and the object identity class is not serializable,
> then the enhancement process silently exits without any (error)
> messages. Also, there is no exit code indicating an error. As a
> consequence, no classes are enhanced. Would it make sense to write a
> warning (or error) message to the console indicating the problem?
>
> Regards,
> Michael
> --
> -------------------------------------------------------------------
> Michael Watzek                  Tech@Spree Engineering GmbH
> mailto:mwa.tech@spree.de        Buelowstr. 66
> Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
> Fax.:  ++49/30/217 520 12       http://www.spree.de/
> -------------------------------------------------------------------
>




Mime
View raw message