Comment 1 Tim deBoer 2006-01-31 17:05:16 EST

The error in the stack trace does not match the current code and several fixes have gone into this class since 1.0. Have you been able or tried to reproduce this on a recent 1.0.1 build?

Comment 2 Simon Wiehe 2006-01-31 18:44:00 EST

I have used whatever is available from the Update site. Eclipse is telling me that everything is up to date. Have these fixes been published on the update site or should I download a build manually?

Comment 3 Simon Wiehe 2006-01-31 19:07:27 EST

I hav just downloaded the latest 1.5M4 build and it still does it. The stack trace this time is below. I have not checked to see if this is the same.

IWAB0234E An internal error occurred. Details: null
    java.lang.IllegalStateException
    at org.eclipse.jst.server.core.internal.RuntimeBridge$Stub.getRuntimeComponents(RuntimeBridge.java:165)
    at org.eclipse.wst.common.project.facet.core.runtime.internal.BridgedRuntime.supports(BridgedRuntime.java:68)
    at org.eclipse.wst.common.project.facet.core.runtime.internal.RuntimeManagerImpl.getRuntimes(RuntimeManagerImpl.java:149)
    at org.eclipse.wst.common.project.facet.core.runtime.RuntimeManager.getRuntimes(RuntimeManager.java:98)
    at org.eclipse.jst.ws.internal.consumption.common.FacetUtils.getRuntimes(FacetUtils.java:501)
    at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.getServerTypeFromFacets(ClientRuntimeSelectionWidgetDefaultingCommand.java:538)
    at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.getServerTypeFromProject(ClientRuntimeSelectionWidgetDefaultingCommand.java:527)
    at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.setClientDefaultServer(ClientRuntimeSelectionWidgetDefaultingCommand.java:302)
    at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.execute(ClientRuntimeSelectionWidgetDefaultingCommand.java:208)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:386)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:327)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:226)
    at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:247)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:346)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:291)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
    at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:217)
    at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:78)
    at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:124)
    at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:119)
    at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:747)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:345)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
    at org.eclipse.jface.window.Window.open(Window.java:787)
    at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:181)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
    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:589)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
    at org.eclipse.core.launcher.Main.run(Main.java:973)
    at org.eclipse.core.launcher.Main.main(Main.java:948)

Update manager is still showing as version 1.0.0.

Comment 4 Tim deBoer 2006-01-31 21:14:56 EST

Hi Konstantin,
The only thing on line 165 where the IllegalStateException is being thrown is:
   RuntimeManager.getRuntimeComponentType("standard.jre").getVersion("5.0");
The exception obviously isn't thrown directly on that line, so my next guess is that the top of the stack trace is missing for some reason. I looked into the RuntimeManager a little and do not see any obvious problems, but there is a lot of set manipulation and since it only occurs in the web services case I'm wondering if there is some sort of concurrency issue here.

Do you have any ideas here on why the IllegalStateException is being thrown, or traces we could do to ensure that the web service code is not interfering?

Comment 5 Konstantin Komissarchik 2006-01-31 23:14:53 EST

Hmm. This is rather puzzling. I don't see any place where an IllegalArgumentException could get thrown from the code that's called on that line. I don't think it's a concurrency issue. The runtime component types are initialized the first time RuntimeManager is accessed and the list is never modified again.

Simon, could you document the exact steps that you are using to reproduce the problem (including the url of the webservice you are trying to connect to). We'll try to reproduce it and see if we can get more insight into the failure.

Comment 6 Simon Wiehe 2006-02-01 04:54:17 EST

Ah, one thing to maybe consider here, I am using the Early Access Java 6 jdk and also the jre to run eclipse. I have repointed back to my Java 5 runtime to start eclipse but still get the same problem. I will reinstall Eclipse 3.1.2 and the plug-ins along with Java 5 jdk to see if it works and then run with Java 6 and see if that works.

I will report back the findings to here later today.

