Environment entries

I store a couple of environment entries in my web.xml file. These are basically a username/password for my OID connection.
I want other applications to use similar environment entries.
Is there a file where I can put these entries so any application stored in a paticular container can see them?
Could I then still do a JNDI lookup to get their values ?
Thanks Richard

Hi,
I never tried it, but I think you should be able to set it up as a datasource configured in teh j2ee/home/config directory of OC4J. There is an existing datasources file already
Frank

Similar Messages

How to add environment entry in EJB3 ejb-jar.xml

Hi,
Is that a build in way of add environment entries in JDev for EJB 3 beans? For EJB 2 beans you can do that using properties. But the bean properties is not available in EJB 3. Please help.
Thanks
Kenny

Thank you for the reply. But I need a way to enter env-entry value in ejb-jar.xml for EJB 3 in Jdev. In EJB 2, Jdev generate ejb-jar.xml for the bean and also let you add env-entry through bean's properties menu. But in there in no properties menu for EJB 3, also generated ejb-jar.xml is only a empty file doesn't contain any EJB depolyment information. That means you have to code ejb-jar.xml all manually.
If I am wrong, can someone show me how to do this right?

Admin UI for editing environment entries (i.e. env-entry in web.xml)

Hi there,
just wanted to know if Weblogic nowadays features a UI for post-deployment editing of environment entries such as the ones declared via <env-entry> in web.xml ( [http://download.oracle.com/docs/cd/E21764_01/web.1111/e13712/web_xml.htm#autoId30] ). So far, I'm using a deployment plan to re-configure these things at the time of each deployment, which works but which is also probably not the most flexible solution.
Thanks in advance,
Chris

Ah, I was trying to do a lookup from session bean for the env-entry defined in
the web.xml. After reading the J2EE spec, I see this just won't work. env-entries
are only accessible from within the component where they are defined.
Still the error message with "comp.env" instead of the expected "comp/env" is
a bit confusing.
Not much traffic in this newsgroup, is there?
Steve
"Steve Ditlinger" <[email protected]> wrote:
>
>
>
If I create an "env-entry" block for a name (e.g. "MySchemaName") in
my web.xml
file and deploy the web app, I should be able to look up the name from
my webapp
with the line:
 
myInitialContext.lookup("java:comp/env/MySchemaName");
 
However when I do that I get the error message:
 
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/MySchemaName'
 
Note that the "comp/env" prefix has been changed to "comp.env". This
worked under
WL 6.1. Is this a bug in WL 7's JNDI or a bug in the error message or
both or
something else altogether?
The immediately previous line successfully performs an EJBHome lookup
using the
same Initial Context object. The main difference is that the EJBHome
name is defined
thru the EJB deployment descriptors, not the web.xml.
Thanks,
Steve

Global Application Environment Entries

In declaring environment entries, is there a way to declare one that is global
to all the beans in an application?.. Currently, I'm declaring them as follows:
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>LMRPackageBQEJB</ejb-name>
<home>LMRPackageBQSLBean.LMRPackageBQHome</home>
<remote>LMRPackageBQSLBean.LMRPackageBQ</remote>
<ejb-class>LMRPackageBQSLBean.LMRPackageBQBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
 <env-entry-name>DB_SCHEMA_NAME_BQ</env-entry-name>
 <env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>lmrdba</env-entry-value>
 </env-entry>
 <resource-ref>
<res-ref-name>jdbc/LMR_DB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>
<session>.....
How can this be changed?
Thanks

Hi,
I never tried it, but I think you should be able to set it up as a datasource configured in teh j2ee/home/config directory of OC4J. There is an existing datasources file already
Frank

Question on clustering and J2EE Environment Entries

Does anyone know if changes made through the admin server console to J2EE
 environment entries are propagated to the managed servers without
 redeploying the entire app. I can find a reference similar to this for
 things in the config.xml which states they are propagated in memory (in most
 cases) and can optionally be written permanently to the confg.xml file. I
 can't find a reference that tells me how/what is done for J2EE environment
 values.
 If this is not possible, how does one do dynamic configuration setting for a
 J2EE application in a clustered environment?
 Kent


What I'm talking about is the environment entries that are set in the web
 application deployment descriptor (web.xml) from the admin server console.
 You go to a specific web-app in the console and then click on "edit web
 application deployment descriptor". From there (towards the bottom of the
 tree on the left) is Env Entry. You can change Environment Entries in the
 DD. What is unclear is if the values are propagated to the running app
 (in memory). For example, if I have a servlet that reads this environment
 entry and I change it in the admin console is the new value reflected
 (relatively) immediately? It's not entirely clear.
 Since there is an option to "persist" these changes (in the top of the tree)
 that would seem to imply that the changes are propagated to the running
 instances in memory otherwise why would I not want to persist the change?
 On the other hand, I would have also expected a button to let me decide when
 to push the changes so I could control when the managed server know about
 the change (for example, if I had to set more than one property to configure
 something).
 So ... does this make my question clearer? And if so is there any
 documentation the describes this? If not how do people handle configuration
 of a running application in a cluster if it not through DD environment
 entries?
 Kent
 "Cameron Purdy" <[email protected]> wrote in message
 news:[email protected]...
 > > Actually I'm talking about what I would call "environment variables" if
 > this
 > > was unix. I am not talking about files (gifs, html, etc) but rather
 > porpety
 > > settings. It is my understanding that these are call "environment
 > entries"
 > > (but I may remembered the name wrong) and are typed values that can be
 > > looked up vi JNDI.
 >
 > You can programmatically set JNDI entries, and they will usually be
 > propagated (although they are not designed to be reliably replicated).
 > Furthermore, the death of the registering server will cause the death of
 the
 > JNDI entries.
 >
 > I don't know how to set them from the console.
 >
 > Peace,
 >
 > --
 > Cameron Purdy
 > Tangosol, Inc.
 > Clustering Weblogic? You're either using Coherence, or you should be!
 > Download a Tangosol Coherence eval today at http://www.tangosol.com/
 >
 >
 >
 > "Kent Mitchell" <[email protected]> wrote in message
 > news:[email protected]...
 > >
 >
 >
 >

Utilizing EJB Environment Entries in different runtime env

Hello
We are in the process of moving to the NWDI environment.
Most of our EJBs are using the EJB Environment Entries (defined in the deployment descriptors)
Some of those EJBs rely on the fact that the same property will have different values in different runtime environments.
I have noticed that during the import process (from one env to another) done by the CMS there is no option to change those environment varialbles.
I have also noticed that there is no option to change the values of those environment entries during runtime in the SAPJ2EE 6.40 (that option existed in SAPJ2EE 6.20)
I just need to get an official answer;
Is there no way to control the values of the environment entries during deployment with NWDI?
Do we have to change our code (that relied on J2EE standards) so it does not expect different values in different runtime environments?
I have an open CSN about this, but no answer there yet...
<a href="https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smp_custmsg/main.do?event=LOAD&smpsrv=h">CSN 0120025231 0001708443 2005</a>

hi
I have the same problem describewd in this <a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=45460">SDN thread</a>
to save you the time, it says that You must add the declaration within the sda-dd.xml
<substitution-variable>
<variable-name>com.vendor.yourVarName</variable-name>
</substitution-variable>
Note that if you write a Server library this file is displayed by the NWDS
However, if you are using a J2EE application module, this file is generated during the build and stored into the ear.
if you try using a substitution variable in your deployment descriptor without specifying it in the sda-dd.xml you get a deployment error -
com.sap.engine.deploy.manager.MissingSubstitutionException: Missing substitution value for variable
(see full log message below)
As a workaround, I edited the sda-dd.xml after the EAR was generated (added the required entry), repacked it and deployed it.
Then it worked.
The problem is, if I use NWDI, I CANNOT edit the EAR that gets generated!
any idea of how to solve this?
full log message of deployment error
02/01/2006 13:58:13 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : zaksrv2
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/zak/LOCALS1/Temp/temp19284checkpoint.comtimeofftest5substear.ear
Result
=> deployment aborted : file:/C:/DOCUME1/zak/LOCALS1/Temp/temp19284checkpoint.comtimeofftest5substear.ear
Aborted: development component 'timeoff/test5/subst/ear'/'checkpoint.com'/'DEV_TIMEOFF6_D'/'20060102135547':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.MissingSubstitutionException: Missing substitution value for variable [com.cp.sapGRP].
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment exception : The deployment of at least one item aborted

JNDI Environment Entries

We're porting a web application from Tomcat 4.1.x to WL 7.x. The application requires
several environment entries that we would like to keep outside of property files...
In Tomcat, we used the <Environment> tag of the <Context>. TC would bind these
entries into the application's local JNDI tree and the application would access
them through java:comp/env. We would like to do something similar in WL, but we
haven't been able to spot the mechanism in the docs.
Even if we have to create the environment values in the global JNDI tree and map
them locally through weblogic.xml, it would be fine. What we want to achieve is
making these changes part of the post-build deployment process.
Any help or a slap upside the head is appreciated - not mention needed. :) Thanks.
Bon

Can you refer this page, it might help.
http://docs.sun.com/source/816-7156-10/agj2eres.html
http://forum.java.sun.com/thread.jspa?threadID=499983&messageID=2362672
I am not an expert. Still Cant we use
<env-entry>
<env-entry-name>...</env-entry-name>
ETC
</env-entry>
in your web.xml
and you can use it.
Check this tag also and see if you can use it.
Hope this helps

Where do you put JNDI environment entries

Hello:
How do you setup environmental entries that can be lookup via JNDI.
I was doing this:
1.) In web.xml put the following:
<resource-env-ref>
<resource-env-ref-name>myStringName</resource-env-ref-name>
<resource-env-ref-type>java.lang.String</resource-env-ref-type>
</resource-env-ref>
2.) In global-web-application.xml, then put the following:
<env-entry-mapping name="myStringName">myStringValue</env-entry-mapping>
However, the web.xml is not able to find the <env-entry-mapping> to "myStringName"
Any help on this is much appreciated.
Thanks (in advance) for any help

Can you refer this page, it might help.
http://docs.sun.com/source/816-7156-10/agj2eres.html
http://forum.java.sun.com/thread.jspa?threadID=499983&messageID=2362672
I am not an expert. Still Cant we use
<env-entry>
<env-entry-name>...</env-entry-name>
ETC
</env-entry>
in your web.xml
and you can use it.
Check this tag also and see if you can use it.
Hope this helps

