[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13414:
-------------------------------------------
Even on Juno with the latest code (http://download.jboss.org/jbosstools/updates/stable/juno/) I'm getting the ugly error message preventing me from generating the WS client with the sample WSDL attached. Regardless of whether the message offers any insight into why it failed, it's not letting me continue.
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: web_service_client
> Fix For: LATER
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-13414:
--------------------------------------
Fix Version/s: LATER
(was: 4.1.0.Beta1)
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: web_service_client
> Fix For: LATER
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13414:
-------------------------------------------
Bumping this to later, since I'm not quite sure how to fix it. It seems to throw an error (ugly though it may be) in Kepler with the latest codebase and this is a bit of an edge case.
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: web_service_client
> Fix For: LATER
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-14363:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Rob Stryker)
Assigning to you for comment before working on it. Let me know if I should bring this up to the list before working on it.
> Creation of 'core' component in base
> ------------------------------------
>
> Key: JBIDE-14363
> URL: https://issues.jboss.org/browse/JBIDE-14363
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.1.0.Beta1
> Reporter: Rob Stryker
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
> 1) Only code designed for re-use can live there
> 2) Only fully and properly java-doc'd code can live there
> 3) Only code for use by TWO OR MORE components can live there.
> 4) Addition of dependencies for this component will be strictly regulated
> 5) Code must be properly tested and have tests cases demonstrating it.
> 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
> {code}
> org.jboss.tools.core.platform
> org.jboss.tools.core.platform.ui
> org.jboss.tools.core.wtp
> org.jboss.tools.core.wtp.ui
> {code}
> Bundles such as these would require test bundles, as well as features that keep them separate.
> {code}
> org.jboss.tools.core.platform.feature
> org.jboss.tools.core.wtp.feature
> {code}
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14363:
-----------------------------------
Summary: Creation of 'core' component in base
Key: JBIDE-14363
URL: https://issues.jboss.org/browse/JBIDE-14363
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
1) Only code designed for re-use can live there
2) Only fully and properly java-doc'd code can live there
3) Only code for use by TWO OR MORE components can live there.
4) Addition of dependencies for this component will be strictly regulated
5) Code must be properly tested and have tests cases demonstrating it.
6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
{code}
org.jboss.tools.core.platform
org.jboss.tools.core.platform.ui
org.jboss.tools.core.wtp
org.jboss.tools.core.wtp.ui
{code}
Bundles such as these would require test bundles, as well as features that keep them separate.
{code}
org.jboss.tools.core.platform.feature
org.jboss.tools.core.wtp.feature
{code}
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14361) BrowserSim: LiveReload's port should be detected by BrowserSim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14361?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-14361:
--------------------------------
Description: By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it in BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729 (was: By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it via BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729)
> BrowserSim: LiveReload's port should be detected by BrowserSim
> --------------------------------------------------------------
>
> Key: JBIDE-14361
> URL: https://issues.jboss.org/browse/JBIDE-14361
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it in BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Roopa Chakra (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Roopa Chakra commented on JBIDE-14358:
--------------------------------------
Tried the workaround. I am able to generate client code. Thanks for looking into this issue.
> 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
> Affects Versions: 4.0.0.Final
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
>
> 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
12 years, 11 months