Do you have the JBoss jars and JNDI correct --
Try copy/paste the below and name it run.bat (in the last line java -cp %myCLASSPATH% %myD% client change client to whatever your client's name is):
Looks sloppy here but if you cut/paste into text editor will look normal (this is Windows version but you can adapt for UNIX if needed):
set myD=-Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.provider.url=localhost:1099 -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java -cp %myCLASSPATH% %myD% client
The log you have posted doesn't has any reference to EJBModule. That is when you deploy an ejb corretly the EJBModule logs a message whith the ejb name.
It looks like if the jar file doesn't has the deployment descriptor files corretly. Check the META-INF directory and the deployment descriptors in the jar file.
Right on Juan. Yes that was my problem I must have had some erroneous files in my META-INF.
I didn't even have the entries display in the log for the EJBModule like you said, and now I do.
I now can build and deploy correctly.
Thanks for the responses guys, Its refreshing to not only get feedback vut good suggestions as well.
I've been trying to post this reply
but Hopefully this went through.
Juan you were right on. I must have had some bad files left over in my META-INF. I recreated my ejb-jar and jboss .xml files. I was then able to build and deploy
my jar files.
I now see my EJBModule come up during startup, correctly
displaying my EJB
Thanks to both responses. Its nice seeing questions get answered with great things to try.