Hi Jon,
Did you run with v2 build? v1(9.0 FCS or 9.0u1) doesn't have this feature.
I confirmed JavaLogger is used well in single persistence unit, but I found
there is a bug if multiple persistence units exist in persistence.xml. If
your persistence.xml has one unit, it should work well.
Could you try with latest v2 build?
Thanks,
-Wonseok
On 1/4/07, Wonseok Kim <guruwons_at_gmail.com> wrote:
>
> Hi Jon,
>
> It was working well, but I could see that lastest build (v2) doesn't
> produce proper Java logging output in SE mode.
> I need to look into this, please be patient for some time.
>
> Sorry for incovenience.
> -Wonseok
>
> On 1/4/07, Jon Miller <jemiller_at_uchicago.edu> wrote:
> >
> > Hi all,
> >
> > The following link states that you can configure TopLink to use
> > java.util.logging logging. I put the following line in my
> > persistence.xml,
> > but, I don't see a difference.
> >
> > <property name=" toplink.logging.logger" value="JavaLogger"/>
> >
> > And then modified my logging.properties file like the following. I also
> > tried just, oracle.toplink.essentials.level.
> >
> > oracle.toplink.essentials.session.level = FINEST
> >
> > http://www.oracle.com/technology/products/ias/toplink/jpa/resources/toplink-jpa-extensions.html#TopLinkLogging
> >
> >
> > Logging statements in my app that is using java.util.logging look like
> > this,
> >
> > [junit] Jan 3, 2007 5:26:04 PM
> > edu.uchicago.at.reservations.ReservationsService saveItem
> > [junit] FINE: entered
> >
> > whereas the TopLink ones are in a different format.
> >
> > [junit] [TopLink Config]: 2007.01.03
> > 05:26:07.760--ServerSession(25699763)--Connection(23971937)--Connected:
> > jdbc:in
> > etdae7:host:1433?database=ReservationsDev
> > [junit] User: dbo
> > [junit] Database: Microsoft SQL Server Version: 9.0.2047
> > [junit] Driver: i-net OPTA 2000 Version: 4.15.01
> >
> > Not a big deal, but, I was thinking it might be nice to just use
> > java.util.logging for everything. Has anyone else got this to work?
> >
> > Jon
> >
>
>