...On that note...is there not a ODBC file driverJDBC-ODBC
bridgeetc?
Just a thought!
Lewis
-Original Message-
From: David Ward [mailto:[EMAIL PROTECTED]]
Sent: 16 July 2001 17:50
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] EJB spec and java.io restrictions
The container
self and your EJB's gracefully, and
> it cannot do this if there are opened reasources it does not know
> about...please feel free to correct me if I am wrong though.
>
>
>
>
> -Original Message-
> From: David Ward [mailto:[EMAIL PROTECTED]]
> Sent: Mond
y 16, 2001 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] EJB spec and java.io restrictions
But the only files I write to are ones returned by
File.createTempFile(...), which are guaranteed to be unique...
--
Peter Wone wrote:
> File I/O is discouraged purely because it is outside
But the only files I write to are ones returned by
File.createTempFile(...), which are guaranteed to be unique...
--
Peter Wone wrote:
> File I/O is discouraged purely because it is outside the scope of the
> transaction manager.
>
> It would be more accurate to say that file OUTPUT is discou
File I/O is discouraged purely because it is outside the scope of the
transaction manager.
It would be more accurate to say that file OUTPUT is discouraged. File input
does not involves updates, and therefore cannot lead to update anomalies,
obviating the concern.
Read files to your heart's cont
We do files manipulation, and we know that it's prohibited in EJB spec, but
it works with JBoss.
However, we're conscious that it's a temporary solution. In a perfect world,
files would be mapped with kind of entity bean, but they are not.
So comes the problem of concurent access (especially with
