- This topic has 2 replies, 2 voices, and was last updated 17 years, 4 months ago by Loyal Water.
-
AuthorPosts
-
panickertMemberHello,
This is probably a silly question. Here it goes, I’ve created an enterprise application project then added 2 existing ejb projects and a web project to build the ear. Subsequently, deployed the ear to the server (JBoss 4.2.1).
The generated application.xml contained the likeness of the following – note that the project lacks .jar extension. Mind you that i did the new module manifest generation.
<module id=”myeclipse.1159311389959″>
<ejb>EJB.Readiness</ejb>
</module>However, when the server starts up, i get the following error
org.jboss.deployment.DeploymentInfo@32095a04 { url=file:/C:/java/jboss-4.2.1.GA/server/myconfig/tmp/deploy/tmp6819SPV.EARs.ear-contents/EJB.Readiness }
deployer: null
status: Starting
state: START_SUBDEPLOYMENTS
watch: file:/C:/java/jboss-4.2.1.GA/server/myconfig/tmp/deploy/tmp6819SPV.EARs.ear-contents/EJB.Readiness
altDD: null
lastDeployed: 1186600410250
lastModified: 1186600410235
mbeans:If I deployed the EJB’s independently with the jar extension everything seems to be fine. What you think I am doing wrong? How can i get the ear to deploy the subsequent EJB’s with jar extensions?
Following is the installation info.
thanks in advance.
*** Date:
Wednesday, August 8, 2007 2:56:30 PM EDT** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.5.1 GA
Build id: 20070521-5.5.1-GA*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 5.5.1 GA
Build id: 20070521-5.5.1-GAEclipse Platform
Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
Build id: M20070212-1330Eclipse RCP
Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
Build id: M20070212-1330Eclipse Java Development Tools
Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
Build id: M20070212-1330Eclipse Plug-in Development Environment
Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20070212-1330Eclipse Project SDK
Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
Build id: M20070212-1330Eclipse Graphical Editing Framework
Version: 3.2.2.v20070208
Build id: 20070208-1315Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse\MyEclipse5.5GA\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
aac_dc
-vm
C:\eclipse\MyEclipse5.5GA\jre\bin\javaw.exe
panickertMemberLittle more info…
If I add .jar extension as following to the application.xml and manually rename the deployed EJB project to EJB.Readiness.jar every thing is peachy again. But I shouldn’t have to do that manually…<module id=”myeclipse.1159311389959″>
<ejb>EJB.Readiness.jar</ejb>
</module>
Loyal WaterMemberHi panickert,
Actually this is by design. When you name a project with a suffix included we assume that the suffix has meaning. As such, we don’t augment it further. This allows people to create .rar projects and other types that need specfiic suffixes at deployment time other than .jar.To work around, rename the project EJB_Readiness
-
AuthorPosts