Win a copy of Svelte and Sapper in Action this week in the JavaScript 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

EJBDeploy Task Fails

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everybody,
I am having a peculiar problem here. And I cannot figure out where I am going wrong.

I create a .ear through a ANT build.xml. Later I ejbdeploy the .ear file from the command line. However the build fails and gives me the following:

[*Error] /checkstatus: The project was not built since its classpath is incomplete. Can not find the class file for com.lds.pay.app.exceptions.LDSException. Fix the classpath then try rebuilding this project

[*Error] ejbModule/com/lds/pay/app/core/checkstatus/EJSRemoteStatelessChangeChec
kStatus_36918ee3.java(0): This compilation unit indirectly references the missing type com.lds.pay.app.exceptions.LDSException (typically some required class file is referencing a type outside the classpath)

I have also set the JAVA_HOME to the Websphere\Appserver\java.

I have the .jar file which includes all class files under com.lds.pay.app.exceptions and it is very much a part of the .ear that I am trying to ejbdeploy.

Thanks and Regards
Jayashree
 
author & internet detective
Posts: 40200
816
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jayashree,
I'm not following. Is the EJBDeploy ant task giving you the message or are you getting it when you later try to deploy the EAR?

Either way, before you try anything else, make sure LDSException is in your manifest.mf file for the ejb jar/project.
 
Jayashree Menon
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The EJBDeploy I am trying to do is not an ANT task, rather a commandline command.

However the .ear that I have created is made by the ANT tasks of jar and ear

The situation is this.
Previously, the project was built using a batch processing file as the expertise and know how of ANT was minimal at the time the project went live, which was around three and a half years back.

Now, with increase in enhancements and improvements which the client is requesting, it is getting cumbersome to build the project. So the migration to ANT.

We were able to create the .ear file of the project with ANT. Also the .jars and other class files in the ANT built .ear is the same as the ones created using the batch processing file. The only difference being the MANIFEST.MF files. The ones created by batch processing file has the classpaths and the ones created by ANT do not.

I also went through ejbdeploy task of ANT. It semed to be too complicated.
So decided to do a commandline ejbdeploy using the ejbdeploy.bat of the websphere appserver.

Now while doing this; I was getting the previously stated error.

If anyone can put some light on where I am going wrong, I would be thankful.

Thanks in advance.
Jayashree
 
drifter
Posts: 1364
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This could be a websphere question about whether there is a special directory within the ear where you put jars to make them available to an ejbjar...

or ...

It could be an ant question. You could specify the classpath for the ejb jar in the jar's manifest. You can specify a manifest file to use with the manifest attribute of the jar task. Or, the jar task can have a nested manifest element and the manifest element can have a nested attribute element.



Jar task documentation
 
Jeanne Boyarsky
author & internet detective
Posts: 40200
816
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jayashree,
WebSphere's command line ejbdeploy does use the manifest file. So you need to update the Ant build to include the manifest.

How did the batch system create the manifest?
 
Jayashree Menon
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Jeanne, Carol

I hadn't mentioned the Class-Path to be included in the MANIFEST.MF file.

I did that and got my work done.

Regards
Jayashree
 
Did you miss me? Did you miss this tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic