I'm not following. It IS a JAR and there is nothing special about it other than the annotations which is only relevant at deployment time to the container.
One of the major design goals of EJB3 is to have less overhead with respect to the number of deployment artifacts and to be more POJO centric. The current Maven EJB plugin as I understand it is written to alleviate the complexities of the side artifacts one would normally have to create when creating older version EJB based applications. There is a usage mismatch (I could be wrong) between the current Maven EJB plugin and EJB3 deployments (or at least JBoss EJB3 deployments, I won't speak for other containers). Finally, JBoss specifically treats EJB3 based applications as simple JARs (you can deploy EJB3's in JAR format without including them in an EAR and the Eclipse based EJB3 plugin is last I checked simple classpath containers pointing to the appropriate EJB3 JBoss libraries to link against). As for including them in an EAR, yes they are just listed as a dependency and javaModule. -aps On 12/28/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
On 12/28/06, Alexander Sack <[EMAIL PROTECTED]> wrote: > I'm not sure why you are using the EJB plugin since EJB3 and JBoss are just > JARs. We use EJB3 and JBoss exclusively and I prefer the JAR plugin. If your EJB3 project is built with the 'jar' packaging, it is handled as a library by the EAR plugin (namely). The concept of artifact's type is important so what you're doing sounds more like a hack. What do you do when you generate an EAR with your EJB archives declared with a 'jar' type. Regards, Stéphane > > -aps > > On 12/27/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > On 12/26/06, Vitor Pellegrino <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > > > > 1 - How can i deploy my project using maven to my Jboss AS instance? > > > > Have a look to cargo. > > > > > > > When i try to do a "mvn ejb:ejb" it is lacking for a ejb-jar.xmlfile > > and at > > > the plugin's usage page it's says that it's not mandatory anymore. > > > > Set the packaging of your project to EJB. Regarding the fact that > > ejb-jar is not mandatory, I think it's not released yet so you'll have > > to take the snapshot (the doc is the doc of the dev version). > > > > > It seems i am losing some point because i don't know where else more > > should > > > i look for these answers. > > > > Take an hour and check "Better builds with Maven" book, it will help > > jumping on board > > > > Let us know how you go. > > > > Cheers, > > Stéphane > > > > > > > > > > Thanks for any help! > > > > > > PS: Sorry about my english, it's not my first tongue. I hope i could > > made > > > myself understood. > > > > > > -- > > > Vitor Pellegrino > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
