Hi,
everybody is talking, don't make I/O access from a J2EE application.
Now, we develop a J2EE application. Users can upload media files, which will be converted. Should now the web-container application make only I/O access to the file system?
Regards,
Rafal
-
I/O & J2EE (2 messages)
- Posted by: Rafal Kedziorski
- Posted on: August 25 2004 17:40 EDT
Threaded Messages (2)
- I/O & J2EE by Zurdo 1119 on August 26 2004 08:27 EDT
- I/O & J2EE by Udayan Patel on August 30 2004 11:23 EDT
-
I/O & J2EE[ Go to top ]
- Posted by: Zurdo 1119
- Posted on: August 26 2004 08:27 EDT
- in response to Rafal Kedziorski
The restrictions are to ensure that the enterprise bean is portable and can be deployed in any compliant EJB 2.1 Container. So, you can use I/O but...
The EJB 2.1 spec says:
25.1.2 Programming restrictions
This section describes the programming restrictions that a Bean Provider must follow to ensure that the enterprise bean is portable and can be deployed in any compliant EJB 2.1 Container.
...
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, to store data. -
I/O & J2EE[ Go to top ]
- Posted by: Udayan Patel
- Posted on: August 30 2004 11:23 EDT
- in response to Rafal Kedziorski
Isn't that one of the reason GOF came up with Proxy???