Skip to main content

Blog Archive for guruwons during September 2006

Previously I bloged about How to use Java Logger in Java SE mode - a workaround to change logger type. But the workaround is no more needed. GlassFish v2(from b17) implemented a new feature - the configuration for logger type for this. It's very easy to use Java logger in Java SE mode, just add following property to persistence.xml.   <property name="toplink.logging....
Introduction The hype of JPA has slowed down and time has come to apply this to real applications. To use JPA properly knowing JPA spec is not enough because JPA spec doesn't cover all aspects and the behaviour can be a little bit different in persistence providers. Especially 2nd-level cache is the one. Which is not covered by JPA spec, but most providers provides it. To increase performance...
TopLink Essentials(GlassFish JPA RI) can be used also in Java SE mode as you know. I will talk about how to change the default logger to java logger in this article. When you use TopLink in Java SE, you see following log messages generated by a default logger. [TopLink Info]: 2006.09.06 05:03:05.221--ServerSession(24529889)--Thread(Thread[main,5,main])--TopLink, version: Oracle TopLink...