Max,
The usual way to accomplish this is to use <env-entry> in the deployment
descriptor and do a lookup in the initial context. Here is an example:
Your descriptor would contain:
<env-entry>
<env-entry-name>myApp.myProperty</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>SomeValue</env-entry-value>
</env-entry>
Your bean would include the following code:
String prop = ( String ) new InitialContext().lookup(
"java:comp/env/myApp.myProperty");
At this point the variable 'prop' would be equal to the value 'SomeValue'.
Hope this helps
Cheers,
peter
At Wed, 3 Jan 2001 16:49:01 +0200 , Mikko Laanti <[EMAIL PROTECTED]> wrote:
>Hi,
>
>In EJB Spec. there was mentioned that using direct file io from Ejb is
>not a "good idea". People also talked about this in this newsletter.
>
>How about using Properties class? I know it's based on file IO but does
>Ejb container support it?
>
>Anyone know?
>
>Br
>
>- Max
>
>
>email: [EMAIL PROTECTED]
>
>===========================================================================
>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".
>
>
>
===========================================================================
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".
