Can anybody really deploy a WAR file?

[icordoba]

Hi there,
after spending 15 days reading messages in this forum, I'd like to know if anybody has been capable of deploying a WAR file that references to EJBs deployed in another .jar .
I've seen many people with exactly the same problema as I have, but noone has yet posted the procedure to check the jboss.xml and jboss-web.xml files, along with that <ejb-link> tag that must be present in ejb-jar.xml:

org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: ejb-local-ref: ejb/skios/UserManagerLocal, target not found, add valid ejb-link)

I've checked my xml descriptors many times and they seem to be OK. They even work perfect in other application servers.
Is there any tutorial that explains how to deploy jars in JBoss? But jars developed with other IDEs than XDocklet and Ant...
I don't have any problem with buing JBoss docs, but do they cover this?

thanks for any help

[jmoring]

You must package the WAR and the EJB jar into an EAR file inorder to access EJBs via local interfaces from a servlet. As an alternative, the remote interfaces are optimized, thus the use of the local interfaces are probably not necessary. We use the EAR file approach with great success.

Hope this helps

[icordoba]

Thanks a lot for your reply,
I had read about what you say, but I also use Pramati Studio J2EE IDE builtin J2EE server and it is capable of deploying separate jars and wars without any problem.
In development time, it is much faster to be able to deploy just the files you change. that is why I was looking for a way to do it in JBoss.

Thanks again,
Ignacio

[jmoring]

You can do that. But you must use remote interfaces not local interfaces.

[thstory]

During development I deploy war and jar file with no problems. I don't have to make changes whether I place the jar & war into an ear or separately. For even quicker development, use Jboss' ability to deploy to a directory that *looks* like the structure of the archive you're deploying. It's very simple and it sped up my development (huge project) by a factor of 10.