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
I assume the test passed the openjpa:someelement
someattribute=somevalue/ uses
?xml version=1.0 encoding=UTF-8?
entity-mappings
version= 1.0
xmlns=http://java.sun.com/xml/ns/persistence/orm;
xmlns:openjpa= http://incubator.apache.org/openjpa/orm;
Since this header
Not that I am volunteering to be the resident namespace expert, but
FTR, I tried throwing in a openjpa:someelement
someattribute=somevalue/ element into an orm.xml, and I notice
that we don't complain when we parse it, so presumably at least our
parse mode doesn't have any problem with
If there is a way to include schema-validation=true when parsing
the orm, I expect that this will throw an exception.
Craig
On Jan 21, 2007, at 11:59 AM, Marc Prud'hommeaux wrote:
Not that I am volunteering to be the resident namespace expert, but
FTR, I tried throwing in a
Do we have any experts with these xml namespaces? Or, anybody that wants to
become an expert? :-)
It seems like we need a real example of using these to make sure they are
viable. On paper, they look like the solution. But, Craig's concern about
allowing new member elements within existing
IIRC this sort of extension would only be allowed if the original
schema http://java.sun.com/xml/ns/persistence/orm; has explicitly
allowed extension. Historically, Sun has made it impossible to
extend their xml documents.
-dain
On Jan 18, 2007, at 6:16 AM, Kevin Sutter wrote:
Do we
Craig,
I'm not an expert with namespaces, but it would be something along the lines
of first defining the openjpa namespace and then specifying the attributes
qualified by this namespace. We would also need to provide a schema for
this openjpa namespace. Something like this, following on from
Hi Kevin,
I'm not either an expert in namespaces, which is why I didn't follow
in the first place ;-)
On Jan 16, 2007, at 6:12 AM, Kevin Sutter wrote:
Craig,
I'm not an expert with namespaces, but it would be something along
the lines
of first defining the openjpa namespace and then
That indeed does sound like a better solution.
On Jan 16, 2007, at 6:12 AM, Kevin Sutter wrote:
Craig,
I'm not an expert with namespaces, but it would be something along
the lines
of first defining the openjpa namespace and then specifying the
attributes
qualified by this namespace. We
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
Hi,
It kinda feels like we're corrupting the intended use of query hints.
Plus, it seems unfortunate to have to drop back into untyped strings if
we can avoid it.
I think that there is another approach that we've talked about earlier:
use namespaces to intersperse OpenJPA data into the orm.xml
16 matches
Mail list logo
