[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6481) [Web Service Wizard] Issues creating web service project for simple WSDL
Brian Fitzpatrick (JIRA)
jira-events at lists.jboss.org
Thu Jul 29 09:55:33 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12541856#action_12541856 ]
Brian Fitzpatrick commented on JBIDE-6481:
------------------------------------------
I'm unfamiliar with the JAXB APis myself. But will your method actually work? The issue is for top-down (from WSDL) not bottom-up (from classes) so "I think we can read all the generated java files, find out the web service interface classes, then generate impl class for every web service interface class." doesn't sound like a workable solution either.
If we go with the JAXB solution, the WTP wizard right now doesn't have a way to provide bindings files. We'd have to add one and it sounds like this is more of an issue with tooling than the underlying runtime which is doing the heavy lifting to generate the code from the WSDL. Whether we change the incoming names as with Lukas' original patch or we go with the JAXB solution, we're not directly supporting what the user would see if they do the same thing at the command line.
As such, what's the real reason the code is failing in this case on our side? The solutions we have so far are simply band-aids over whatever the underlying problem is.
> [Web Service Wizard] Issues creating web service project for simple WSDL
> ------------------------------------------------------------------------
>
> Key: JBIDE-6481
> URL: https://jira.jboss.org/browse/JBIDE-6481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.2.x
> Reporter: Brian Fitzpatrick
> Assignee: Feng Qian
> Priority: Critical
> Fix For: 3.2.x
>
> Attachments: BibleWebservice.asmx.wsdl, JBIDE-6481.txt
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Ran into an issue while doing some testing. The simple WSDL at http://www.ecubicle.net/gsearch_rss.asmx?WSDL, which can be used and tested to convert a simple Google search into an RSS feed, is causing issues when I try to create a new Web Service out of it. I've tried with the WSDL at the url and with a locally saved version and get the same response.
> Any ideas? This particular issue also showed up with my new WS wizard that I'm working on. The error in this case is generated from the existing WTP Web Service wizard available in the New wizards under the Web Services category.
> I've also noticed that though a new project is created, it's lacking the JRE library entry in its path and you have to go in and add it to the classpath manually. I don't think these issues are related however.
> Here's the console output with the exception:
> Retrieving document at 'file:/NotBackedUp/bfitzpat/eclipse3.6m7b/runtime-New_configuration_May25/WSDLProj/gsearch_rss.wsdl'.
> Gsearch_rssSoap
> !ENTRY org.jboss.tools.ws.creation.core 4 0 2010-06-16 16:24:13.838
> !MESSAGE Failed to Generate Web Service code, please check the log for more details
> !STACK 1
> org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details
> at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:450)
> at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133)
> at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:97)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:887)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508)
> at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2839)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734)
> at org.eclipse.swt.widgets.Tree.gtk_key_press_event(Tree.java:1977)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4794)
> at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3485)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4372)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8163)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2224)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
> !SUBENTRY 1 id 4 0 2010-06-16 16:24:13.841
> !MESSAGE Failed to Generate Web Service code, please check the log for more details
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list