Hi!
When developing a system using EJB one sometimes wants to use a specific
resource, a legacy system or whatever, that is not supported by the
container. In COM one has the possibility to implement a Resource Manager,
using a well-known API, that can be plugged into the architecture, thus
providing pooling and such for the resource. In the current specification
each resource has to be supported by the container, or one needs to
implement a resource manager that uses an API provided by the container. I
propose that the resource manager API should be a part of the spec, thereby
making it possible to change container provider without having to rewrite
each resource manager. If, for example, a legacy system is used one might
have quite a big task just providing the first resource managers and a
future change of container provider is not feasible since one has to
re-implement those managers.
What are the thoughts on this problem and proposition?
/Kalle
===========================================================================
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".
