- This topic has 9 replies, 2 voices, and was last updated 16 years, 6 months ago by Loyal Water.
-
AuthorPosts
-
oddridgeMemberHi all,
I’m currently evaluating MyEclipse Blue as an alternative to RAD 6. The target server is WAS 5.1 and we have our workspace up and running in RAD 6 with it’s included runtime.
Now I’m trying to do the same with MyEclipse Blue.
The original EAR wasn’t strictly correct in that it contained non-EJB jars as libraries, referenced via the Manifests in the EJB jars. We have fixed this for RAD 6 by adding the bin dirs of the “library” projects as ws.ext.dirs in the 5.1 runtime.
Now I can’t deploy the EAR to a full WAS5.1 installation using the WebSphere 5.x connector.
Here’s the error:
IWAE0002E Could not reflect methods for com.kainos.hibppp.ejb.bps.BPSDataProviderLocal because one of the methods references a type that could not be loaded. Exception: java.lang.NoClassDefFoundError: com/kainos/hibppp/commonEx/BPSRetrieveDataException
How can I add the “library” commonEx project classes to the path used for deployment?
cheers,
doddy
Loyal WaterMemberDoddy,
You can have a dependent java project with you your library and add this project as a dependency. Now you can go to Project > Properties > MyEclipse > EAR and check the option that says “JAR exported from dependent java project”.You can refer to this doc for help:-
http://www.myeclipseide.com/documentation/quickstarts/earprojects/
oddridgeMemberWell the whole workspace builds okay, so all of the libraries and projects are referenced properly in the workspace.
It’s at deployment stage that I have the problem – how can I inform the deployment step that it should use the classes from the “library” projects during deployment?
Loyal WaterMemberCan you look at my edited post above. I guess that should resolve the issue for you.
oddridgeMemberYes that’s a big help thanks Nipun.
Next problem – I have three EJB jars in the EAR which contain just imported classes.
These are effectively “black box” to us, but in order to deploy them from RAD I set up projects for them and imported the classes from EJB jars.When I deploy from MyEclipse none of the imported classes are copied to the WAS installedApps folder, leading to deployment exceptions.
The imported classes have been “Exported” in the build path for access by other projects but I don’t this relates to deployment.
Is there an option somewhere to include these classes in the deployment?
cheers,
dod
oddridgeMemberGot it – the EJB Option under MyEclipse in project properties did the trick.
I think this is badly worded though:
Classes directly contained in an output directory of a dependent Java
project will be added to both exploded or archived deploymentsI’m not concerned with a dependent Java project at all, but an imported classes folder…
anyway onwards and upwards :>
oddridgeMemberSorry I guess this should be in MyEclipse Blue section – please someone move it there?
dod
Loyal WaterMemberMoving to MyEclipse Forum Index » MyEclipse Blue IDE » General
oddridgeMemberThe problem I have now is that even though the whole workspace builds correctly i.e. all third party jars etc. are referenced properly, I still get deployment exceptions because of missing classes.
Do I need to configure the class path for WAS deployment separately from the projects in MyEclipse?
I’ve tried adding ws.ext.dirs to the server and also adding dirs to the Paths screen in the config of the WAS5.x connector, but still get:
The project was not built since its classpath is incomplete. Cannot find the class file for com.kainos.utils.CCollection.
This all builds fine in MyEclipse. That CCollection class is in a little helper library which is referenced as an external jar in the workspace.
Any thoughts?
-
AuthorPosts