openjpa logging

I am running a Query select d.breed from Dog d .This query gives an argument exception because Dog does not have a field called breed.Now there is no way I can make openjpa log this exception.The only way I can see this exception is by having a try and catch block in my code and catching and

Re: openjpa logging

OpenJPA does not log exceptions that are thrown to your code. ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may

RE: How to unit test the Enhancer?

You could also just test that the class implements org.apache.openjpa.enhance.PersistenceCapable. Such a check assumes that the OpenJPA enhancement is happening correctly under the covers, but should be a good first approximation at least. FTR, yes, there are tests for this stuff. Sadly, the

Re: Using query hints for mapping extensions in orm.xml

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

Re: openjpa logging

Abe, On 1/22/07, Abe White [EMAIL PROTECTED] wrote: OpenJPA does not log exceptions that are thrown to your code. So the assumption is that the caller will log the appropriate exception-related message if such an exception is caught? The processing that I am used to is to log any

Re: How to unit test the Enhancer?

Hi Patrick, Thanks for the pointer, I think something might be better than nothing - I will use this approach to test the Enhancer! When you say 'majority Kodo test suite has not yet made it into OpenJPA' - do you mean that this is scheduled to happen sometime? If not, are there plans to

RE: How to unit test the Enhancer?

When you say 'majority Kodo test suite has not yet made it into OpenJPA' - do you mean that this is scheduled to happen sometime? I hope to see more of the Kodo test suite make its way into OpenJPA over time. It's not a concrete goal on our (BEA's) roadmap, though, so it takes a back seat to

RE: openjpa logging

Okay, that's clearer. So, when we receive a SQLException from a database, we either re-throw the exact same exception, or we throw a new Exception consistent with the API interface setting the cause as the caught Exception? Is that our current exception processing model? Pretty much.

[jira] Created: (OPENJPA-105) Put together a test suite for Enhancer

Put together a test suite for Enhancer -- Key: OPENJPA-105 URL: https://issues.apache.org/jira/browse/OPENJPA-105 Project: OpenJPA Issue Type: Task Reporter: Rahul Thakur Subsequent to

Re: How to unit test the Enhancer?

Hi Craig, [snip] If not, are there plans to put together such tests into OpenJPA itself? OpenJPA is, like most Apache projects, a do-ocracy. If you have an itch, you are encouraged to scratch it. Yep, totally agree there and I would love to 'scratch' this 'itch' as well, but right now I