For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 3 voices, and was last updated 13 years, 9 months ago by
.
-
Posts
-
When creating EAR file from enterprise project, the EAR file fail to pass the ejbdeploy enrichment require for WebSphere.
Ejbdeploy result with hundreds of errors.I tested the same project in MyEclipse 8.6/9/10 all result with same errors (attached).
In earlier versions of MyEclipse same projects deploys perfectly and pass the ejbdeploy process with no errors (also attached), and get installed correctly on WebSphere.
This prevents us from upgrading MyEclipse to a version newer than MyEclipse 8.5.ronenmalka,
Sorry to hear you are running into this issue. Please refer ejbdeploy with MyEclipse 10.txt. It looks like there are compilation issues listed. Could you please check if all the relevant resources are placed correct? It also lists build-path issues. Please verify project builld-path.
Could you attach a sample project to help me reproduce this issue at my end? In case you cannot attach here, please send a mail to support@genuitec.com with sample project as attachment. Include above weblink for quick tracing and add ATTN:Joy in the subject.
Ronen,
Just to confirm your exact use case, you are not deploying your application directly with MyEclipse, but instead exporting an EAR (from MyEclipse) and then deploying that manually using the command line. The EAR created from 8.5 works but that created from subsequent versions does not.. Is this an accurate understanding of your problem?
If you deploy your application using MyEclipse deployment, does that work or do you never use the inbuilt deployment with versions > 8.5?
Brian,
Your understanding is correct.
I do not deploy using MyEclipse. I only generate the EAR file, then run ejbdeploy batch and then install it on WAS using WAS console.I fail on the second stage, running the ejbdepoly on the EAR.
Ronen,
I’m afraid this problem is not easy to track down remotely. To help narrow down the problem, can you help us find obvious differences between the two EARs exported?
a) I assume the file sizes are different.
b) If you expand each of the EARs (8.5 and greater) into separate folders do you find that the size of the EJB jars within are different? Are there other differences?
c) If yes, can you further expand the EJB jars and find which particular folders are missing or different in the two versions.Instead of a manual investigation, you could alternatively unzip each EAR and subsequently unzip all JARs and WARs within that EAR into their respective folders. You can these use a diff tool like CSDiff to compare the two directories and generate a report that will help us take this further. Please ensure you unzip the component WAR and JAR files into the same locations within each EAR to get an accurate diff report.
