@incubator.apache.org
Subject: Re: OPENJPA-182: reuse Connection constants or
create our own?
It should be ok anyway in the same VM. Unfortunately I had
conflicting messages
on weather it's the name or the ordinal that is guaranteed to
work across the
VMs :(.
-marina
Patrick Linskey wrote:
Fascinating
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 4:56 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: OPENJPA-182: reuse Connection constants or
create our
own?
It should be ok anyway in the same VM. Unfortunately I had
conflicting
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
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 4:39 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: OPENJPA-182: reuse Connection constants or
create our own?
One note of caution about using enums - there can be a
problem in passing enums
from a client
It should be ok anyway in the same VM. Unfortunately I had conflicting messages
on weather it's the name or the ordinal that is guaranteed to work across the
VMs :(.
-marina
Patrick Linskey wrote:
Fascinating. Happily, as it turns out, we never compare these things
directly; instead, we
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 4:56 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: OPENJPA-182: reuse Connection constants or
create our own?
It should be ok anyway in the same VM. Unfortunately I had
conflicting messages
FYI, one problem with using an enum is that the rest of FetchPlan uses
symbolic constants, not enums. But, I think that we should deprecate
those methods and add in enum-based methods there when applicable at
some point here, anyways.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
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
