search

jsoliveira / javaapiforkml

Automatically exported from code.google.com/p/javaapiforkml
0 stars 0 forks source link

OutputStream isn't closed when marshalling via "public boolean marshal(final File)" method in KML class #21

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I originally, accidentally posted this issue at the xjcpluginjavaapiforkml 
project and have re-posted it here where it seems to actually belong.

What steps will reproduce the problem?
1. Call public boolean marshal(final File) on a KML object with a File object 
parameter
2. Attempt to delete the resulting KML file while the application is still 
running

What is the expected output? What do you see instead?

The OutputStream that's created by the method should be closed after the KML 
object has been marshaled to the KML file.

What version of the product are you using? On what operating system?

2.2.0 on Windows XP Professional 32-bit

Please provide any additional information below.

This bug prevents the resulting KML files from being deleted within Windows 
Explorer until the application performing the marshaling has been closed.

Original issue reported on code.google.com by mhrobin...@gmail.com on 29 Jun 2010 at 1:44