Judging from your object name, I'm guessing your having problems getting a reference object from a JNDI context lookup. I believe this is caused by the absence of a JNDI name/binding for your bean. You can specify/configure this in the jboss.xml file. My file, which declares an entity bean, is as follows (sorry about the excessive comments):
<!--- Name of the bean, must correspond to related --->
<!--- bean declarations in ejb-jar.xml --->
<!--- JNDI binded name of the bean, used to look --->
<!--- up references to the bean's home interface. --->
<!--- Other entity beans are defined here --->
<!--- Session & Messaging beans, as well as other --->
<!--- jboss-related information are defined here. --->
The jboss.xml file goes into the meta inf directory with the ejb-jar.xml file (and any others you need). You don't need to edit the jboss-web.xml or web.xml files, because all necessary configuration is done on the ejb's end, inside its jar file.
Once you have redeployed your jar, you should be able to access your bean fine.
Hope that helps.
Thank you for your help...
I checked my *.xml files and found out that if you want to access your ejb's from within java server pages you have to define an ejb-ref tag in the web.xml and bind this ref to a jndi-name in the jboss-web.xml. The jndi-name should be the same as the one u used in jboss.xml.
It took me at least three days to figure this out, ugh.
(JBoss 3.0 -)
I had the same problems as u did. But I still could not solve it. My ejbs work perfectly well when I use the remote interfaces to access from a jsp page.
But when I use local interfaces it gives me a
NamingException ejb not bound ...add a valid ejb link.
On my part I found out that one has to use ejb-local-ref
<ejb-ref-name>ejb name ref. in jboss.xml</ejb-ref-name>
This too did not work and throwed the same exception.
I also found in the DTD of jboss_web_3_0.dtd that it does not support tags for local ref as in the dtd of web.xml which is from Sun.