- This topic has 8 replies, 3 voices, and was last updated 14 years, 9 months ago by support-shalini.
-
AuthorPosts
-
larryfloodMemberThis message has not been recovered.
support-shaliniMemberThis message has not been recovered.
dongkunMemberI have this same issue with MyEclipse 8 when I try to reuse the workspace that was created by version 6.0.1. If I try on a new workspace, and create a new EAR project, EJB project, and Web project, I am able to see the EJB and Web modules in the New Application Module dialog. Is there a way to fix my 6.0.1 workspace to work with 8? I want to avoid having to setup Preferences, recreate projects, etc. if that can be avoided.
My install summary is as follows:
*** Date:
Wednesday, March 3, 2010 10:28:26 AM PST** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.0
Build id: 8.0-20091120*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 8.0
Build id: 8.0-20091120Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 8.x Latest\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Program Files\Genuitec\MyEclipse 8.x Latest\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Program Files/Genuitec/MyEclipse 8.x Latest
-data
C:\devtools\AccuRev\lightspeed\R10.1-Res-Rewrite-Int
-launcher
C:\Program Files\Genuitec\MyEclipse 8.x Latest\myeclipse.exe
-install
C:/Program Files/Genuitec/MyEclipse 8.x Latest
-vm
C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dllThanks!
dongkunMemberI found a work around for this. I renamed my EAR project, and just created a new EAR project with the same name, copying over existing files from the old project except for .mymetadata, .project, and application.xml. I was then able to see all of the modules to add to the deployment.
What is it about the old EAR project that is blocking the modules dialog from working properly?
support-shaliniMemberdongkun,
Thank you for the workaround.Can you clarify if the previous EAR project was developed using J2EE1.3/J2EE1.4?
when adding modules to an existing EAR project, the modules that can be added should have JDK compliance level that is compatible with that of the EAR project. For example, if the EAR project is created with J2EE5, modules created with J2EE1.3/J2EE1.4/ Java EE5 can be added.
Let me know if that helps.
dongkunMemberLooks like the previous EAR was set at J2EE 1.3, while the modules were at J2EE 1.4. That would explain it.
Is there a way to switch the EAR to a different spec from which it was created?
support-shaliniMemberdongkun,
You can try changing j2ee-spec to “1.4” for the EAR projects .mymetadata<enterprise-project
version=”1.0.0″
name=”EAR13″
id=”myeclipse.1268108732755″
j2ee-spec=”1.4″
archive=”EAR13.ear”>Let me know if that helps
dongkunMemberThanks Shalini. A colleague had pointed me to that file as well. However, just updating it didn’t work for me. I think I have to also update the DTDs being included in the application.xml. In any case, I did not try this as it is just simpler to create a new EAR project, and copy over the needed files. Then the .mymetadata and application.xml all have the correct settings. This issue is now closed for me. Thanks for all your responses as they helped me discover the issue and work around.
support-shaliniMemberdongkun,
Good to know that you are all set.
Do let us know if you have any issues. -
AuthorPosts