Scott M Stark wrote:
> Great. I went through the archives and to summarize for others, the key is
> ClassLoaders and the Java2 security mechanism. The thread that contains
> the bulk of the discussion on the archive is 'EJB Restrictions-- threads,
> io'.
Class loaders and the Java 2 security mechanism are keys to how you
can have code in a container that can call APIs that EJB code is not
normally granted permissions to call. So this is important when you
are writing the resource manager that wraps up the file I/O access
to your data stores, and installing it in an EJB container.
But there's somewhat more to creating a connector (that's what the
next J2EE spec will call the gateways to external resources) than
just that. You have to consider aspects like transactions and
security (not the permission level security, but the user/role sign
on kind) as well. There can also be issues with connection
management (similar to what the JDBC connection pools do in most
containers). The file I/O APIs don't provide much support for these
aspects, so you'll have to add that in your connector if your
application calls for it.
Paul
===========================================================================
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".
