> Kov�cs P�ter wrote:
>
> I like your solution, but I am always uneasy about using
> static initalizers
> when my component sits on top of a more or less complex
> system.
After my previous reply, I did realize that there is one drawback to what I am
doing. If my static initializer just initialized a variable to some literal
value, there would be no problem. However, in my EJB, I am initializing a
static variable based on the results of making a remote call to another server
(an LDAP server). If the server is down, then my EJB is not properly
initialized. My bean is a little more complex because it needs logic to deal
with this situation. However, this is a conscious tradeoff that I chose to
accept: I minimized the number of calls to the server for data that is
essentially constant at the cost of a more complex EJB.
===========================================================================
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".
