One note of caution about using enums - there can be a problem in passing enums
from a client to a server using RMI-IIOP serialiazation - see GlassFish issue
https://glassfish.dev.java.net/issues/show_bug.cgi?id=193 for some details.
regards,
-marina
Abe White wrote:
I think that JDBCFetchPlan should take a Java 5 enum, and
JDBCFetchConfiguration should use the Connection values.
Certainly JDBCFetchConfiguration should use the Connection values. I
personally have never had a problem with symbolic constants for
settings, but enums for the FetchPlan are cool too. So long as the
JPA QueryImpl parses the enum value and its string form correctly
when using it as a hint.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or legally
privileged, and is intended solely for the use of the individual or entity
named in this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then delete
it.