Comment 7 Simon Wiehe 2006-02-01 07:49:12 EST

OK, new install of Eclipse 3.1.2 with all the standard features inslalled from update manager, followed by 15M4 and dependent GEF, JEM and works, sort of.

I did get this exception

IWAB0014E Unexpected exception occured.
  
      java.lang.NoClassDefFoundError
      at org.eclipse.wst.common.internal.emfworkbench.EMFWorkbenchContext.createURIConverter(EMFWorkbenchContext.java:376)
      at org.eclipse.jem.util.emf.workbench.EMFWorkbenchContextBase.initializeResourceSet(EMFWorkbenchContextBase.java:114)
      at org.eclipse.wst.common.internal.emfworkbench.EMFWorkbenchContext.initializeResourceSet(EMFWorkbenchContext.java:76)
      at org.eclipse.jem.util.emf.workbench.EMFWorkbenchContextBase.getResourceSet(EMFWorkbenchContextBase.java:89)
      at org.eclipse.jem.internal.plugin.JavaEMFNature.primaryContributeToContext(JavaEMFNature.java:137)
      at org.eclipse.jem.internal.util.emf.workbench.EMFWorkbenchContextFactory.initializeEMFContextFromContributors(EMFWorkbenchContextFactory.java:127)
      at org.eclipse.jem.internal.util.emf.workbench.EMFWorkbenchContextFactory.createEMFContext(EMFWorkbenchContextFactory.java:110)
      at org.eclipse.jem.util.emf.workbench.WorkbenchResourceHelperBase.createEMFContext(WorkbenchResourceHelperBase.java:249)
      at org.eclipse.jem.util.emf.workbench.nature.EMFNature.createEmfContext(EMFNature.java:105)
      at org.eclipse.jem.util.emf.workbench.nature.EMFNature.getEmfContextBase(EMFNature.java:229)
      at org.eclipse.jem.util.emf.workbench.nature.EMFNature.getResourceSet(EMFNature.java:184)
      at org.eclipse.jst.ws.internal.common.JavaMOFUtils.getJavaClass(JavaMOFUtils.java:212)
      at org.eclipse.jst.ws.internal.axis.consumption.ui.task.Stub2BeanInfo.writeSEIMethods(Stub2BeanInfo.java:474)
      at org.eclipse.jst.ws.internal.axis.consumption.ui.task.Stub2BeanInfo.writeClass(Stub2BeanInfo.java:254)
      at org.eclipse.jst.ws.internal.axis.consumption.ui.task.Stub2BeanInfo.write(Stub2BeanInfo.java:158)
      at org.eclipse.jst.ws.internal.axis.consumption.ui.task.Stub2BeanCommand.execute(Stub2BeanCommand.java:163)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:386)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:327)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:226)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:247)
      at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:346)
      at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:291)
      at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:217)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:78)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:227)
      at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:335)
      at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
      at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
      at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
      at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
      at org.eclipse.jface.window.Window.open(Window.java:787)
      at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:181)
      at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
      at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
      at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
      at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
      at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
      at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
      at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
      at org.eclipse.core.launcher.Main.run(Main.java:973)
      at org.eclipse.core.launcher.Main.main(Main.java:948)

When doing the Generate Proxy section. I cannot finish the wizard but I do get some java classes.

Comment 8 Simon Wiehe 2006-02-01 07:50:56 EST

On checking the java classes some are missing.

Comment 9 Simon Wiehe 2006-02-01 08:13:28 EST

In summary, as there is a lot of information on here.

I installed Eclipse 3.1.2
I then installed Web Tools 1.5M4 from the zip
Next I installed emf-sdo-xsd-SDK-2.2.0M4 from the zip followed by GEF-SDK-3.2M4.zip and JEM-SDK-1.2M1.zip

Next I ran the update manager to install new features from the eclipse update site, I selected all features.

I then created a new Java project and added a new server through the windows -> preferences -> server -> Installed runtimes. I selected the install dir of my Tomcat 5.5 server and let eclipse search for the runtime.

