[Donald R. Kichline]

We have an ear that contains an ejb module. The ejb module relies on a jar for some of the ejb’s interfaces. Building the code works just fine because we can setup the classpath.

However when I deploy the ear to the server via the MyEclipseBlue interface (Servers Tab, WebSphere 6.0, Add Deployment), I receive the following error in the deployment log:

ADMA5008E: EJBDeploy failed on C:\Program Files\IBM\SDP70\runtimes\base_v6/profiles/default\wstemp\wstemp\app_119e81fa169\dpl\dpl_Rentalnet.ear: com.ibm.websphere.management.exception.AdminException: ADMA0063E: An error occurred in EJB deployment - [ejbModule/com/penske/apps/rentalnet/ejb/EJSRemoteStatelessCommandServer_229a5ca8.java(8): CommandServer cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSRemoteStatelessCommandServerHome_229a5ca8.java(8): com.penske.apps.rentalnet.ejb.CommandServerHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessVehiclePricing_0a8e729b.java(9): com.penske.apps.rentalnet.ejb.VehiclePricingLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessVehiclePricingHome_0a8e729b.java(9): com.penske.apps.rentalnet.ejb.VehiclePricingLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessRate_4434b0f6.java(9): com.penske.apps.rentalnet.ejb.RateLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessRateHome_4434b0f6.java(9): com.penske.apps.rentalnet.ejb.RateLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessQuote_6419e5e8.java(9): com.penske.apps.rentalnet.ejb.QuoteLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessQuoteHome_6419e5e8.java(9): com.penske.apps.rentalnet.ejb.QuoteLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessPreference_87de3019.java(9): com.penske.apps.rentalnet.ejb.PreferenceLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessPreferenceHome_87de3019.java(9): com.penske.apps.rentalnet.ejb.PreferenceLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessLocation_bf67d8da.java(9): com.penske.apps.rentalnet.ejb.LocationLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessLocationHome_bf67d8da.java(9): com.penske.apps.rentalnet.ejb.LocationLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessInsurances_7139779c.java(9): com.penske.apps.rentalnet.ejb.InsurancesLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessInsurancesHome_7139779c.java(9): com.penske.apps.rentalnet.ejb.InsurancesLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessCustomer_c7230384.java(9): com.penske.apps.rentalnet.ejb.CustomerLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessCustomerHome_c7230384.java(9): com.penske.apps.rentalnet.ejb.CustomerLocalHome cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessCommandServer_229a5ca8.java(9): com.penske.apps.rentalnet.ejb.CommandServerLocal cannot be resolved or is not a valid superinterface, ejbModule/com/penske/apps/rentalnet/ejb/EJSLocalStatelessCommandServerHome_229a5ca8.java(9): com.penske.apps.rentalnet.ejb.CommandServerLocalHome cannot be resolved or is not a valid superinterface]

Talking to our system admins, when they deploy this code to production, they have to set an optional ejb classpath in order for the deployment to work in our production environment.

To set the classpath in the admin console you do the following steps:
1. Install New Application
2. Select the ear file
3. Next
4. Next
5. Next
6. Next
7. Set the “Deploy EJB Option – classpath” value.

I do not see a similar option in the MyEclipseBlue interface. Is there a way to do this so that I can deploy through your interface?

Thanks,

Don

[Loyal Water]

Don,
You should use a Dependent Java Project where your jar would be placed and set the appropriate deployment policy. You can refer to this doc to get an explanation of how to go about doing this:-
http://www.myeclipseide.com/documentation/quickstarts/earprojects/#advanced_features

[Donald R. Kichline]

That did the trick, thanks!

[Loyal Water]

Your Welcome

[Author]

Posts