Hello!
Rickard �berg wrote:
> On Sun, 5 Nov 2000 02:38:22 -0500, James Cook <[EMAIL PROTECTED]> wrote:
> >Nothing has changed. The spec states:
> >"An enterprise bean must not use the java.io package to attempt to access
> >files and directories in the file system. The file system APIs are not
> >well-suited for business components to access data. Business components
> >should use a resource manager API, such as JDBC API, to store data."
>
> Implement the I/O stuff in a separate library that the bean can call
> instead. The only reason I see for turning off security is performance.
I'm back, after checking the archives, and I have to ask (nearly) the same
question again:
What do you mean by "separate library"?
As far as I understand the spec and the other mails in the archive an EJB
must not perform any IO related stuff and this covers the "pure" EJB and
all methods called on the complete call-graph. Therefore you cannot use
any "helper classes", "utility classes" or "separate libraries".
So whats the clue to solve the problem?
(* 2h later, reading archived mails *)
I think I got it:
Is it correct that a "separate library" or "helper class" means, an
installed JAR-File on the app-server?
Therefore I MUST NOT use IO/Threads or something like that AS LONG AS I
pack it with the EJB and I MAY use it IF I install the IO library on the
app server.
Regards,
Dirk
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
