[jmzD]

I tried posting my issues in the Blue forum, but no one has responded so I am cross posting (and i have done my research…)

I am getting this error when attempting to deploy to Websphere 6.1 using MyEclipseBlue

WASX7017E: Exception received while running file “C:\apps\MyEclipse Blue 7.0 M2\eclipse\plugins\com.genuitec.eclipse.blue.websphere61_6.9.200.zmyeclipse69200200809\installWebModule.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task “MapResRefToEJB

ADMA0007E: A Validation error occurred in task Mapping resource references to resources. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding jdbc/datasource_SQL2005 in module dining.war with EJB name {3}.”

This issue is rather annoying as I do not have any EJB’s in the application or the web.xml file, and when it is installed directly onto Websphere the application works almost perfectly (I am trying to do hot deploy to find a bug that is wiping a table in my database). Additionally this same error comes up when i try to hot deploy another application that is already working on my employer’s production servers and in my WAS development environment.

I have tried going in and rewriting the .jacl script mentioned in the first error, but to no avail, as the required parameter for MapResRefToEJB is a list and feeding the function null values results in a different error…

Can anyone provide me some insight into this?

Regards,
James Steele

[Loyal Water]

James,
I’m sorry we missed the previous post. Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

Can you upgrade to MyEclipse 7.0 and test this again. I think you ran into a known issue.

[jmzD]

*** Date:
Wednesday, October 22, 2008 9:24:57 AM PDT

** System properties:
OS=WindowsVista
OS version=6.0.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Blue Edition
Version: 7.0 Blue Milestone-2
Build id: 7.0-Blue-M2-20080915

*** Eclipse details:
MyEclipse Blue Edition

Version: 7.0 Blue Milestone-2
Build id: 7.0-Blue-M2-20080915

Eclipse Project SDK

Version: 3.4.0.v20080522-7O7S-CHEp2gcoGjmFFomLz-d5M8NdvuPgDrH17jw0Mvhe
Build id: I20080617-2000

Eclipse Platform

Version: 3.4.0.v20080610-9I96EhtEm-T_5LxIsybz-3MdGZmOA3uwv7Ka_M
Build id: I20080617-2000

Eclipse Java Development Tools

Version: 3.4.0.v20080603-2000-7o7tEAXEFpPqqoXxgaBhhhq
Build id: I20080617-2000

Eclipse Graphical Editing Framework GEF

Version: 3.4.0.v20080115-677-8082A5696H274A
Build id: 200806091334

Eclipse RCP

Version: 3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB
Build id: I20080617-2000

Eclipse Plug-in Development Environment

Version: 3.4.0.v20080603-7T7U-E_EkMNrNKb39WcMC
Build id: I20080617-2000

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\apps\MyEclipse Blue 7.0 M2\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\apps\MyEclipse Blue 7.0 M2\eclipse\plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800\eclipse_1114.dll
-startup
C:\apps\MyEclipse Blue 7.0 M2\eclipse\plugins/org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar
-exitdata
7c8_4c
-clean
-vm
C:\apps\MyEclipse Blue 7.0 M2\jre\bin\javaw.exe

THE OS IS NOT REALLY VISTA, IT IS MICROSOFT SERVER 2008 STANDARD

[jmzD]

@jmzD wrote:

THE OS IS NOT REALLY VISTA, IT IS MICROSOFT SERVER 2008 STANDARD

It is our Dev Server running WAS.

[jmzD]

Additionally, I have the same error in 6.5 Blue

And I am running WAS 6.1 updated to 19 with and without the EJB3.0 support.

[Riyad Kalla]

Is dining.jar a Web Project? Where is the “jdbc/datasource_SQL2005” data source defined?

It looks like WebSphere is coughing back that message about EJB deployment, but you mentioned there are no EJBs anywhere, which is really odd… trying to figure out why it thinks there is.

Is this a J2EE 1.3, 1.4 or 5.0 project?

[jmzD]

Dining.war is a MyEclipse J2EE Web Project.

The datasource is defined as a constant in my project in a file named DbConfig.properties.

This is a J2EE 1.4 project.

The jacl script does not contain a value for MapResRefToEJB, so is it possible that MyEclipse is making the wrong call to WAS?

If so, is there any way to fake it out to call the proper deployment?

As I said earlier, the app deploys fine and has database functionality when deployed directly to WAS.

[jmzD]

Anyone?

[Loyal Water]

jmzD,
Riyad is not available to answer your query today. He will be back tomorrow. Sorry for the delay.

[Riyad Kalla]

jmzD,

Sorry for the delay, most of us were out at EclipseWorld this week. I’ve put this on the Blue team’s plate to evaluate and assess. Thanks for reporting it and I’m sorry I don’t have an immediate workaround for you right now.

[Riyad Kalla]

jmzD,

Could you kick us an example project that exhibits this behavior? It looks like the use of the JNDI context is not something we support yet and might be causing us to incorrect detect an EJB that needs to be deployed. WE need to do some more testing, but having an example from you that was specifically causing problems would be very helpful.

Could you email it to [email protected] ATTN Riyad, and I’ll send it off to the dev team?

[jmzD]

No problem, I’ll put something together…

[DragonMan]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Author]

Posts