I've seen this argument a number of times, but what's the reality for these
claims?
Can someone cite me an example of an EJB container that enforces these
restrictions.
Scott
"Sharan, Abhishek" wrote:
> Hi Sridhar
> i dont know much about NAS however there are some programming restrictions
> in EJB.
> Enterprise beans make use of the services provided by the EJB container,
> such as life-cycle management. To avoid conflicts with these services,
> enterprise beans are restricted from performing certain operations:
> * Managing or synchronizing threads
> * * Accessing files or directories with the java.io package
> * Using AWT functionality to display information or to accept information
> from a keyboard
> * Listening on a socket, accepting connections on a socket, or using a
> socket for multicast
> * Setting a socket factory used by ServerSocket, Socket, or the stream
> handler factory used by the URL class
> * Loading a native library
>
>
===========================================================================
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".
