[Brian Bezanson]

What operating system and version are you running?
Windows 2000 Professional
What Eclipse version and build id are you using? (Help > About Eclipse Platform)
Eclipse Platform
Version: 2.1.3
Build id: 200403101828
– Was Eclipse freshly installed for MyEclipse?
Yes, though some other extensions were added first. To see about clearing the problem described below, I installed a clean copy of Eclipse and MyEclipse in new directories and encountered the same problem.
– If not, was it upgraded to its current version using the update manager?
No
– Are any other external plugins installed?
Yes
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*

What MyEclipse version are you using? (Help > About Eclipse Platform > Features)
2.7.1
What JDK version are you using to run Eclipse? (java -version)
1.4.2_04
What JDK version are you using to launch your application server?
Same
What steps did you take that resulted in the issue?
See below…
What application server are you using?
JBoss 3.2.4RC1

I am having a problem that goes as follows.

1) Create a new web module project (name ‘foo”), using default install directory.

2) Click “Finish” and project creates fine.

3) Click/Select the project and from the MyEclipse Window try and “Add Struts Capabilities”.

4) Dialog comes up. Leave all defaults set (struts 1.1, *.do, install check boxes set) and click on “Finish” — NOTHING HAPPENS. The dialog does not close and not files/changes are made to the project.

5) You can click on the “Finish” button as much as you want, but the dialog does not go away. You have to click “cancel” to leave.

6) A solution I previously found to fix this was to replace the entire JDK — but that takes a while and seems very weird. Why doesn’t this just work?

Does MyEclipse log problems anywhere?

Thanks in advance for the help,

Brian

[Riyad Kalla]

Brian,
I think there is something going on with your install, please post your log file here (<workspace>\.metadata\.log) I’m betting anything that clicking “Finish” is causing a pretty mean exception to be thrown. Please post your whole log file incase there are exceptions before that, that will help us figure out what is going on.

Your setup (JDK, Eclipse, MyEclipse, JBoss versions) all seem fine and shouldn’t be giving you any hassle, so you shouldn’t need to upgrade/change anything. We *might* need to reinstall Eclipse/MyEclipse though to rule out any weirdness.

[Brian Bezanson]

Riyad,

Your message led me to finding a solution/work-around for now.

In examining the log file, I see the following error throughout it for every time I tried to add struts to the project.

!ENTRY org.eclipse.ui 4 0 Apr 30, 2004 11:19:00.341
!MESSAGE org.jdom.input.SAXBuilder.setFactory(Lorg/jdom/input/JDOMFactory;)V
!STACK 0
java.lang.NoSuchMethodError: org.jdom.input.SAXBuilder.setFactory(Lorg/jdom/input/JDOMFactory;)V
at org.easystruts.jdom.JDomStruts.loadWebAppDocument(Unknown Source)
at com.genuitec.eclipse.org.easystruts.eclipse.wizards.NewEasyStrutsWizard.�(Unknown Source)
at com.genuitec.eclipse.org.easystruts.eclipse.wizards.NewEasyStrutsWizard.performFinish(Unknown Source)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at com.genuitec.eclipse.struts.action.AddStrutsCapabilitiesActionDelegate.basicRun(Unknown Source)
at com.genuitec.eclipse.struts.action.AddStrutsCapabilitiesActionDelegate.run(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingActionDelegate.runWithEvent(Unknown Source)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)

So as you can see there was a problem with a JDOM library. The way I have my system set up, I am using JBoss 3.2.4RC1 because it has Tomcat 5 built in for JSP debugging. Being new to JBoss I went through the JBoss 3.2.3 getting started documentation and ran through their examples. However I had problems with JBoss missing some libraries from 3.2.3. So I added the following libraries to the jdk/jre/lib/endorsed directory:

jdom.jar
resolver.jar
xercesImpl.jar
xml-apis.jar

So I had the JDOM jdom.jar file and three libraries from Xerces 2.6.2 (http://xml.apache.org/xerces2-j/index.html).

My CLASSPATH and JBOSS_CLASSPATH were set as follows below.

It appears (my assumption) that MyEclipse had some issues with the single jdom.jar file in one directory, but the other libraries located elsewhere or vise-versa. Removing the 4 files from the endorsed directory made MyEclipse very happy. I also added jdom.jar and resolver.jar to the CLASSPATHs and re-ran MyEclipse and everything seems fine. I need to run the JBoss samples to see if the new CLASSPATH options keep JBoss running OK too.

CLASSPATH
.;
%LOG4J_HOME%/dist/lib/log4j-1.2.8.jar;
C:\dev\jdom\lib\jaxen-core.jar;
C:\dev\jdom\lib\jaxen-jdom.jar;
C:\dev\jdom\lib\saxpath.jar;
C:\dev\xerces-2_6_2\xercesImpl.jar;
C:\dev\xerces-2_6_2\xml-apis.jar;
C:\dev\j2sdk1.4.2_04\jre\lib\endorsed\pg74.1jdbc3.jar

JBOSS_CLASSPATH
C:\dev\jdom\lib\jaxen-core.jar;
C:\dev\jdom\lib\jaxen-jdom.jar;
C:\dev\jdom\lib\saxpath.jar;

Thanks again for your help. If you think I should be doing this some other way, please let me know.

Thanks,

Brian

[Scott Anderson]

Brian,

Looks like you diagnosed this one perfectly. The JDOM API’s are still a moving target and get refactored quite a bit. Internally, we’re using an older version than the current one, which is what caused the break when you added the new one to the endorsed directory.

Glad you’re up and running, and thanks for posting the update for anyone else who may have done something similar.

[Author]

Posts