This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: [java] transforming a file to itself - buffered?
- From: Robert Koberg <rob at koberg dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Tue, 04 Jun 2002 14:34:05 -0700
- Subject: Re: [xsl] [java] transforming a file to itself - buffered?
- References: <007a01c207f4$9bb59ae0$6401a8c0@pcukmka> <3CF7B759.4196CDDD@mitre.org> <3CFCFA34.1030508@koberg.com> <3CFD2A15.2020002@yahoo.de>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi and thanks Joerg,
J.Pietschmann wrote:
Robert Koberg wrote:
What is the best way to handle transforming a file to itself?
Currently I do:
File source = new File(servlet_context.getRealPath(_xml));
transformer.transform(new StreamSource(source), new
StreamResult(source));
Opening a file both for reading and writing at the same
time is always risky. Either write to a buffer, and write
the buffer to disk after the transformation has finished,
or write to a temporary file and rename to the original
file afterwards.
The reason I want to use java.nio is because there is a locking method.
It can lock the entire file or parts of the file. I am just
experimenting... I can open the file and provide the source through nio.
I would like to be able to write to the part of the document that i have
specified. Currently I only let one user access a particular file at a time.
Something like;
ByteArrayOutputStream baos=new B...;
File source = new File(servlet_context.getRealPath(_xml));
transformer.transform(new StreamSource(source), new StreamResult(baos));
byte buf[]=baos.toByteArray();
new FileOutputStream(source).write(buf);
BTW doing this in a servlet context appears to be
rather strange...
Why? Am I doing something stupid? I have only had a few concurrent users
at any one time and there has not been any problems. The user base for
any 'one' set of files is pretty small (1-10 users).
thanks again,
-Rob
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list