This website requires Javascript to function properly. Please go to the setting of your web browser and enable Javascript for this website.

Ad by

最优利率和cashback可以申请特批，好信用好收入offer更好。请点链接扫码加微信咨询，Scotiabank -- Nick Zhang 6478812600。

Ad by

最优利率和cashback可以申请特批，好信用好收入offer更好。请点链接扫码加微信咨询，Scotiabank -- Nick Zhang 6478812600。

there are three options that i could think of right now.......

lubx(黑白世界*大漠孤烟)

1. using IOC light container like Springframe work, put into bean application context, then spring will inject the configuration you want to EJB context, EJB could access the config at any time. or
2. keep it in web tier applicaion context, when the client create EJB, pass the config in, (create(Parameter param), check with spec), web tier application context is a cache.

3. bind in JNDI tree after container started (not suggested, since JNDI tree is container specific and not guaranteed to work the way you want )

(#2227380@0)
Last Updated: 2005-4-7
This post has been archived. It cannot be replied.

Report

Replies, comments and Discussions:

工作学习 / IT技术讨论 / HELP!!! HELP!!! J2EE application configuration problems. -icanada(I can!); 2005-4-7 {963} (#2226749@0)
I am working on a J2EE project. We need to store some configuration information for our J2EE applications. We use EJB, JMS, and Databases.

The question is WHERE to put and How to get application or server configuration information? We store the application configuration information into an XML file. We put this XML file into jboss\bin\input and use a plain java class to read configuration parameter. All other EJB will access the plain Java class to get configuration parameters.

However, access to the filesystem from EJBs is not allowed in J2EE specification despite that our method is indirect access XML file by EJB. I know that I can put configuration in a database *sounds* like a good idea - but I think there will be a performance hit - and the relational model is not necessarily good for properties with a hierarchy.

I would like to get some informed opinions - some feedback on how other people have tackled this problem.

Thanks!!!!

没用过jboss，不明白你卡在哪了。通常的做法是servlet load configuration, pass it to slsb, then persistence layer(entity bean, jdbc, hibernate or whatever)，应该是不会有任何问题的。 -xanada(㊣流水); 2005-4-7 (#2226767@0)

I just don't know where to put the XML file and how EJB (say sessionBean) can access the XML file for J2EE application configuration. -icanada(I can!); 2005-4-7 (#2227066@0)

xxxxx.class.getResourceAsStream("file path") -macsym(日进斗斤); 2005-4-7 (#2226784@0)

But file access is not alowed in EJB. Enven though, in my application, XML file is accessed by a singleton class and EJB call this class. I am not sure this is good or not. -icanada(I can!); 2005-4-7 (#2227060@0)

No, you can read file from ejb, package it in JAR. I've did it before for read public key file. in your case, maybe put it as env-entry in deployment descriptor file. -macsym(日进斗斤); 2005-4-7 (#2227258@0)

or storing environment entry elements (env-entry) into the deployment descriptor. -macsym(日进斗斤); 2005-4-7 (#2226806@0)
Suggestion, using a help class to load the conf xml from startup listener, pass it on to EJB container -lubx(黑白世界*大漠孤烟); 2005-4-7 {468} (#2227189@0)
you are right, EJB should never access resource directly, (could be fired if my team member doing that, ), a help class to load the config in web startup listener, later on pass this config to application context that EJB container could access. Using a lookup class to find the config and keep in cache for performance. This is not a specific Jbosss related implementation, but JBoss has it own class loader, which is too container specific, not suggest to use that.

我觉得这是正解.只是不明白1.EJB container 如何访问application context? 2.如何lookup config,3 如何keep in cache -richwin(); 2005-4-7 (#2227247@0)

there are three options that i could think of right now....... -lubx(黑白世界*大漠孤烟); 2005-4-7 {524} (#2227380@0)
1. using IOC light container like Springframe work, put into bean application context, then spring will inject the configuration you want to EJB context, EJB could access the config at any time. or
2. keep it in web tier applicaion context, when the client create EJB, pass the config in, (create(Parameter param), check with spec), web tier application context is a cache.

3. bind in JNDI tree after container started (not suggested, since JNDI tree is container specific and not guaranteed to work the way you want )

Don't make sample things complex. I don't think it's best way. -macsym(日进斗斤); 2005-4-7 (#2227397@0)

你对，俺经常OVER ENGINEERING -lubx(黑白世界*大漠孤烟); 2005-4-7 (#2227414@0)

This typical problem has been discussed for long long time... -yuanzidan(原子弹); 2005-4-7 {798} (#2227259@0)
"The bean's "runtime environment properties" (i.e Context.lookup( "java:comp/env/..." )) are what this is for - providing runtime configuration to your bean."

"Refer to section 24.1.2, "Programming Restrictions", of the specification (EJB 2.0). Beans are strictly prohibited from accessing either the local filesystem via classes of the java.io package or the system ClassLoader, both being typical means for accessing properties files. Possible ways around these restrictions are through other resource manager classes such as a URL connection or the JNDI Filesystem Service Provider. Both of these methods, however, may prove to be more troublesome than they are worth."

"Use either the bean's "runtime environment" or a database to provide configuration data to your bean."

@Calgary

there are three options that i could think of right now.......

Replies, comments and Discussions:

More Topics