egally 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.
> >
> &
6 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
> on weather it's the name or the ordinal that is guaranteed to
> work
age-
> 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
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 extra
e-
> From: [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
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 JDBCFetchPla
then delete it.
> -Original Message-
> From: Abe White [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 06, 2007 2:17 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: OPENJPA-182: reuse Connection constants or
> create our own?
>
>
> > I think that JD
> 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 ar
or.apache.org
> Subject: OPENJPA-182: reuse Connection constants or create our own?
>
> Hi,
>
> There's one last open issue for OPENJPA-182 that I know of. Currently,
> the JDBCFetchPlan.setIsolation() and
> JDBCFetchConfiguration.setIsolation() methods use the
> symbolic const
ay, April 06, 2007 12:47 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: OPENJPA-182: reuse Connection constants or create our own?
>
> Hi,
>
> There's one last open issue for OPENJPA-182 that I know of. Currently,
> the JDBCFetchPlan.setIsolation() and
> JDBCFet
Hi,
There's one last open issue for OPENJPA-182 that I know of. Currently,
the JDBCFetchPlan.setIsolation() and
JDBCFetchConfiguration.setIsolation() methods use the symbolic constants
defined in Connection. Should they, or should we use our own?
I think that JDBCFetchPlan should take a Java 5 en
11 matches
Mail list logo
