- This topic has 26 replies, 3 voices, and was last updated 21 years ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version:
Eclipse version: 3.0M6
Eclipse build id: 200312182000
MyEclipse version: 3.7RC2
Eclipse JDK version: 1.4.2_01-b06
Application Server JDK version: N/A– Message Body ——————————-
How to Reproduce:
1. Create an EJB project.
2. Try to add a class by right clicking on the source folder and selecting New > EJB (session, entity and message).
3. Enter com.abc for the package and FooBean for the name.
4. Select the Entity EJB for the template to use and click finish. The bean will be created.
5. Now right click on the source folder again and select New > Class.
6. Enter com.abc for the package and BarBean for the name.
7. Click the “Add…” button to add the javax.ejb.EntityBean interface.
8. Marvel at the error dialog.
9. Click OK on the error dialog and Finish and the bean is successfully created.Nonetheless the bean creation process is greatly slowed the *&^# down by the fact that 1.) the ejb templates include stuff I don’t want and 2.) the normal class wizard is giving errors. NOTE: this happens when creating servlets also, maybe even jsp’s but I didn’t check.
Binyan
undefinedI’ve just tried these exact steps with Eclipse 2.1.2, ME 2.7RC2 on Linux and everything worked fine without any error messages. We do appreciate the detailed error report and I’ll forward it off to Scott to take a look at so we can get this fixed up.
Keep in mind that the Eclipse M series and the MyEclipse 3.x series are provided as a preview. If you need something stable that is going to run without bugs and hickups, it is recommended to go with the stable release of both instead of the development branches.
Binyan,
I ran through all your steps on 3.7RC2 on a Mac and it worked perfectly all the way through. No errors, no dialogs.
Did you follow the full installation instructions for 3.7 RC2 related to deleting the .config directory? Are there errors shown in the log file?
There is nothing in the log. I have done this procedure on a Windows 2000 box and a Windows XP box with Eclipse 3.0M6, java 1.4.2_X and ME 3.7RC2 and it is 100% reproducible. The error dialog title is “Select Type” and the text of the dialog is “Could not uniquely map the type name to a type. Path is /C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.6.200\data”. There may be more to the text but it runs off the right side of the dialog and the dialog is NOT resizable.
I have Eclipse/MyEclipse installed to:
C:\Java\Eclipse
C:\Java\MyEclipsenote: no spaces in the directories…
Scott did you have any spaces in your install directories?
Here is an url to a viewlet that will let you all watch the complete steps to create this bug.
http://mysite.directlink.net/wbeckwith/viewlets/mebug.swf
Unfortunately I don’t have my licensed version on this computer so you will have a watermark in the middle of the viewlet. Nonetheless, you can see the steps performed.
The viewlet will show a new install of eclipse and ME and the steps to get the error.
Following is the contents of the log from eclipse after getting the error:
!SESSION Jan 16, 2004 10:17:27.859 ———————————————
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.ui 4 4 Jan 16, 2004 10:17:27.859
!MESSAGE Unable to find view label: org.eclipse.debug.ui.ConsoleViewHope this helps.
Wow, this is the best bug report ever.
binyan, try this:
1) uninstall MyEclipse (yes again)
2) remove the eclipse dir (yes again)
3) reunzip eclipse to the bug dir
4) RUN eclipse, close eclipse
5) Install MyEclipse
6) Run eclipse, try to create the bug againDoes this work? If not, what happens when you erase the .config dir and restart Eclipse (with MyEclipse installed?)
@support-rkalla wrote:
Wow, this is the best bug report ever.
binyan, try this:
1) uninstall MyEclipse (yes again)
2) remove the eclipse dir (yes again)
3) reunzip eclipse to the bug dir
4) RUN eclipse, close eclipse
5) Install MyEclipse
6) Run eclipse, try to create the bug againDoes this work? If not, what happens when you erase the .config dir and restart Eclipse (with MyEclipse installed?)
1. Done.
2. Done.
3. Done.
4. Done.
5. Done.
6. Done.No, it doesn’t work. ME does not show up in the preferences, so I have to shut eclipse down and delete the .config dir, then ME shows up in eclipse by having its welcome page displayed.
Next I re-tried creating the project and it errored as previously described. I then removed the 1.3 Container from the projects’s Java Build Path on the Libraries tab. I then added the j2ee.jar that is in websphere and tried to create a class that implements the EntityBean interface and it worked correctly.
Finally I then removed the websphere j2ee.jar and added all the jars from the ME 1.3 Library container as EXTERNAL jars. I then re-tried (again) creating an entity bean class and it all worked. So for the moment I have a workaround and hopefully I have provided you all enough info to hunt this issue down and kill it with extreme prejudice. 🙂
You attention to detail and help in this matter is appreciated immensly. I’m sure we shouldn’t have a problem killing this off 😉
Finally I then removed the websphere j2ee.jar and added all the jars from the ME 1.3 Library container as EXTERNAL jars.
The issue was most likely adding the websphere j2ee.jar to the project since this would have created multiple versions of many classes. This problem was never reproducable internally, so I’m marking this closed.
This #$#$ bug is apparently back in 3.0M8 (atleast for me). I have done a complete uninstall/reinstall of eclipse 3.0M8 and then ME 2.7.2. And I once again have the issue of trying to create an ejb and getting the dialog that displays the error “Could not uniquely map the type name to a type. Path is /C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.7.2\data\lib” is all I can see but it must be referring to librararyset\1.3\jboss-j2ee.jar.
I also ge the problem with trying to create a servlet, only then the fjar that is reffered to in the selection dialog is javax.sevlet.jar. This same computer wirh Windows XP, java sdk 1.4.2_04, eclipse 3.0M7 and ME 3.7.0 did not produce this problem so I thought it was fixed.
I should note that in both cases the base class and interface selection dialog only has one entry in the Qualifier section which points to the ME jar files.
@scott wrote:
Finally I then removed the websphere j2ee.jar and added all the jars from the ME 1.3 Library container as EXTERNAL jars.
The issue was most likely adding the websphere j2ee.jar to the project since this would have created multiple versions of many classes. This problem was never reproducable internally, so I’m marking this closed.
The above is a mistake in your understanding of the issue. I never had the websphere j2ee.jar added to the project while the ME J2EE 1.3 library container was added. I just wanted to verify that it does work and there seemed to be something weird happening in relation only to the ME library container. Therefore I removed the ME library container and added the j2ee.jar and then tried to create classes and it all worked fine. Never was there 2 j2ee.jar files added to the project, but even if there had been I would have had to select the correct one in the selection dialog.
