Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 2467 invoked from network); 25 Nov 2009 19:11:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Nov 2009 19:11:29 -0000 Received: (qmail 65625 invoked by uid 500); 25 Nov 2009 19:11:29 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 65547 invoked by uid 500); 25 Nov 2009 19:11:28 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 65537 invoked by uid 99); 25 Nov 2009 19:11:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2009 19:11:28 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists+1214986160035-208411@n2.nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2009 19:11:25 +0000 Received: from jim.nabble.com ([192.168.236.80]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NDNGa-0002R2-I6 for users@openjpa.apache.org; Wed, 25 Nov 2009 11:11:04 -0800 Date: Wed, 25 Nov 2009 11:11:04 -0800 (PST) From: Pinaki Poddar To: users@openjpa.apache.org Message-ID: <1259176264555-4067037.post@n2.nabble.com> In-Reply-To: References: <1259103322359-4061808.post@n2.nabble.com> Subject: Re: How to specify LRS in orm.xml? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Pinaki Poddar Hi, > Why not define a separate OpenJPA XML schema? Then declare its namespace > in > orm.xml and one can use JPA and custom elements in the same document. Yes that is a possibility. And this idea looks like a neat one. This limitation to translate OpenJPA-specific source code annotations to XML descriptors has been a long-standing issue [1]. Patrick commented way back in April 2008: "Hopefully, we can get this into JPA 2.0." -- but that hope is not yet realized. May be someone will volunteer to contribute... [1] https://issues.apache.org/jira/browse/OPENJPA-125 Christopher Giblin wrote: > > Hi Pinaki, > Thanks for the quick response. > > Why not define a separate OpenJPA XML schema? Then declare its namespace > in > orm.xml and one can use JPA and custom elements in the same document. The > original JPA schema is untouched. > > -chris > >> Hi, >> Any OpenJPA specific annotations are, unfortunately, not supported in XML >> descriptor. Because, JPA spec does not define a XML schema with a simple >> mechanism for vendor extensions. OpenJPA can merge source > code >> annotations with orm.xml -- so, one has to leave OpenJPA-specific mapping >> annotations on source code itself. >> >> >> Christopher Giblin wrote: >> > Hi >> > The OpenJPA describes how to indicate that a field should use OpenJPA's >> > large result set proxies using the @LRS Java annotation. >> > >> > Can I specify LRS using orm.xml instead? >> > >> > Thanks,chris > > > ----- Pinaki -- View this message in context: http://n2.nabble.com/How-to-specify-LRS-in-orm-xml-tp4061742p4067037.html Sent from the OpenJPA Users mailing list archive at Nabble.com.