AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Using query hints for mapping extensions in orm.xml
Let's put this into a more concrete terms:
Given:
1) Existing JPA orm schema in
http://java.sun.com/xml/ns/persistence/orm_1_0.xsd
2) OpenJPA supports its version of the orm schema
this message in error, please immediately return this
by email and then delete it.
-Original Message-
From: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 24, 2007 8:38 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Using query hints for mapping extensions
it.
-Original Message-
From: Albert Lee [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 24, 2007 8:38 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Using query hints for mapping extensions in orm.xml
First, I would not expected other providers will handle
Thank you, Albert, for your experimentation. The updated schema definition
(openjpa_orm_1_0.xsd) and the example openjpa_orm.xml seems to be what we
are looking for. I guess the only concern is whether we can count on other
JPA implementations to ignore this extra schema definition and just
: Wednesday, January 24, 2007 8:38 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Using query hints for mapping extensions in orm.xml
First, I would not expected other providers will handle the special
openjpa.orm.xsd even if it is spec'ed out in the document
header. If they
choose
Somehow the one of the attachment (openjpa_orm_1_0.xsd) from my previous
note did not make it to this forum.
Try again here.
--
?xml version=1.0 encoding=UTF-8?
!--
OpenJPA specific orm.xml schema
] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people-
A limitation of the JPA specification is that there is no
built-in
way to put
Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people-
A limitation of the JPA specification is that there is no
built-in
way to put implementation-specific extensions
query hints for mapping extensions in orm.xml
OpenJPA people-
A limitation of the JPA specification is that there is no
built-in
way to put implementation-specific extensions in an orm.xml
file,
which limits the use of OpenJPA's many useful extensions to
only
being expressible
this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA
this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people
PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people-
A limitation of the JPA specification is that there is no built-in
way to put implementation-specific extensions in an orm.xml file,
which limits the use of OpenJPA's many
12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people-
A limitation of the JPA specification is that there is no built-in
way to put implementation-specific extensions in an orm.xml file,
which limits the use of OpenJPA's
OpenJPA people-
A limitation of the JPA specification is that there is no built-in
way to put implementation-specific extensions in an orm.xml file,
which limits the use of OpenJPA's many useful extensions to only
being expressible annotations. Past suggestions for getting around
this
I think this is the way to do it. Isn't this what the QueryHints are
intended to do - to allow vendor specific query extensions to hook in :-)
Cheers,
Rahul
Marc Prud'hommeaux wrote:
OpenJPA people-
A limitation of the JPA specification is that there is no built-in way
to put
and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007 12:26 PM
To: open-jpa-dev@incubator.apache.org
Subject: Using query hints for mapping extensions in orm.xml
OpenJPA people
17 matches
Mail list logo