Why is Websphere EJB files genereated, but not JBoss?

Mick Knutson Thu, 21 Jul 2005 10:26:05 -0700

ManagerBean:
===========
/**
* Bean implementation class for Enterprise Bean: ConsumerManagerBean
*
* @ejb.bean    name="ConsumerManager"
*              display-name="Consumer Manager Session Bean"
*              type="Stateless"
*              view-type="local"
*              local-jndi-name="local/ConsumerManagerLocal"

*local-business-interface="com.blackhawk.ff.service.ConsumerManager"

*
* @ejb.home local-extends="javax.ejb.EJBLocalHome"

* @ --ejb.interface local-extends="ConsumerManager,javax.ejb.EJBLocalObject"

* @ejb.interface local-extends="javax.ejb.EJBLocalObject"
*
* @jboss.container-configuration name="Standard Stateless SessionBean"
*
* @websphere.container-configuration name="Standard Stateless SessionBean"
* @websphere.bean
*
* @ejb.env-entry   name="ejb/BeanFactoryPath"
*                  type="java.lang.String"
*                  value="applicationContext.xml"
*
* @ --mock.generate
* @ejb.util generate="physical"
* @ejb.transaction type="Required"
* @ejb.transaction-type type="Container"
* @ejb.permission unchecked="true"
*/



project.xml dependancies:
=====================
       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xjavadoc</artifactId>
           <version>1.0.2</version>
       </dependency>

       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet</artifactId>
           <version>1.2.3</version>
       </dependency>

       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet-xdoclet-module</artifactId>
           <version>1.2.3</version>
       </dependency>

       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet-ejb-module</artifactId>
           <version>1.2.3</version>
       </dependency>

       <dependency>
           <groupId>jboss</groupId>
           <artifactId>jboss-j2ee</artifactId>
           <version>3.2.1</version>
       </dependency>

       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet-ibm-module</artifactId>
           <version>1.2.3</version>
       </dependency>

       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet-mockobjects-module</artifactId>
           <version>1.2</version>
       </dependency>
       <dependency>
           <groupId>xdoclet</groupId>
           <artifactId>xdoclet-web-module</artifactId>
           <version>1.2.3</version>
       </dependency>



project.properties:
========================================================
#//-------------------------------------------------------------------------------------------------------------------//
#// XDoclet Configuration
maven.xdoclet.ejbdoclet.entitybmp.0=false
maven.xdoclet.ejbdoclet.entitycmp.0=true
maven.xdoclet.ejbdoclet.entityfacade.0=true
maven.xdoclet.ejbdoclet.entitypk.0=true
maven.xdoclet.ejbdoclet.homeinterface.0=true
maven.xdoclet.ejbdoclet.localhomeinterface.0=true
maven.xdoclet.ejbdoclet.localinterface.0=true
maven.xdoclet.ejbdoclet.remoteinterface.0=true
maven.xdoclet.ejbdoclet.session.0=false
maven.xdoclet.ejbdoclet.utilobject.0=true
maven.xdoclet.ejbdoclet.utilobject.0.cacheHomes=true
maven.xdoclet.ejbdoclet.utilobject.0.includeGUID=true

maven.xdoclet.ejbdoclet.deploymentdescriptor.0=true
maven.xdoclet.ejbdoclet.deploymentdescriptor.0.destDir=${maven.build.dir}/xdoclet/ejbdoclet/META-INF


maven.xdoclet.ejbdoclet.valueobject.0=true
maven.xdoclet.ejbdoclet.fileset.0.sourcedir=${basedir}/src/java


#//-------------------------------------------------------------------------------------------------------------------//
#// The following items are used to generate JBoss specific files.

#// We are using JBoss for local development, so the build must co-deployonto JBoss and Websphere.

maven.xdoclet.ejbdoclet.jboss.0=true
maven.xdoclet.ejbdoclet.jboss.0.useIds=true
maven.xdoclet.ejbdoclet.jboss.0.Version=4.0
maven.xdoclet.ejbdoclet.jboss.0.createTable=true
maven.xdoclet.ejbdoclet.jboss.0.datasource=java:/defaultDS
maven.xdoclet.ejbdoclet.jboss.0.datasourceMapping=DB2
maven.xdoclet.ejbdoclet.jboss.0.xmlencoding=UTF-8
maven.xdoclet.ejbdoclet.jboss.0.validateXML=true

maven.xdoclet.ejbdoclet.jboss.0.destDir=${basedir}/target/xdoclet/ejbdoclet/META-INF
#maven.xdoclet.ejbdoclet.jboss.0.mergeDir=${maven.build.dir}/temp/mergedir


#//-------------------------------------------------------------------------------------------------------------------//
#// The following items are used to generate Websphere specific files.

#// We are using Websphere for production releases, so the build mustco-deploy onto JBoss and Websphere.

maven.xdoclet.ejbdoclet.websphere.0=true
maven.xdoclet.ejbdoclet.websphere.0.useIds=true
maven.xdoclet.ejbdoclet.websphere.0.Version=5.1
maven.xdoclet.ejbdoclet.websphere.0.xmlencoding=UTF-8
maven.xdoclet.ejbdoclet.websphere.0.validateXML=true

maven.xdoclet.ejbdoclet.websphere.0.destDir=${basedir}/target/xdoclet/ejbdoclet/META-INF

The WAS 5.1 xmi files are created just fine, but not the JBoss files(jboss.xml).





Thank You
Mick Knutson

Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com

HP Consulting Services (Walnut Creek, CA)



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

Why is Websphere EJB files genereated, but not JBoss?

Reply via email to