persistence@glassfish.java.net

Re: [FYI] article about newly added category-specific logging level and cascade refresh query hint

From: Tom Ware <tom.ware_at_oracle.com>
Date: Tue, 10 Jul 2007 15:16:32 -0400

Hi Wonseok,

  Thanks for reviewing. The two issues are fixed.

-Tom

Wonseok Kim wrote:

> Hi Tom,
> Thanks for quick response. :)
>
> What I found odd is that the default value of "toplink.logging.level"
> is CONFIG.
> Haven't we changed it to INFO several monthes ago?
>
> Also I could see plenty of blank lines in " toplink.logging.level"
> description.
>
> Regrads,
> Wonseok
>
> On 7/10/07, *Tom Ware* <tom.ware_at_oracle.com
> <mailto:tom.ware_at_oracle.com> > wrote:
>
> Hi Wonseok,
>
> The page has been updated. Let me know if you have any concerns.
>
> -Tom
>
> Wonseok Kim wrote:
>
> >
> > I blogged about recently added two enhancements.
> >
> >
> > TopLink Essentials enhancements - category-specific logging
> > level and cascade refresh query hint
> >
> <http://weblogs.java.net/blog/guruwons/archive/2007/07/_toplink_essent.html>
> >
> > Tom, I think these are necessary to be documented in the TopLink
> > Essentials JPA Extensions Reference page
> >
> <http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html
> <http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html>>.
> >
> > thanks,
> > Wonseok
> >
>
>