Bugzilla – Full Text Bug Listing
| Summary: | the web-service creation wizard hangs eclipse | ||
|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Dan Morrow <dmorrow> |
| Component: | jst.ws | Assignee: | Chris Brealey <cbrealey> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | thatnitind |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Dan Morrow
Dan, sorry you're having trouble here. I'm not familiar with the Mac platform, so please bear with me if I lapse into any Windows-isms. I haven't seen this behaviour on Windows - Which isn't to say it's unique to the Mac, but simply means I haven't encountered the problem myself - yet. Please start Eclipse with the -consoleLog and -debug options so that an Eclipse console (or Mac "terminal"?) window is left open. Re-try your scenario. When the platform hangs, ask the JRE for a core dump which will include stack traces for all threads in the JRE. On Windows, CTRL-Break from the console window will cause the core dump to happen. You can either copy & paste the relevant stack trace from the core dump file to a comment on this bug, or you can attach the core dump file in all its glory to this bug. That should help us get an idea of where the Eclipse platform is getting stuck. You can also inspect any "catalina" log files that Tomcat deposits to your workspace's .metadata\.plugins\org.eclipse.tomcat directory for unusual looking messages. Dan, am returning this for more information as requested in my previous remarks. Thanks - CB. Look, I'm new to Java. And very new to Eclipse. (I've been doing C++ for 12 years, though). So, my ignorance of this stuff is big. I can't do a ctrl-break on the Mac, because that doesn't work the way you'd expect. What I can tell you, is that this may have something to do with the fact that Eclipse, or the wizards that are generating the code, are having trouble finding the JRE on the Mac. If I do a "New > Other > Web > J2EE Web Project" (the beginning of the Bottom Up Web Service) and hit "Finish" it put the "JRE System Library" in my project, but "(unbound)" is at the end of the name. And it can't be opened. But if I do a right-click on this entry, and choose "Configure", I can choose "Workspace default JRE" and then it finds the JRE, and things look OK, I can open up the JRE, and it shows various jars, etc. If I go into the Eclipse prefernces, and choose "Java > Installed JREs" it find the JVM 1.4.2 just fine. So, I don't know why this is causing a problem for when projects get created. But it does. I can't be sure that this has to do with the crash, but my guess is that it has something to do with it. So, if you don't have access to a Mac, I'd urge that this bug be passed on to someone who does, and knows how to properly debug this problem. Or, maybe I could do this? If so, are there detailed instructions on how to debug Eclipse itself? Would I run & debug the 3.1 WTP project in Eclipse 3.0? I'm afraid to try this myself, due to my "brand-new-ness" to Java and Eclipse. But I'm running out of options here. I know this stuff is still in development, and I shouldn't be using this in a production environment, etc, etc. But I'm just trying to get a few things working, so I can prove that it can be done. -Dan. Dan, thanks for your reply. Off hand, I don't know of any Web service experts in the WTP community equipped with the Mac platform. I'll post a note to the wtp-dev@eclipse.org distribution list to see if anyone bites. I cannot presently provide a timeframe on the above, so if you are willing to try and help debug this problem, that may be the best course of action right now. There are a few articles about debugging available on the Eclipse Articles Web site [1]. I don't know if they cover aspects specific to Mac. The platform- debug-dev mailing list [2] may be able to help also. You should, by the way, run and debug the Eclipse 3.1 WTP project from an Eclipse 3.1 IDE. [1] http://www.eclipse.org/articles/index.html [2] mailto:platform-debug-dev@eclipse.org Lowering severity to "major" and raising priority to "P1" to insure critical and blocking severities are reserved for issues blocking delivery of WTP milestones (namely M4) per the project plan [1]. [1] http://www.eclipse.org/webtools/development/eclipse_WTP_project_plan_1_0.html Moving to P2 priority, because I believe our practice is to reserver "P1" to mean "won't release without". And, sadly, I don't think a Mac specific problem will currently qualify for that, simply due to our limited number of mac developers. I do think there is a Mac somewhere in the building, so will try to reproduce and track down eventually, if someone from community doesn't debug a provide a patch. Just so you know. I don't know if this is happening anymore, because I'm not trying to build the bottom- up-web-service anymore. Creating a skeleton java bean service is what I'm doing now. I'm pointing to a WSDL file that we use for our web services here, and this seems to work. Just mentioning it, because it's no longer a priority for me. -Dan. Ok ... given Dan's last comment, and knowing that many "browser bugs" have been fixed by the base Eclipse component, such as see Bug 100730, I'm going to be optimistic and assume this has been fixed by base Eclipse. If anyone has time/ability to check recent builds on MacOSX, please re-open if you still see. Thanks all. I'm not really sure if this works anymore, since the tutorial on the website is not for the M5 build of WTP. I can't follow the directions to the letter, because the docs don't match up with the environment. But I've built Web Services using the WTP, and they seem to work well, so I don't have any complaints. If you'd like me to verify this bug once the M5 docs go public, I'd be happy to do so. The bug about the bottom-up tutorial being out of sync with the release is 93117. Chris, assigning to you as you seemed to handle this bug. This bug was moved to 'closed' state, since it is so old is is assumed its dup, invalid, or worksforme resolution is no longer in qustion and the bugzilla needs no further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error in this case. |