OC4J 9.0.3: ctx.listBindungs causes NameNotFoundException

Question

Hello,
this is a repost of a message allready posted a couple of days before, see Re: JDeveloper 10.1.3.0.4 and JSTL Core 1.1 . But I can't find that posting in the list anymore, so here it' once again...
Hello,
I've got a problem with Context.listBindings, using OC4J 9.0.3 build 020725.1695 with JDK 1.3.1_04 on W2K with SP2. From within a bean I do something like this:
try
javax.naming.Context ctx = new javax.naming.InitialContext();
javax.naming.NamingEnumeration enum = ctx.listBindings("java:comp/env");
Object each = null;
while (enum.hasMoreElements()) {
each = enum.next();
System.out.println(each.toString());
} catch (Exception ex) {
ex.printStackTrace();
And get this list:
jms/EJBTopic: com.evermind.server.jms.EvermindTopic:[Topic: Demo Topic]
jms/EJBQueue: com.evermind.server.jms.EvermindQueue:[Queue Demo Queue]
jdbc/EJBDataSource: com.evermind.sql.OrionCMTDataSource:com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleDS
ejb/dependencies/entityBeans_Account: com.evermind.server.ejb.DelayedHomeBinding:com.evermind.server.ejb.DelayedHomeBinding@2aa1ce
ejb/dependencies/entityBeans_AccountLocal: com.evermind.server.ejb.DelayedHomeBinding:com.evermind.server.ejb.DelayedHomeBinding@64dbfb
ejb/references/TheAddress/AddressLocal: com.evermind.server.ejb.DelayedHomeBinding:com.evermind.server.ejb.DelayedHomeBinding@2646f7
ejb/associations/TheAddress/Address: com.evermind.server.ejb.DelayedHomeBinding:com.evermind.server.ejb.DelayedHomeBinding@7d357f
jms/EJBTopicConnectionFactory: com.evermind.server.jms.EvermindXATopicConnectionFactory:com.evermind.server.jms.EvermindXATopicConnectionFactory@1ac263
jms/EJBQueueConnectionFactory: com.evermind.server.jms.EvermindXAQueueConnectionFactory:com.evermind.server.jms.EvermindXAQueueConnectionFactory@670dfb
But if I try to list the bindings for the jndi path "java:comp/env/ejb" I get a NameNotFoundException:
javax.naming.NameNotFoundException: ejb not found in Customer
at com.evermind.naming.MapContext.lookup(MapContext.java:61)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:124)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:66)
at com.evermind.server.ApplicationContext.listBindings(ApplicationContext.java:390)
at javax.naming.InitialContext.listBindings(InitialContext.java:394)
at entityBeans.CustomerBean.getAccountCount(CustomerBean.java:68)
at Customer_EntityBeanWrapper20.getAccountCount(Customer_EntityBeanWrapper20.java:2182)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:103)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:
Can anyone help us with this issue?
Here are some parts of ejb-jar.xml and orion-ejb-jar.xml:
<entity >
<display-name>Customer</display-name>
<ejb-name>Customer</ejb-name>
<home>entityBeans.CustomerHome</home>
<remote>entityBeans.Customer</remote>
<local-home>entityBeans.CustomerLocalHome</local-home>
<local>entityBeans.CustomerLocal</local>
<ejb-class>entityBeans.CustomerBean</ejb-class>
<ejb-ref >
<ejb-ref-name>ejb/associations/TheAddress/Address</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>entityBeans.AddressHome</home>
<remote>entityBeans.Address</remote>
</ejb-ref>
<ejb-ref >
<description>ejb-ref for dependency (entityBeans_Account)</description>
<ejb-ref-name>ejb/dependencies/entityBeans_Account</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>entityBeans.AccountHome</home>
<remote>entityBeans.Account</remote>
</ejb-ref>
<ejb-local-ref >
<ejb-ref-name>ejb/references/TheAddress/AddressLocal</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>entityBeans.AddressLocalHome</local-home>
<local>entityBeans.AddressLocal</local>
</ejb-local-ref>
<ejb-local-ref >
<description>ejb-local-ref for dependency (entityBeans_Account)</description>
<ejb-ref-name>ejb/dependencies/entityBeans_AccountLocal</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>entityBeans.AccountLocalHome</local-home>
<local>entityBeans.AccountLocal</local>
</ejb-local-ref>
<resource-ref >
<description>resource reference to the test data source</description>
<res-ref-name>jdbc/EJBDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref >
<description />
<res-ref-name>jms/EJBQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref >
<description />
<res-ref-name>jms/EJBTopicConnectionFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-env-ref >
<description />
<resource-env-ref-name>jms/EJBQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
<resource-env-ref >
<description />
<resource-env-ref-name>jms/EJBTopic</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
</resource-env-ref>
</entity>
<entity-deployment
name="Customer"
location="Customer"
call-timeout="90"
copy-by-value="True"
max-tx-retries="3"
data-source="jdbc/OracleDS"
disable-wrapper-cache="False"
do-select-before-insert="False"
exclusive-write-access="False"
force-update="False"
instance-cache-timeout="60"
isolation="serializable"
locking-mode="optimistic"
max-instances="10"
min-instances="0"
max-instances-per-pk="50"
min-instances-per-pk="0"
pool-cache-timeout="60"
table="T_CUSTOMER"
update-changed-fields-only="True"
>
<ejb-ref-mapping location="Account" name="ejb/dependencies/entityBeans_Account"/>
<ejb-ref-mapping location="Address" name="ejb/associations/TheAddress/Address" />
<resource-ref-mapping location="jdbc/OracleDS" name="jdbc/EJBDataSource" />
</entity-deployment>
Hope anyone can help...
Regards
Stefan

Answer 1

Hello,
this is a repost of a message allready posted a couple of days before, see Re: JDeveloper 10.1.3.0.4 and JSTL Core 1.1 . But I can't find that posting in the list anymore, so here it' once again...Hi,
The reason the post not showing up, is likely due to one or several bugs in this Forums software. Please read these and "join the club" :)
Re: Plz Urgent SQL problem
Re: Moving / Coping processes flows between process packages
Cheers,
Fredrik