Problem deploying on WS 6.1: jndi missing in ibm-web-bnd.xmi

Home Forums MyEclipse IDE WebSphere Development Problem deploying on WS 6.1: jndi missing in ibm-web-bnd.xmi

This topic contains 3 replies, has 2 voices, and was last updated by Profile photo of support-swapna support-swapna 3 years, 3 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #325508
    Profile photo of Tarrasque


    I’m switching to MyEclipseBlue 10 for developing and deploying to a WebSphere 6.1 server.

    If I develop my ear on regular Eclipse and package with Maven, the resulting EAR can pe deployed and started with the admin console without problems.

    If I try to deploy with MyEclipse, I get these errors in the deployment.log

    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/ZH-devDS in module incassi-webfe-0.0.1-SNAPSHOT.war with EJB name {3}.

    And the application doesn’t start nor shows on the admin console.

    The datasources are configured correctly on WS and web.xml and we never had those errors with regular Eclipse.

    I looked around and I found out that this kind of errors could be related to discrepancies between wex.xml and file ibm-web-bnd.xmi and in facts, this file is COMPLETELY MISSING in the war generated py MyEclipse during deploy.

    Can anybody help?

    Profile photo of support-swapna


    Sorry that you are seeing this issue.

    Can you answer some more questions for us ?

    1. Can you please share the Installation Details from MyEclipse > Installation Summary > Installation Details ? Paste them here for us.

    2. In which version of Eclipse did you develop the EAR ? Which version of Maven did you work with in Eclipse IDE ?

    3. Are you creating the EAR in MyEclipse or importing the one developed in Eclipse ? Please list out the steps you are following for us to help replicate the issue at our end.

    4. ibm-web-bnd.xmi is not generated by MyEclipse. You can use the xdoclet plugin that comes with MyEclipse. Use the webspherewebxml sub task of webdoclet to generate the ibm specific ibm-web-ext.xmi and ibm-web-bnd.xmi files. Take a look at this tutorial:

    5. Clear the contents of the deployment log, now try to deploy the project and paste the entire contents of the deployment log here to investigate further.

    Profile photo of Tarrasque

    Thank you very much for the support.

    By copying the .xmi files that Indigo generated and putting them in the MyEclipse project’s WEB_INF folder I’m now able to deploy an EAR that shows up regularly on the WS console.

    I have now problems when I start the server, though. The problem seems to be in the fact that we set up our project using Maven, and we make extensive use of Maven profiles and filters to fill in some configuration properties depending on the target server we want to deploy the ear to (for example: link URLs, homepage titles, logos, etc.)

    When MyEclipse compiles and deploys on the WS in my development machine, cah I specify a MAven profile (or some equivalent action) in order to solve this problem?


    Profile photo of support-swapna


    You can specify the profiles in the pom.xml or settings.xml. Take a look at this link :

    Please take a look at this thread to run the profiles specified within pom.xml :

    Let us know if you see any issues.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

We are experiencing a server disruption at and will have the site back up shortly. Sorry for the inconvenience.

about 11 hours ago

Follow us on social media


Hello developers of the world!Genuitec is pleased to announce the release of Webclipse. Webclipse comes loaded with features that are aimed to cover many missing pieces of Eclipse for Web development. At Genuitec, we are a family of programmers fr...