Hello,

I wanted to create template project structure for EJB3 application based on the DVD trailblaizer from JBoss site (http://trailblazer.demo.jboss.com/DVDTrail/).

I used Maven2 2.0-beta-1-SNAPSHOT -

I created structure which is available at http://piotr.radzisz.com/maven2/

I would like to know your opinions about the structure I created (what I did wrong, what should be handled different way etc.). I have following problems:

1. There is module demo-par - it is persistence archive file - simple jar file but with extension par instead of jar and added persistence.xml file in the META-INF directory. I set <packaging> element to par but I cannot find where can I find how to bind this packaging type to particular plugin (by the way: jar plugin doesn't allow to create jar files with extension different than jar - already submitted issue in the Maven2 issue tracking system).

2. I found the same problem with the demo-ejb module. Generated artifact should have "ejb3" extension(not jar). How should I resolve this?

3. I am not sure if demo-ear module configuration (pom.xml) is correct. I defined:
<build>
   <plugins>
     <plugin>
       <groupId>org.apache.maven.plugins</groupId>
       <artifactId>maven-ear-plugin</artifactId>
       <configuration>
         <modules>
           <javaModule>
             <groupId>net.bzdyl.demo</groupId>
             <artifactId>demo-utils</artifactId>
             <library>true</library>
           </javaModule>
           <ejbModule>
             <groupId>net.bzdyl.demo</groupId>
             <artifactId>demo-par</artifactId>
           </ejbModule>
           <ejbModule>
             <groupId>net.bzdyl.demo</groupId>
             <artifactId>demo-ejb</artifactId>
           </ejbModule>
           <webModule>
             <groupId>net.bzdyl.demo</groupId>
             <artifactId>demo-war</artifactId>
             <contextRoot>/demo</contextRoot>
           </webModule>
         </modules>
       </configuration>
     </plugin>
   </plugins>
 </build>

I guess that when I specify <ejbModule> then ear plugin will look for *.jar files (not *.par and *.ejb3 files). How should I handle par and ejb3 files in the ear plugin?

I think this kind of the project skeleton could be good start point for EJB 3 projects.

Best regards,
Piotrek

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to