• 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Websphere 6.1 deployment questions & problems (ejbDeploy)

Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I get errors while deploying an ear file to WAS 6.1.

In short, I developed the project under RAD 7 and was testing it by publishing it to a local WAS 6.1 installation.
Doing that RAD also creates deployment code for the one stateless session bean.
Then I was producing an EAR file by right clicking the EAR project and exporting it directly from withing RAD.

But now, the ear file is not being created by myself anymore. An Ant script generates the package.

When deploying the new ear file to WAS through WAS Console, WAS tries to generate ejb deployment code but fails.

My questions :
1) "The project was not built since its build path is incomplete. " How and where can I set the build path ?
2) (The declared package "a.b.c.util" does not match the expected package "ejbModule.a.b.c.util") - What does that mean ? and how can I solve it ?
3) "The method toString(int) in the type Integer is not applicable for the arguments (Integer)" - That sounds like a Java 1.4 - 1.5 problem, but why ? the javac -version command gives this output :

/ibm/WebSphere/AppServer/java/bin:>./javac -version
javac 1.5.0
javac: no source files

Other log output is like this :
Type mismatch: cannot convert from int to Integer
Type mismatch: cannot convert from Long to long

Websphere level is on AIX. But I get the same result on Windows (, too.

Can anybody help me on this ?
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I faced similar problem while deploying ear with ejbs. EJBDeploy Task of Dmgr will first try to compile all the session beans.Hence the Jars for the classes which are directly referenced in EJB Session Beans should be mapped in the META-INF/application.xml of EAR or META-INF/MANIFEST.MF of EJB project or inside appserver lib.

If you want to have these Jars reside in shared library only. Then the option is while deploying your application, please choose the Detailed Path and then on ejb deploy options page there will be an option to provide classpath.
input the jar files with absolute paths which needs to be referenced by application in this classpath option(text box) and proceed with further steps to complete deployement successfully.

refer to the below link for more information.

Just let me do the talking. Ahem ... so ... you see ... we have this tiny ad...
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic