JNDI lookup help please-Bean to Bean callout locally in same oc4j container

Question

Hi - I'm fairly new to oc4j/ejb coding - I'm trying to get a simple application running to show that our code can be run in local mode - here is the scenario:
- Bean A (our application bean) within Application A
- Bean B (customer-developed bean) within Application B
- Bean B calls Bean A
- Bean A + Bean B are different application instances in the same oc4j container
- Jsp (residing in ApplicationB) within the same oc4j container calling Bean B, which invokes Bean A
====
I get the following exception (classes renamed to match scenario):
javax.naming.NameNotFoundException: oracle.apps.applicationa.common.BeanA not found in anothercompany.applicationb.common.BeanB
[java] at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:93)
[java] at com.oracle.naming.J2EEContext.lookup(J2EEContext.java:76)
[java] at com.evermind.server.ApplicationContext.lookupJavaCompEnv(ApplicationContext.java:265)
[java] at com.evermind.server.ApplicationContext.lookupJavaComp(ApplicationContext.java:132)
[java] at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:306)
[java] at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:120)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
- BeanA is part of application named "AppA" in server.xml
- BeanB is part of application named "AppB" in server.xml
- AppB has attribute 'parent="AppA"' in server.xml
- If I change the Jsp file (residing in AppB) to call BeanA directly in the jsp code it works with no JNDI error, but changing the jsp code back to calling BeanB (which then calls BeanA) will throw the NameNotFoundException
My Stateless Session Bean is very simple and I have tried not setting the context and setting the context. I'm thinking this is a very simple configuration issue, but have not been able to find the solution yet... I've tried playing with the setSessionContext method in the session bean but have had no luck and am not sure what to set the variables to or even if I'm in the correct method...
public void setSessionContext(SessionContext ctx) {   
if (verbose)
System.out.println("setSessionContext called");
Properties env = new Properties();
// tried all three context factories...
//env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.ApplicationInitalContextFactory");
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.ApplicationClientInitialContextFactory");
//env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.rmi.RMIInitialContextFactory");
// not sure what url to put, if any
//env.put(Context.PROVIDER_URL, "ormi://localhost:23791/AppB");
env.put(Context.PROVIDER_URL, "ormi://localhost/AppB");
// tried with and without security principals... also tried sysadmin/sysadmin
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
// mProps is a local transient member var of type Properties
mProps = env;
// mCtx is a local transient member var of type SessionContext
mCtx = ctx;
(edit) additional info:
- all beans/classes are in the same classes directory; there are no jar files, so in application.xml the specified classpath is "classes" which includes both appA and appB classes
- I verified that if I point (appB) jsp directly to BeanA it works with the "parent" attribute set on appB in server.xml, and when I remove the "parent" attribute on appB in server.xml the jsp throws a NameNotFoundException
edit #2:
another interesting note is that the exception message says "oracle.apps.applicationa.common.BeanA not found in anothercompany.applicationb.common.BeanB"
and usually the naming error I see is:
"oracle.apps.applicationa.common.BeanA not found in appB"
(as with the case when I use a jsp to access appA beans without setting the parent application of appB to appA)
- also my j2ee/home/applications/appB/WEB-INF/web.xml includes the oracle.apps.applicationa.common.BeanA ejb-ref tag
any help is appreciated - thanks!
Message was edited by:
oleon

Answer 1

Hi Steve
thanks for the reply - I currently have the parent attribute set in server.xml which is why the jsp connection works, but for some strange reason the bean cannot connect to other bean...
my server.xml has something like...
<application name="appA" location="appA" auto-start="true"/>
<application name="appB" location="appB" parent="appA" auto-start="true"/>
(ok, the tags might be off because I'm not in front of my workstation looking at the xml file...)
on another interesting note, in the session bean for AppB I've tried searching for the ejb bean for app B (itself basically) with the default initial context and it cannot find its own bean within the same application... the message would be something like "NameNotFoundException: anothercompany.applicationb.common.BeanB not found in anothercompany.applicationb.common.BeanB"