>
>
>
>
>
> transaction-type="RESOURCE_LOCAL">
>
> org.apache.openjpa.persistence.PersistenceProviderImpl
> com.myclass.Country
> true
>
>
>
>
>
>
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/Unable-to-turn-off-logging-tp16800706p16808297.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
That's my fault for not checking the doc. I tried and got an error.
I re-ran with and it looks like
that "worked" for me with OpenJPA 1.2.0-SNAPHOT.
Web Master, which version of OpenJPA are you using?
-Mike
On Mon, Apr 21, 2008 at 9:25 AM, Craig L Russell <[EMAIL PROTECTED]>
wrote:
> Hi Mike
Hi Mike,
According to the documentation, a setting of "none" is legal. Does it
not do the obvious: inhibit all messages? Seems we may have a bug,
either in the implementation or description of "none".
Craig
On Apr 21, 2008, at 6:58 AM, Michael Dick wrote:
Hi,
If you want the bare minimu
Hi,
If you want the bare minimum of messages to be logged you can specify
Unfortunately there's still the potential for some messages to be logged,
but you can redirect the output to a file which might be a little cleaner :
Hope this helps,
-Mike
On Sun, Apr 20, 2008 at 7:20 PM, Web Master <
I've had a great experience with OpenJPA thus far, until I went to prepare
the app for a deployment to Production. For some reason, I cannot find a
way to stop trace level output to the console/stdout. Unfortunately, even
setting the openjpa.Log property to "none" had no effect. Anybody seen thi
