java.lang.NoSuchMethodException org.jboss.ejb.EjbModule.<init>
gbhatia8 Sep 9, 2010 1:49 AMHi,
When Im trying to deploy pm-ejb.jar (ejb 1.1) on JBOSS AS 5.0.1GA, Im getting the below mentioned error.
NOTE: I have updated the DOCTYPE from 1.1 to 2.0.
This jar contains 2 xml files
1..ejb-jar.xml with content
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>common.ProcessMonitor</ejb-name>
<home>com.equant.common.ejb.ProcessMonitor.ProcessMonitorSBHome</home>
<remote>com.equant.common.ejb.ProcessMonitor.ProcessMonitorSB</remote>
<ejb-class>com.equant.common.ejb.ProcessMonitor.ProcessMonitorSBBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
<env-entry-name>subcontext</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ProcessMonitor</env-entry-value>
</env-entry>
</session>
</enterprise-beans>
</ejb-jar>
2..jboss.xml with content
<?xml version="1.0"?>
<jboss>
<enterprise-beans>
<session>
<ejb-name>common.ProcessMonitor</ejb-name>
<jndi-name>common.ProcessMonitor</jndi-name>
</session>
</enterprise-beans>
<!--<container-configuration>
<call-logging>false</call-logging>
<instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
<container-pool-conf>
<MaximumSize>10</MaximumSize>
<MinimumSize>1</MinimumSize>
</container-pool-conf>
</container-configuration>-->
</jboss>
=======
ERROR:
=======
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/D:/Software/forJBOSSMigration/jboss-5.0.1.GA/server/default/deploy/ibmpm.war/"
is in error due to the following reason(s): java.lang.NoSuchMethodException org.jboss.ejb.EjbModule.<init>(org.jboss.deployers.vfs.spi.structure.VFSDeploymentUnit, org.jboss.metadata.ApplicationMetaData)
09:44:32,072 INFO [STDOUT] 171127 [main] ERROR org.jboss.system.server.profileservice.ProfileServiceBootstrap - Failed to load profile: Summary of incomplete deployment
s (SEE PREVIOUS ERRORS FOR DETAILS):
Can anybody help me out with this ?