[defiant42]

I’ve created a very simple Enterprise Project (J2EE 1.4) that has a single Session Bean in an EJB Project (J2EE 1.4), and a Simple Struts Project (J2EE 1.4), and trying to deploy to a WebSphere 6.1.0.17 Server, and am getting the following error during the -ejbdeploy phase:

-deployejb
WASX7017E: Exception received while running file “C:\apps\MyEclipse6.5Blue\myeclipse\eclipse\plugins\com.genuitec.eclipse.blue.websphere61_6.5.0.zmyeclipse650200806\installEAR.jacl”; exception information: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: IWAE0022E Exception occurred loading deployment descriptor META-INF/application.xml for module “TestProjectEJB.jar” in EAR file “C:\Documents and Settings\ZMM0362\Local Settings\Temp\app64916.ear”

A couple of other items to note:

* This project WOULD deploy FINE on WAS 6.1.0.13. However, I was getting context.lookup errors when trying to lookup the session bean via JNDI. Our production enviro is 0.17, so I needed to get there anyway.

* Created an Enterprise Project (1.4) WITHOUT the EJB Project and it deploys fine. I’ve also commented out the <display_name> element in the application.xml (this fixed an earlier deployment problem).

* When I upgraded from 0.13 to 0.17 My original server profiles (0.13 version) were preserved, so first tried to using the original server profile, no luck.

* Next, I created a NEW server profile (0.17 version), and get the same error in both cases.

Any help would be greatly appreciated.

Eric

Below is the installation summary of the ME-Blue that I’m running:

*** Date:
Thursday, August 14, 2008 11:00:50 AM CDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_14

*** MyEclipse details:
MyEclipse Blue Edition
Version: 6.5.0 Blue GA
Build id: 6.5.0-Blue-GA-20080609

*** Eclipse details:
MyEclipse Blue Edition

Version: 6.5.0 Blue GA
Build id: 6.5.0-Blue-GA-20080609

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\apps\MyEclipse6.5Blue\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\apps\MyEclipse6.5Blue\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\apps\MyEclipse6.5Blue\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
145c_78
-clean
-showlocation
-data
C:\dev\eclipse\ws8
-vmargs
-Xmx1536m
-vm
C:\apps\MyEclipse6.5Blue\jre\bin\javaw.exe

[Loyal Water]

defiant42,
Can you update to MyEclipse 6.5.1 and test this again. This was a know issue that was fixed in the 6.5.1 release.

Let me know if the problem persists after upgrading.

[defiant42]

Yes. Will give that a try.

Eric

[defiant42]

This appears to have FIXED IT!

Eric

[Author]

Posts