[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-14358:
-------------------------------------------
This looks like a duplicate of (or related to) JBIDE-14339.
Can you try this workaround: https://issues.jboss.org/browse/JBIDE-14339?focusedCommentId=12771195&pag...
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> 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:1028)
> 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:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBIDE-14339) The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14339?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-14339:
-------------------------------------------
Is the project you're creating the WS client in a Dynamic Web Project? If so, is the JBoss Web Services Core facet enabled in the Project Facets for the project? To check, right-click on the Properties and select Project Facets, select JBoss Web Services Core in the list.
The issue appears to be the fact that the Preference default isn't being picked up. The workaround is to select the JBoss Web Services Core facet, look to the right in the tabs - Details & Runtimes, and select your runtime in the Runtimes list.
Definitely a weird issue. But that seems to be the workaround. We'll see if we can find a way to fix that however, probably by finding the workbench default (set in the preferences).
> The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-14339
> URL: https://issues.jboss.org/browse/JBIDE-14339
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Fix For: 4.1.0.Beta1
>
> Attachments: JBDS_WS_Error.png, JBDS_WS_Error_config.png
>
>
> Using the Web Services Tools to generate client stubs etc I always seem to get the error "The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page."
> See attached screen shots which shows I have it configured (correctly from what I can tell)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTIS-70) JBTIS Kepler component content
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-70?page=com.atlassian.jira.plugin.s... ]
Paul Leacu updated JBTIS-70:
----------------------------
Description:
Welcome to Kepler.
JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here:
https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
The specific files to change are:
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
The Kepler JBTIS target platform is here:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
I'll process the PR and regenerate the aggregate update site.
Thanks!
--paull
was:
Welcome to Kepler.
JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please build your component for Kepler and update your contribution to the integration stack. The release procedure is here:
https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
The specific files to change are:
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
The Kepler JBTIS target platform is here:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
I'll process the PR and regenerate the aggregate update site.
Thanks!
--paull
> JBTIS Kepler component content
> ------------------------------
>
> Key: JBTIS-70
> URL: https://issues.jboss.org/browse/JBTIS-70
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BPEL, BPMN2, drools/ jBPM5, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
> Affects Versions: 4.1.0
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.1.0
>
>
> Welcome to Kepler.
> JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here:
> https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
> The specific files to change are:
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> The Kepler JBTIS target platform is here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> I'll process the PR and regenerate the aggregate update site.
> Thanks!
> --paull
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTIS-70) JBTIS Kepler component content
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-70?page=com.atlassian.jira.plugin.s... ]
Rob Cernich commented on JBTIS-70:
----------------------------------
Hey Paul,
Were you going to create an individual JIRA for each component?
The next tooling release for SwitchYard will be 1.0. Depending on the project schedule, I'm not sure whether or not the 1.0 release will target Kepler or will remain on Juno.
I suspect other projects may already be compatible with Kepler. If that is the case, those projects should not have to provide a specific Kepler build (i.e. their current release may work just fine).
Rob
> JBTIS Kepler component content
> ------------------------------
>
> Key: JBTIS-70
> URL: https://issues.jboss.org/browse/JBTIS-70
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BPEL, BPMN2, drools/ jBPM5, ESB, Fuse IDE, modeshape, savara, switchyard, teiid
> Affects Versions: 4.1.0
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.1.0
>
>
> Welcome to Kepler.
> JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please build your component for Kepler and update your contribution to the integration stack. The release procedure is here:
> https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
> The specific files to change are:
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de...
> The Kepler JBTIS target platform is here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> I'll process the PR and regenerate the aggregate update site.
> Thanks!
> --paull
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month