Interesting discussion. We're currently working with a customer that is migrating from Hibernate to OpenJPA. Having an option like this could be useful in situations like this. Although, since the JPA spec is not crystal clear on a few aspects, some interpretation is left up to the beholder... So, we may still run into some areas that are interpretted as extensions to one vendor and as spec compliant to another. Providing an option like for OpenJPA would definitely help identify the processing that we think is spec compliant.
Kevin On Jan 16, 2008 1:27 AM, Patrick Linskey <[EMAIL PROTECTED]> wrote: > How would 'ignore' and 'false' differ? > > Also, your naming would presumably restrict the property to just JPQL. > What about a broader toggle to control strict JPA compliance? It seems > like if someone wants strict compliance, they're going to want it > everywhere, not just in JPQL. > > -Patrick > > On Jan 15, 2008 8:05 PM, Pinaki Poddar <[EMAIL PROTECTED]> wrote: > > openjpa.jpql.Extensions : true|false|ignore|warn > > > > > > -----Original Message----- > > From: Patrick Linskey [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 15, 2008 10:03 PM > > To: [email protected] > > Subject: JPQL extensions > > > > Hi, > > > > Earlier today, I modified the JPQL parser to allow some extensions to > > JPQL. I expect that there is other non-standard extended behavior (JPQL > > and otherwise) in OpenJPA. It seems like it might be desirable to have a > > property that controls whether or not OpenJPA allows extended behavior. > > > > I was thinking that a property like so could be useful: > > > > openjpa.JPAExtensions: true | false | warn > > > > Thoughts? > > > > -Patrick > > > > -- > > Patrick Linskey > > 202 669 5907 > > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally 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. > > > > > > -- > Patrick Linskey > 202 669 5907 >