I then added a new proxy (I let eclipse select the default proxy type) and entered the URL http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

I kept clicking next and when it tried to generate the proxy classes I got the last exception listed above. Some classes generated but others did not. It seems the ones that did not generate had limited nodes under the method name, for example HelpResponse did not generate.

I also tried this with Java 6 and it does not work.

Comment 10 Konstantin Komissarchik 2006-02-01 09:15:04 EST

I notice you are using Eclipse 3.1.2 with a WTP 1.5 build. WTP 1.5 requires Eclipse 3.2M4. You can find all of the correct pre-reqst at this URL:

http://download.eclipse.org/webtools/downloads/drops/S-1.5M4-200601131852/

Comment 11 Simon Wiehe 2006-02-01 11:44:00 EST

Thanks,

I now get it to work generating the proxy but I still have compile time errors, some of the WSDL seems to be ignored. The Help element does not seem to be converted into a class.

Would this likely be a plug-in problem or something wrong with the WSDL?

Comment 12 Tim deBoer 2006-02-06 17:36:01 EST

Transferring to web service team for further problem determination since I can't help with determining if the WSDL is correct. Please feel free to transfer back if there are still any server tools issues.

Comment 13 Chris Brealey 2006-02-09 17:05:39 EST

Kathy,
would you please try running the WSDL from comment 9 thru WTP and the native Axis 1.2.1 WSDL2Java emitter?

Simon,
if the Java code generated by the wizard fails to compile, then the problem may be with the WSDL or with the Apache Axis emitters. We'll try to determine which. If it turns out to be Axis, then the next step will be to crack open a bug against Apache Axis.

Comment 14 Kathy Chan 2006-02-09 23:39:56 EST

Hi Simon,

I was able to reproduce the compile error with generated code when creating Web service client with the URL:

http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

I trie today's WTP 1.5 integration build v2006I02090643.

I got the same compilation error when trying Axis 1.2.1 in a command line environment (i.e. not using WTP).  This is the level of Axis code shipped in WTP 1.0 and still in WTP 1.5.  I was just about to open an Axis bug when I decided to try Axis 1.3 first.

I found that the problem is no longer there in Axis 1.3.  The missing classes that were not generated when using Axis 1.2.1 are now generated using Axis 1.3.

We already has a defect (bug 116308) opened for upgrading Axis from 1.2.1 to 1.3 in WTP 1.5.  

In the meanwhile, you could download Axis 1.3 and replace the JARs in plugins\org.apache.axis_1.2.1.vxxxxx\lib with the ones from the lib directory of Axis 1.3.

The JARs you should backup and replace are:

axis-ant.jar
axis.jar
commons-discovery-0.2.jar
commons-logging-1.0.4.jar
jaxrpc.jar
log4j-1.2.8.jar
saaj.jar
wsdl4j-1.5.1.jar

Note that you do not need to replace javaxzombie.jar as it's a dummy JAR we created to workaround another Axis problem and is not in Axis 1.3 lib.  This JAR only starts to show up in this week's build.

After replacing the Axis JARs, restart the workbench with:

eclipse -clean

If you found that the problem is not solved by moving to Axis 1.3, please re-open the defect.





*** This bug has been marked as a duplicate of 116308 ***

Comment 15 Kathy Chan 2006-06-15 11:08:51 EDT

As we are trying to close down WTP 1.5, please get the latest WTP 1.5 driver to verify the bug and reopen if the problem had not been fixed.  If this defect is not verified/reopened by end of day 06/16, I'll attempt to verify the defect by reproducing the problem as described in the defect.  However, since you know your scenario best, it would be more appropriate if you verify the fix.

Comment 16 John Lanuti 2006-11-28 15:50:00 EST

This is part of a mass update to close out all stale WTP bugs which are in the resolved state without an appropriate targeted version.  If you feel this bug was closed inappropriately, please reopen.