[JBoss JIRA] (TEIIDDES-1303) Add OData Translator to Designer
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1303?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1303:
--------------------------------
Summary: Add OData Translator to Designer (was: Create OData Importer)
> Add OData Translator to Designer
> --------------------------------
>
> Key: TEIIDDES-1303
> URL: https://issues.jboss.org/browse/TEIIDDES-1303
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: Komodo
>
>
> To provide support for more complicated OData use cases, we should extend the XML Importer to create an OData importer. This importer will read the metadata of the service in the selected CP and determine what columns are allowable for input. We would then need to create an access pattern on the generated base table for these fields. These fields would be added to the URL of the service.. so the above Bank service URL would become:
> http://gw.esworkplace.sap.com/sap/opu/sdata/sap/DEMO_BANK/z_demo_bankColl...
> and the generated transformation should take the column values from the access pattern and build the URL accordingly in the invokeHttp() call.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-1641:
-------------------------------------
Lucie,
I think the version of JBT may be the cuprit here. Try using JBT 4 for Juno.. see here: http://www.jboss.org/tools/download/installation.html
> Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
> ---------------------------------------------------------
>
> Key: TEIIDDES-1641
> URL: https://issues.jboss.org/browse/TEIIDDES-1641
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.8
> Environment: fedora 17, x86_64,
> eclipse juno 4.0, sr1
> teiid designer 8.1.alpha2 (also 7.8)
> Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
> server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> java jdk 1.6.0_33
> Reporter: Lucie Fabrikova
> Attachments: WebServ.zip
>
>
> !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
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
13 years
[JBoss JIRA] (TEIIDDES-1560) Add Support for Query Parameters in Generated REST War
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1560?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1560:
--------------------------------
Release Notes Text: The generated REST WAR now support query parameters in addition to URI parameters and XML/JSON inputs. Query parameters can be specified in the target REST procedure's URI property using "&" as a delimiter. For example: REST:URI = rootURI&parm1&parm2 or authors&authorFirstName&authorLastName. (was: The generated REST WAR now support query parameters in addition to URI parameters and XML/JSON inputs. Query parameters can be specified in the target REST procedure's URI property using "&" as a delimiter. For example: REST:URI = authors&parm1&parm2. )
> Add Support for Query Parameters in Generated REST War
> ------------------------------------------------------
>
> Key: TEIIDDES-1560
> URL: https://issues.jboss.org/browse/TEIIDDES-1560
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Web Services Support
> Affects Versions: 7.8, 8.0
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 7.7.2, 8.1
>
>
> The generated REST war supports path parameters and XML/JSON inputs, but does not allow for query parameters. We should support query parameters as well.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1140) Model Extension Definition Validation Should Report All Validation Messages And Not Stop When It Finds The First Error
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1140?page=com.atlassian.jira.plu... ]
Dan Florian resolved TEIIDDES-1140.
-----------------------------------
Fix Version/s: 8.1
(was: 8.2)
Resolution: Done
The pull request was merged about a month ago in the 8.1 branch.
> Model Extension Definition Validation Should Report All Validation Messages And Not Stop When It Finds The First Error
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1140
> URL: https://issues.jboss.org/browse/TEIIDDES-1140
> Project: Teiid Designer
> Issue Type: Task
> Components: Editors
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Dan Florian
> Fix For: 8.1
>
>
> The validation being done associated with MEDs is being done by the ModelExtensionDefinitionValidator. While the validator does perform validation in lots of different areas and reports issues in each of those areas, it does not report multiple issues within the same category. For instance, when the validator looks at all property definitions, it will only report the first error it finds in any of the property definitions. It should report all the problems from all the property definitions. Need to update ValidationStatus class so that it can contain multiple statuses and update the validator to report multiple statuses.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ]
Lucie Fabrikova updated TEIIDDES-1641:
--------------------------------------
Environment:
fedora 17, x86_64,
eclipse juno 4.0, sr1
teiid designer 8.1.alpha2 (also 7.8)
Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
java jdk 1.6.0_33
was:
fedora 17, x86_64,
eclipse juno 4.0, sr1
teiid designer 8.1.alpha2 (also 7.8)
Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
> ---------------------------------------------------------
>
> Key: TEIIDDES-1641
> URL: https://issues.jboss.org/browse/TEIIDDES-1641
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.8
> Environment: fedora 17, x86_64,
> eclipse juno 4.0, sr1
> teiid designer 8.1.alpha2 (also 7.8)
> Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
> server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> java jdk 1.6.0_33
> Reporter: Lucie Fabrikova
> Attachments: WebServ.zip
>
>
> !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
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
13 years
[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ]
Lucie Fabrikova updated TEIIDDES-1641:
--------------------------------------
Attachment: WebServ.zip
> Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
> ---------------------------------------------------------
>
> Key: TEIIDDES-1641
> URL: https://issues.jboss.org/browse/TEIIDDES-1641
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.8
> Environment: fedora 17, x86_64,
> eclipse juno 4.0, sr1
> teiid designer 8.1.alpha2 (also 7.8)
> Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
> server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
> Reporter: Lucie Fabrikova
> Attachments: WebServ.zip
>
>
> !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
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
13 years
[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIIDDES-1641:
-----------------------------------------
Summary: Eclipse Juno 4.0 freezes while generating JBossWS-CXF war
Key: TEIIDDES-1641
URL: https://issues.jboss.org/browse/TEIIDDES-1641
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.8
Environment: fedora 17, x86_64,
eclipse juno 4.0, sr1
teiid designer 8.1.alpha2 (also 7.8)
Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1
server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1
Reporter: Lucie Fabrikova
!ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278
!MESSAGE An error occurred while creating WAR file, check log for detail
!STACK 0
java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
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:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
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:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
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
13 years
[JBoss JIRA] (TEIIDDES-1140) Model Extension Definition Validation Should Report All Validation Messages And Not Stop When It Finds The First Error
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1140?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1140:
-----------------------------------
Fix Version/s: 8.2
(was: 8.1)
> Model Extension Definition Validation Should Report All Validation Messages And Not Stop When It Finds The First Error
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1140
> URL: https://issues.jboss.org/browse/TEIIDDES-1140
> Project: Teiid Designer
> Issue Type: Task
> Components: Editors
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Dan Florian
> Fix For: 8.2
>
>
> The validation being done associated with MEDs is being done by the ModelExtensionDefinitionValidator. While the validator does perform validation in lots of different areas and reports issues in each of those areas, it does not report multiple issues within the same category. For instance, when the validator looks at all property definitions, it will only report the first error it finds in any of the property definitions. It should report all the problems from all the property definitions. Need to update ValidationStatus class so that it can contain multiple statuses and update the validator to report multiple statuses.
--
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
13 years
[JBoss JIRA] (TEIIDDES-1640) Creating a WS operation input or output message when they already exist results in ModelerCoreException
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1640?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1640.
------------------------------------
Resolution: Done
Done. DisabledCommands are ignored and not shown
> Creating a WS operation input or output message when they already exist results in ModelerCoreException
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1640
> URL: https://issues.jboss.org/browse/TEIIDDES-1640
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 Unable to execute Command : org.teiid.designer.core.util.DisabledCommand@34f83a29 null
> at org.teiid.designer.core.ModelEditorImpl.executeCommandInTransaction(ModelEditorImpl.java:1739)
> at org.teiid.designer.core.ModelEditorImpl$5.run(ModelEditorImpl.java:687)
> at org.teiid.designer.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:568)
> at org.teiid.designer.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:612)
> at org.teiid.designer.core.ModelEditorImpl.createNewSiblingFromCommand(ModelEditorImpl.java:698)
> at org.teiid.designer.ui.actions.NewSiblingAction.doRun(NewSiblingAction.java:194)
> at org.teiid.designer.ui.common.actions.AbstractAction$1.run(AbstractAction.java:544)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
--
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
13 years