- This topic has 2 replies, 3 voices, and was last updated 20 years, 1 month ago by Scott Anderson.
-
AuthorPosts
-
edwardotisMemberhi,
my EJB projects will not deploy to Sun AppServer 8.0, but my WAR files will. Any ideas?
Thanks,
-Ed
.mymetadata file:
<?xml version=”1.0″ encoding=”UTF-8″?>
<project-module
type=”EJB”
name=”librarymanagementgreenEJB”
id=”myeclipse.1101895460613″
j2ee-spec=”1.3″
archive=”librarymanagementgreenEJB.jar” />Error from appserver console:
[#|2004-12-01T02:10:24.967-0800|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\domains\domain1\autodeploy\librarymanagementgreenEJB.jar ] for autodeployment.|#]
[#|2004-12-01T02:10:24.967-0800|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\domains\domain1\autodeploy\librarymanagementgreenEJB.jar. — Unknown deployable object type specified: “Cannot determine the J2EE component type: C:\Sun\AppServer\domains\domain1\autodeploy\librarymanagementgreenEJB.jar — Unknown deployable object type specified: “Cannot determine the J2EE component type: C:\Sun\AppServer\domains\domain1\autodeploy\librarymanagementgreenEJB.jar|#]
.project file:
<?xml version=”1.0″ encoding=”UTF-8″?>
<projectDescription>
<name>librarymanagementgreenEJB</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.genuitec.eclipse.j2eedt.core.DeploymentDescriptorValidator</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.validation.validationbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.sse.model.structuredbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>com.genuitec.eclipse.ast.deploy.core.deploymentnature</nature>
<nature>com.genuitec.eclipse.j2eedt.core.ejbnature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>.classpath
<?xml version=”1.0″ encoding=”UTF-8″?>
<classpath>
<classpathentry kind=”src” path=”src”/>
<classpathentry kind=”con” path=”org.eclipse.jdt.launching.JRE_CONTAINER”/>
<classpathentry kind=”con” path=”com.genuitec.eclipse.j2eedt.core.J2EE13_CONTAINER”/>
<classpathentry kind=”output” path=”classes”/>
</classpath>
Riyad KallaMemberChecking on this, I’m not aware of any funkiness with Sun 8.
Scott AndersonParticipantThe J2EE spec says that only EAR’s really need to be supported. I don’t believe Sun supports EJB jars deployed by themselves. You can get around this by creating an EAR project, adding your EJB project as one of the modules, and deploying the resulting EAR instead.
-
AuthorPosts