For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 4 voices, and was last updated 21 years, 5 months ago by
Riyad Kalla.
-
AuthorPosts
-
Chris FriedlMemberEnvironment:
JDK 1.4.2
Eclipse 3.0
myEclipse 3.7.101I just downloaded Eclipse 3.0 and installed the latest myEclipse plugin. I then attempted to run through the Struts tutorial. I went half way throught the tutorial (up to where the LoginAction.java is complete but before the success.jsp is to be built), saved everything, exited and tried to come back in.
Upon reentering Eclcipse I received the following error message: Problems occurred restoring workbench. – Unable to restore perspective Workspace – MyEcipse. Unable to create editor LoginAction.java.
When I click OK Eclipse comes up but there is no structure under the StrutsDemo project in the Package Explorer.
Is this product compatible with 3.0? Is there a solution expected soon?
June 28, 2004 at 1:06 pm #209145
Riyad KallaMemberActually yes MyEclipse is compatible with Eclipse 3.0 but you need to download/use the 3.8 Beta 1 Manual Install. Detailed instructions are included with it to walk you through the install step-by-step.
The version you are using now actually requires Eclipse 3.0M8. And part of the problem for us is that Eclipse has been versioned “3.0.0” since the first development release of it, so our installer can’t tell the difference between M1 and final release.
June 28, 2004 at 2:51 pm #209149
Riyad KallaMemberReopening:
Oops, Scott has correctly pointed out that I jumped the gun too quickly here. You are currenlty using the correct version (3.7.101 == 3.8Beta1) and the installer DOES support Eclipse 3.0, again my fault (I got my wires crossed along the way).When you downloaded Eclipse 3 and MyEclipse, was it a fresh install with a clean workspace? Or were you reusing a new workspace? Was this workspace from Eclipse 2 or a previous Eclipse 3 install?
June 28, 2004 at 3:51 pm #209153
Chris FriedlMemberThis was a clean everything. Fresh Eclipse 3.0 new workspace, Fresh install of ME and no other plug-ins.
I think that part of the problem has already been described in another bug report. It seems that I left the struts-config.xml open when I left the workspace and re-started ME it would crash the package view. after closing the struts-config.xml, exiting and re-entering it opens the package view.
However, I have noticed another problem. I was going though the demo tutorian and when I tried to run the deployed application it failed. I tracked the problem down to the auto-generated JSP. What I noticed was that entering all of the data on the wizard forms would generate the JSP but (as the code snippet below shows) ME fails to substitute for the [ACTION_PATH] variables in a template.
<html:form action=”/[ACTION_PATH]”>
name : <html:text property=”name”/><html:errors property=”name”/></br>
<html:submit/><html:cancel/>
</html:form>My hope is that this can be easilly fixed by modifying a text template somewhere. Any ideas?
Thanks,
ChrisJune 28, 2004 at 4:16 pm #209155
Riyad KallaMemberChris,
Thank you for both of thsoe detailed reports, I wasn’t aware of the struts-config staying open crashing the package explorer, I’ll send that along. Also I know that we know about the ACTION_PATH bug, and think its fixed in Beta 2, but I’ll double check for sanity sake.June 28, 2004 at 6:30 pm #209167
Scott AndersonParticipantBoth these are known bugs in Beta 1 and have already been fixed internally for Beta 2. Thanks for reporting them.
June 29, 2004 at 3:21 pm #209198
sblewisMember@support-rkalla wrote:
Chris,
Thank you for both of thsoe detailed reports, I wasn’t aware of the struts-config staying open crashing the package explorer, I’ll send that along. Also I know that we know about the ACTION_PATH bug, and think its fixed in Beta 2, but I’ll double check for sanity sake.What is the fix for this with Beta 1?
Thanksinadvance,
Scott
June 29, 2004 at 3:24 pm #209199
Riyad KallaMemberScott,
There isn’t one, if you check the reply right above yours our Scott said “These are known bugs against Beta 1 and are fixed in Beta 2”, so when Beta 2 comes out it will be fixed. -
AuthorPosts
