Magnus Stenman wrote:
> My objection (besides the hack/"trickery") is that the container suddenly
> has to keep an updated "active bean" <-> thread mapping which drains
> performance (and yes, there is a thread <-> transaction mapping already
> when there are active transactions but this adds some to the work). And
> this goes for *every* bean-method invocation - not just the ones where the
> context will be looked up (since this cannot be determined up front).
I agree 100%. There's already alot going on (2 thread assocs. at least:
security and tx) for each call, and 1 more just to "keep it nice" is not
acceptable IMHO. The context sensitive JNDI solution is a "possible
solution" but not a "good solution". I'd also say that since this is a
JNDI-behaviour that is specific to component-programming it will be
confusing. It is not very obvious for Joe Programmer to understand how
this could work. Magic is only good when you don't see it at all.
> I oppose the current design and propose somehow getting a reference to the
> context from the already existing EJBContext object - alternatively just
> receiving a Map/similar interface instead. Most types of "enterprise
> components" already, Servlet = ServletContext/ServletConfig, JSP =
> PageContext, EJB = EJBContext, etc etc...
>
> Any thoughts?
I suggested this too a few days ago. See archive for details/replies
(http://archives.java.sun.com/archives).
I would assume that the ServletConfig is also going away "for
consistency". <annoyed mode>It will probably wreck, oh I'd guess about
100% of all current servlets, but that's the price of progress I guess
:-/.</annoyed mode>
Mark, Vlada:
Are there any more reasons for using this technique to obtain the
environment? Convince me!
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
