persistence@glassfish.java.net

RE: Issue when the file writers are not being closed

From: Gordon Yorke <gordon.yorke_at_oracle.com>
Date: Sat, 18 Mar 2006 11:01:52 -0500

Pramod,
    I thought I had responded. This change looks good please check it in.
--Gordon
  -----Original Message-----
  From: Pramod Gopinath [mailto:Pramod.Gopinath_at_Sun.COM]
  Sent: Friday, March 17, 2006 6:46 PM
  To: persistence_at_glassfish.dev.java.net
  Cc: Gordon Yorke
  Subject: Re: Issue when the file writers are not being closed


  Hi Gordon/Tom

     Any updates related to this change.

  Thanks
  Pramod

  Pramod Gopinath wrote:
    Hi Gordon
      The change listed in this email is for a scenario for which there is no issue filed. But we have noticed this issue on Windows machines.

    In oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider for the java2db case we do not close the file writers. This leads to issues on Windows platform. The change is to call

    SchemaManager.closeDDLWriter();

    Again this call will happen only if java2db is enabled.

    Thanks
    Pramod


----------------------------------------------------------------------------
Index: src/java/oracle/toplink/essentials/ejb/cmp3/EntityManagerFactoryProvider.java
===================================================================
RCS file: /cvs/glassfish/entity-persistence/src/java/oracle/toplink/essentials/ejb/cmp3/EntityManagerFactoryProvider.java,v
retrieving revision 1.22
diff -r1.22 EntityManagerFactoryProvider.java
344a345
          mgr.closeDDLWriter();