ejb-jar.xml a clear definition for EJB3

[Alessandro Ilardo]

Hi there,
I'm facing a problem which is probably quite common with newbie like me. There a lot of informations and tutorials on the net, but they're quite different between eachother. So in the end we are just confused and we are not sure about we are following the good procedure.

I'm ok with Persistence and EJB3 annotations (for the moment), but I'm stuck with the configuration files.

First of all, with the annotations, do we still need the ejb-jax.xml? And if yes, how should it look like, at least the minimum tags required by JBoss 4.1

Same question for the jboss.xml.

I'm trying to deploy an EJB Module which implements Hibenate and EJB3, is it correct rename the package as .ejb3 instead of .jar?

I hope that someone with more experience then me help me in keep this thread active as I think to not be the only person facing these issues.

Thanks in advance

[Raghu Kodali]

The answer for your first question, you don't require an ejb-jar.xml if you have annotated the classes. In other words it is not mandatory, you can have both if need be and at deployment time, the settings in the deployment descriptor (ejb-jar.xml) overwrite the annotations.

I think the .ejb3 extension was specific to JBoss early releases of ejb3. The standard is to use .jar. Having said that I didn't check the latest version of JBoss.

raghu
Beginning EJB 3 Application Development

[Alessandro Ilardo]

thank you very much for your explanation, I hope that it will help other people. In anycase, I think that there're too many standards for implementing and running EJB3, especially for configuration files.
Thank you again.