Win a copy of Modern JavaScript for the Impatient this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Error deploying jar file!

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While trying to deploy a jar file on WAS, foll. error is encountered :
com.ibm.etools.archive.exception.ResourceLoadException: IWAE0007E Could not load resource "META-INF/application.xml" in archive ....
.
.
com.ibm.etools.archive.exception.ArchiveRuntimeException: Invalid binaries path: D:\Program Files\WebSphere\AppServer/installedApps/MC101/TESTEJB_jar.ear
any possible reasons ??
Thanks
 
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Amit
why have you created a directory inside installedApps??
copy the EAR file to installableApps & then deploy it...
 
Amit Mathur
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying to deploy through admin console of WAS from a remote machine.
And that directory inside installedApps is the node name of the server.
I believe that node is created when we setup the server?
 
Vinod Bijlani
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
then the ESTEJB_jar.ear does not confirm to J2EE 1.2 or 1.3. my guess is u have got a wrong application.xml in ear.
try to open the ear in winzip & check the package structure
 
Amit Mathur
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks...
We were making the jar from WSAD. When we tried making the jar from another WSAD setup and deployed on WAS it worked.
Thanks again
 
Right! We're on it! Let's get to work tiny ad!
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic