Hi,
I’m using MyEclipse Blue 9.1 edition now.
There is a problem when deploying my application, with following scenario:
EAR Project – TestEAR
EJB 2.1 Project – TestEJB
Application Client Project – TestAppClient
Web Project – TestWEB
Note that, all above projects are Case-Sensitive.
TestEAR has been configured/added with all above projects (TestEJB, TestAppClient and TestWEB), by following steps:
1. Right click the TestEAR project, and choose MyEclipse -> Add and Remove Modules.
2. Add all above module projects, and change the archive name, eg:
TestEJB.jar -> testejb.jar
TestAppClient.jar -> testappclient.jar
TestWEB.war -> testweb.war
Note that, application.xml is updated automatically in this case. Also, the same in .mymetadata file created for the TestEAR project. At this point of time, all module archives are in lowercase naming.
It is then successfully deployed (exploded mode using classic type) into WebSphere 6.1.
This is a happy flow.
However, whenever i restarted the MyEclipse, there will be a warning error in the deployed TestEAR.
By checking the application.xml and .mymetadata file, it is fine as everything as configured in earlier.
Anyhow, when I further check and verify the modules of TestEAR (by MyEclipse -> Add and Remove Modules), it shows that all archive names are automatically changed to follow the Module Project Name, excepted web module.
Eg. as configured in earlier time:
testejb.jar ->TestEJB.jar (changed automatically)
testappclient.jar -> TestAppClient.jar (changed automatically)
testweb.war -> testweb.war (remain unchanged)
This is causing the deployment failure and I need to always rename these archive names after each restart of MyEclipse.
Any idea if this is a known issue?
(Note: alternatively, I have to rename all module projects to lowercase, as exactly defined in the application.xml to avoid this restart issue)
Thanks.