STS 2.3.0 Bug - Create Axis SOAP Web Service

[jay.wagner]

I am having an issue creating an Axis SOAP web service from bottom-up. It used to work with STS 2.2.1. It seems it fails on the WSDL generation. Here is the failure. By the way, I do have the saaj.jar in the classpath at that location.

IWAB0506E Error when copying Axis jar files to web project
java.io.FileNotFoundException: /lib/saaj.jar
at org.eclipse.osgi.framework.internal.protocol.bundl eentry.Handler.findBundleEntry(Handler.java:44)
at org.eclipse.osgi.framework.internal.core.BundleRes ourceHandler.openConnection(BundleResourceHandler. java:175)
at java.net.URL.openConnection(URL.java:945)
at java.net.URL.openStream(URL.java:1009)
at org.eclipse.jst.ws.internal.axis.consumption.ui.ta sk.CopyAxisJarCommand.copyIFile(CopyAxisJarCommand .java:187)
at org.eclipse.jst.ws.internal.axis.consumption.ui.ta sk.CopyAxisJarCommand.copyAxisJarsToProject(CopyAx isJarCommand.java:156)
at org.eclipse.jst.ws.internal.axis.consumption.ui.ta sk.CopyAxisJarCommand.execute(CopyAxisJarCommand.j ava:109)
at org.eclipse.jst.ws.internal.axis.creation.ui.comma nd.BUCodeGenOperation$BottomUpWSModifyOperation.ex ecute(BUCodeGenOperation.java:108)
at org.eclipse.jst.ws.internal.axis.creation.ui.comma nd.BUCodeGenOperation.execute(BUCodeGenOperation.j ava:80)
at org.eclipse.wst.command.internal.env.core.fragment .CommandFragmentEngine.runCommand(CommandFragmentE ngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment .CommandFragmentEngine.visitTop(CommandFragmentEng ine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment .CommandFragmentEngine.moveForwardToNextStop(Comma ndFragmentEngine.java:254)
at org.eclipse.wst.command.internal.env.ui.widgets.Si mpleCommandEngineManager$6.run(SimpleCommandEngine Manager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurr entThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(Modal Context.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDi alog.java:944)
at org.eclipse.wst.command.internal.env.ui.widgets.Si mpleCommandEngineManager.runForwardToNextStop(Simp leCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.Wi zardPageManager.runForwardToNextStop(WizardPageMan ager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.Wi zardPageManager.getNextPage(WizardPageManager.java :154)
at org.eclipse.wst.command.internal.env.ui.widgets.Si mpleWizardPage.getNextPage(SimpleWizardPage.java:1 36)
at org.eclipse.jface.wizard.WizardDialog.nextPressed( WizardDialog.java:823)
at org.eclipse.jface.wizard.WizardDialog.buttonPresse d(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected( Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent( TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(Event Table.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.ja va:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents( Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Di splay.java:3473)
at org.eclipse.jface.window.Window.runEventLoop(Windo w.java:825)
at org.eclipse.jface.window.Window.open(Window.java:8 01)
at org.eclipse.wst.command.internal.env.ui.widgets.po pup.DynamicPopupWizard.run(DynamicPopupWizard.java :130)
at org.eclipse.ui.internal.PluginAction.runWithEvent( PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.ha ndleWidgetSelection(ActionContributionItem.java:58 4)
at org.eclipse.jface.action.ActionContributionItem.ac cess$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5. handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(Event Table.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.ja va:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents( Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Di splay.java:3473)
at org.eclipse.ui.internal.Workbench.runEventLoop(Wor kbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench. java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workben ch.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench. java:500)
at org.eclipse.core.databinding.observable.Realm.runW ithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWork bench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Pl atformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplica tion.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle. run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseA ppLauncher.runApplication(EclipseAppLauncher.java: 110)
at org.eclipse.core.runtime.internal.adaptor.EclipseA ppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru n(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru n(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework( Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.ja va:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:13 11)
at org.eclipse.equinox.launcher.Main.main(Main.java:1 287)

[Christian Dupuis]

Jay,

that seems to be a bug in WTP. STS ships two javax.xml.soap bundles in different versions and only the 1.2.0.v200905122109 has the saaj.xml to copy.

Can you try to delete the 1.3.0.v200904281458 and restart STS with the -clean flag.

Let me know if that helps.

Christian

[jay.wagner]

Jay,

that seems to be a bug in WTP. STS ships two javax.xml.soap bundles in different versions and only the 1.2.0.v200905122109 has the saaj.xml to copy.

Can you try to delete the 1.3.0.v200904281458 and restart STS with the -clean flag.

Let me know if that helps.

Christian

With the distribution I have, I only see the 1.2.0.v200905122109 for javax.xml.soap.

-Jay

[Christian Dupuis]

Jay,

my version of STS 2.3.0 has the following in the plugins directory:

javax.xml.soap_1.2.0.v200905122109
javax.xml.soap_1.3.0.v200904281458.jar

Is this different to what you see? Note the one bundle is a file the other is folder.

Christian

[jay.wagner]

Jay,

my version of STS 2.3.0 has the following in the plugins directory:

javax.xml.soap_1.2.0.v200905122109
javax.xml.soap_1.3.0.v200904281458.jar

Is this different to what you see? Note the one bundle is a file the other is folder.

Christian

Well I downloaded the latest distribution, which by the way is the same 2.3.0 but it did have that folder and jar file. I tried with them and it failed. So I removed both and it worked. So there is an issue with this in place. By removing them what will that affect.

-Jay

[Christian Dupuis]

Jay,

please delete only the javax.xml.soap_1.3.0.v200904281458.jar as some plugins need the javax.xml.soap bundle to be around.

You can also try to work-around this bug by manually adding the saaj.jar to your /WEB-INF/lib directory.

HTH

Christian

[frankp]

I just ran into exactly the same bug with 2.6.0 release. I've got both plugins mentioned (1.2.0 & 1.3.0). I'll try the workaround.

[dserodio]

Same problem with STS 2.7.0. Both javax.xml.soap_1.2.0.v201005080501 and javax.xml.soap_1.3.0.v201005080502 are folders, not JARs.

Filed https://issuetracker.springsource.com/browse/STS-2072

[fritzfs]

Same problem with 2.7.1 STS release. I've deleted javax.xml.soap_1.3.0 folder and left javax.xml.soap_1.2.0 folder. Restarted STS with -clean and now works. When can we expect fix for this?

[Martin Lippert]

Hi!

We analyzed this in more detail and it turns out that this is a bug in wtp while looking up the saaj.jar file. I have filed the corresponding bug with wtp.

-Martin