Can I modify the value of an enviroment entry for an EJB without having to re-deploy.

I wish to modify the value of an envrioment entry for an EJB. The entry already exists and has been created using
<env-entry>
<env-entry-name>myFlag</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>true</env-entry-value>
</env-entry>
I can access the value using code similar to the following:-
InitialContext initialContext = new InitialContext();
String value = (String) initialContext.lookup("myFlag");
However if I try the following:-
InitialContext initialContext = new InitialContext();
initialContext.rebind("myFlag", "false");
I get an OperationNotSupportedException thrown.
Do I need to use LDAP directly (rather than through JNDI) to modify this value or is there another / better way? If I do need to use LDAP directly what would the code look like ?

Hi,
As per J2EE specification:
Naming environment entries allow customization of a component during deployment or assembly without the need to access or change the component?s source code. The container implements the naming environment, and provides it to the component instance through a JNDI naming context.
The Deployer can modify values of environment entries that have been previously set by the Application Component Provider and/or Application Assembler.
Generally only those variables/properties are set in environment entries which are likely to be different on various Application server configurations/installations, so it is not required/advisable to change these entries programmatically. Any way iAS-6.0/6.5 doesn't support changing environment entries programmatically, it binds all the JNDI names during Server startup after reading it from the registry.
For your purpose you can use a boolean variable in your code to set your flag, and may be put it into session.
Please feel free to ask further questions.
Sanjeev,
Developer Support, Sun ONE Application Server-India.

Env-entry reachable from more than one bean

Is it possible to reach env-entries of one session-bean from another session-bean within same ejb-jar.xml?
Or is the only way to write them twice, once per each bean.

Greetings,
Is it possible to reach env-entries of one
session-bean from another session-bean within same
ejb-jar.xml?In theory, a JNDI namespace is hierarchical (a tree structure - like a filesystem) - and a server typically maintains a global namespace - so as long as your bean knows the lookup name of the entry it can be accessed regardless of the locality of the bean (ie. it may even exist in a separate application running on the same server!). However...
Or is the only way to write them twice, once per each
bean.The purpose of environment entries is to provide "post-compile time" customization to your beans and so ideally each bean should have it's own env-entries specific to it's needs. Additionally, depending on your vendor implementation private namespaces for env-entries might be provided and/or you may also get assembly/deployment errors for beans performing lookups against the namespace for which assembly mappings were not provided. In these cases you will have to devise a mechanism for the passing the env information between your beans (since the specification prohibits beans from modifying their runtime environments. ':-o ).
I hope this helpful.
Regards,
Tony "Vee Schade" Cook

Env-entry?

How do you 'configure' a Workshop application?
The normal way to do this in J2EE is to add environment entries in web.xml,
ejb-jar.xml or even application.xml.
In Workshop there is only web.xml. And when deploying as an EAR file, it
gets packaged in a WAR file, not inside the JAR file of the Web Service. So
you can't just look up a web.xml environment entry from your jws file.
=======
Another question: why is web.xml and weblogic.xml available in Workshop in
the first place? What can you do with these files? I don't see how they can
be useful to the developers.
Since all the 'plumbing' of Web Services is hidden inside Workshop anyway, I
think they should remain hidden too. Or if they are useful, then I think we
should be able to see the other deployment descriptors (the WebServices's
(ejb-jar.xml) and the EAR's (application.xml)).
Even better, how about some new categories under the project's properties,
called 'descriptors'. Hide all that XML and show it graphically. Don't allow
modifying what is the guts of the system, it's error-prone.
Thanks,
Emmanuel Proulx

Thanks for the details, Emmanuel. I'm sure that our Product Management team
will be interested in your feedback.
Ian M. Goldstein
Developer Relations Engineer
BEA Systems, Inc.
"Emmanuel Proulx" <[email protected]> wrote in message
news:[email protected]...
Ian, group,
Unfortunately, I'm going to answer your first question with a question
(since we're in Beta, let's think of this as an opportunity for us tolearn
from each other): What kinds of "configuration" do you want to do to
your
Workshop application? What types of environment entries are youinterested
in adding to the deployment descriptors?J2EE defines the environment entries as a way to set up an application
without modifying the code. You just look up the environment entry and you
get a value that you can use in the code. This modifies the behavior ofyour
code without having to change it. It's like an OS environment variable.
Examples:
- Debug Flag
- Currency Symbol
- Location of temp folder
- Location of a resource (although ther are resource references for that,a
special kind of environment entry), like JDBC datasource, JMS conn.factory,
EJB reference (using ejb-refs), etc.
You can change any of those in the XML file and you don't have torecompile.
This is very very useful, in particular when switching an application froma
development to a production box. The debug flag should be turned off, the
temp folder is different, the datasource should point to the production
database, etc.
Currently if you want to configure a Workshop application in this way, you
have to modify the project and recompile. This can introduce problems when
deploying to the production server.
I suggest we add a new category in the project properties (right pane)like
this:
+ target-namespace
+ schema
- configuration
- environment
debugFlag java.lang.Boolean true
currency java.lang.Char $
temp String c:/temp
- resource references
databaseDS javax.sql.DataSource Container DS-JNDI-Name
Shareable
- EJB references
EJB1 Session EJB-JNDI-Name EJBHome EJBRemote EJBName
(ejb-link)
- EJB local references
EJB1 Session Local-EJB-JNDI-Name EJBLocalHome EJBLocal
EJBName (ejb-link)
These should be saved in application.xml at the time of deployment. The
references should be available as a choice in the various controls. E.g.for
the database control, any Datasource reference should appear in thecreation
dialog and properties.
NOTE: The above comes from what I saw in Weblogic Builder. But somethingis
missing from WebLogic Builder: either <resource-ref> or <resource-env-ref>
is not listed.
More 0.02$.
Talk to you soon,
Emmanuel
As for your second question, I agree that exposing the web.xml and
weblogic.xml in the project tree does in fact suggest that developers
may
want to edit them. I'll bring that feedback to our development team.Thanks!
Your suggestion about providing a graphical editor for modifyingdeployment
descriptors is something that the WebLogic Server development team feels
pretty strongly about, too -- check out WebLogic Builder
(http://e-docs.bea.com/wls/docs70/wlbuilder/WebLogicBuilder.html),
included
in the WebLogic Platform 7.0 beta. Of course, you don't need to go thatdeep
into application deployment descriptors to build and deploy your
applications with WebLogic Workshop. (In fact, you don't even need to
know
what a deployment descriptor is to successfully deploy web services you
develop with WebLogic Workshop.)
Cheers!
Ian M. Goldstein
Developer Relations Engineer
BEA Systems, Inc.
"Emmanuel Proulx" <[email protected]> wrote in message
news:[email protected]...
How do you 'configure' a Workshop application?
The normal way to do this in J2EE is to add environment entries inweb.xml,
ejb-jar.xml or even application.xml.
In Workshop there is only web.xml. And when deploying as an EAR file,
it
gets packaged in a WAR file, not inside the JAR file of the WebService.
So
you can't just look up a web.xml environment entry from your jws file.
=======
Another question: why is web.xml and weblogic.xml available in
Workshop
in
the first place? What can you do with these files? I don't see how
they
can
be useful to the developers.
Since all the 'plumbing' of Web Services is hidden inside Workshop
anyway,
I
think they should remain hidden too. Or if they are useful, then I
think
we
should be able to see the other deployment descriptors (the
WebServices's
(ejb-jar.xml) and the EAR's (application.xml)).
Even better, how about some new categories under the project'sproperties,
called 'descriptors'. Hide all that XML and show it graphically. Don'tallow
modifying what is the guts of the system, it's error-prone.
Thanks,
Emmanuel Proulx

Updated env-entries in web.xml

          We are using WLS 5.1 SP10.
          In a web-application we like to have some parameters (related to the webapp as
          a whole) which can easily be changed (without having to restart the server).
          What is the best way to do that?
          I was thinking of env-entries.
          But when I change them the web.xml is not reloaded and the changes have no affect.
          Is dynamic reload of web.xml possible under WLS5.1 SP10?
          When should env-entries be used, and when init-params?
          Init-params seems to be servlet(JSP) related, while the environment entries affect
          the web-app environment. Are there other elements to take in consideration?
          In the doc I found no real explanation of when to use what...
          Any help would be appreciated,
          Frederic
          Please send answers also to my e-mail: [email protected]


Hi,
these are only configurations and don't cause a harm or use resources. So I suggest to leave them in just in case yu need them later
Frank

Changing env-entry after deployment

Hi,
I was wondering how I can change the value of an env-entry after deployment? Do I have to change the value in the ejb-jar.xml, redeploy the application, or is there a utility I can use?
thanks
Steve

Okay gentlemen, I dug around and couldn't find anything on this concept of defining an env-entry after deployment using Sun Java System Application Server 8.1 - so I just came up with my own hack. Thought I'd share it in case others have the same question and can't find the answer.
Just to restate the problem: In SJAS you can't seem to define an environment entry that you can just look up via JNDI (you can do this in Tomcat pretty easy though using the context.xml file and an env-entry like syntax) - the benefit of this being of course that you can easily define deployment-time variables which a system administrator can set based on his setup. There seems to be no way to do this is SJAS 8.1
As a workaround, you can create your own custom JNDI resource which will expose the properties that you set in the Admin Console as a simple java.util.Map that you can use from your app.
Here's the blow by blow:
2. Create a JNDIProperties object that implements java.util.Map but does NOT implement java.io.Serializable:
package helpers.jndi;
import java.util.Collection;
import java.util.Map;
import java.util.Set;
public final class JNDIProperties implements Map {
 private Map map;
 public JNDIProperties(Map aMap) { map = aMap; }
 public boolean containsKey(Object key) { return map.containsKey(key); }
 public void clear() { map.clear(); }
 public Object get(Object key) { return map.get(key); }
 public boolean containsValue(Object value) { return map.containsValue(value); }
 public Set entrySet() { return map.entrySet(); }
 public boolean isEmpty() { return map.isEmpty(); }
 public Set keySet() { return map.keySet(); }
 public Object put(Object key, Object value) { return map.put(key, value); }
 public void putAll(Map t) { map.putAll(t); }
 public Object remove(Object key) { return map.remove(key); }
 public int size() { return map.size(); }
 public Collection values() { return map.values(); }
}2. Create an object that implements javax.naming.spi.ObjectFactory and returns an instance of JNDIProperties containing the properties defined in the container:
package helpers.jndi;
import java.util.Enumeration;
import java.util.Hashtable;
import java.util.Map;
import javax.naming.Context;
import javax.naming.Name;
import javax.naming.RefAddr;
import javax.naming.Reference;
import javax.naming.spi.ObjectFactory;
public class PropertyFactory implements ObjectFactory {
 public Object getObjectInstance(Object obj, Name name, Context nameCtx, Hashtable environment) throws Exception {
 Map myMap = new Hashtable();
 Reference myReference = (Reference)obj;
 Enumeration myEnumeration = myReference.getAll();
 while (myEnumeration.hasMoreElements()) {
 RefAddr myRefAddr = (RefAddr)myEnumeration.nextElement();
 myMap.put(myRefAddr.getType(), myRefAddr.getContent());
 JNDIProperties myJNDIProperties = new JNDIProperties(myMap);
 return myJNDIProperties;
}3. Build this and copy the jar to $SJAS_HOME/domains/domain1/lib/ext/ (or other appropriate folder for your setup), then restart the app server to get to load the jar.
4. Go to the admin console and go to Resources -> JNDI -> Custom Resources -> New. Give it a sensible JNDI name (I'll use "testproperties" in this example), enter java.util.Map as the resource type and the name of your factory class for the "factory class" field, e.g. "helpers.jndi.PropertyFactory". Below that under "Additional Properties", add in each of the properties that you want to expose, for example enter a property named "testproperty1" with the value of "my test".
5. You can now get a java.util.Map that contains the properties that you set for your custom JNDI resource by doing something like the following (example in JSP):
<%
Context myContext = new InitialContext();
Context myEnvContext = (Context)myContext.lookup("java:comp/env");
Map myMap = (Map)myEnvContext.lookup("testproperties");
%>
<%=myMap.get("testproperty1")%>Output is:
my testNOTE: If this sounds convoluted - I agree, it is. If anyone's got a better idea, please post it; as I could not find another solution to this seemingly simple problem.

Accessing EnvironmentProperty entries from an EJB

Does anyone know how to access environment entries from within an EJB? One of the examples in the ejb/corba devguide contains the following:
// Add any environment properties that
// the bean requires
EnvironmentProperties {
prop1 = "value1";
prop2 = "value two";
Yet there are no examples or instructions on how to access them anywhere in the document, nor in any of the other Java documents, that I've found.
I've tried the following from within my ejb:
Context Initial = new InitialContext();
String prop1 = (String)initial.lookup("prop1");
This does not work. Neither does a string of the form "java:comp/env/prop1".
Anybody know how to access these properties?
Cheers,
ax
null

In answer to my own question, use the SessionContext getEnvironment() method.
ax
null

Environment variable and spring

Hi all, we are getting this when trying to run our app in Oracle 904:
org.springframework.beans.factory.access.BootstrapException: Define an environment variable [java:comp/env/ejb/BeanFactoryPath] containing the class path locations of XML bean definition files; nested exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/BeanFactoryPath
javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/BeanFactoryPath
 at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
 at javax.naming.InitialContext.lookup(InitialContext.java:345)
 at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:123)
 at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
 at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
 at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:71)
 at org.springframework.context.access.ContextJndiBeanFactoryLocator.useBeanFactory(ContextJndiBeanFactoryLocator.java:64)
 at org.springframework.ejb.support.AbstractEnterpriseBean.loadBeanFactory(AbstractEnterpriseBean.java:117)
 at org.springframework.ejb.support.AbstractStatelessSessionBean.ejbCreate(AbstractStatelessSessionBean.java:63)
 at MethodInvokerHome_StatelessSessionHomeWrapper1.callCreate(MethodInvokerHome_StatelessSessionHomeWrapper1.java:115)
 at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.ejb.StatelessSessionEJBHome.getContextInstance(StatelessSessionEJBHome.java:275)
 at MethodInvokerRemote_StatelessSessionBeanWrapper0.invoke(MethodInvokerRemote_StatelessSessionBeanWrapper0.java:77)
 at java.lang.reflect.Method.invoke(Native Method)
 at org.springframework.remoting.rmi.RmiClientInterceptorUtils.doInvoke(RmiClientInterceptorUtils.java:103)
 at org.springframework.ejb.access.SimpleRemoteSlsbInvokerInterceptor.doInvoke(SimpleRemoteSlsbInvokerInterceptor
Basically the app server thinks there is no environment entry but I have it declared in ejb-jar.xml descriptor:
<env-entry>
<env-entry-name>ejb/BeanFactoryPath</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>applicationContext.prod.xml</env-entry-value>
</env-entry>
Any ideas,
J

u need display in order to have a graphical env with font, raster and all this information is taken from the ip address to which u have set the DISPLAY
Also make sure xwindows is running. U can check whether DISPLAY has been configured properly by running xclock
Best Regards
Rajesh Alex

Environment entries

Similar Messages

Maybe you are looking for