[JBoss JIRA] (TEIIDDES-1544) Error While Generating WAR in Teiid 8.0
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1544?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1544.
---------------------------------
Resolution: Cannot Reproduce Bug
> Error While Generating WAR in Teiid 8.0
> ---------------------------------------
>
> Key: TEIIDDES-1544
> URL: https://issues.jboss.org/browse/TEIIDDES-1544
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.0
> Reporter: Ajit Kumar Nayak
> Assignee: Ted Jones
> Fix For: 8.1
>
>
> Hi,
> I am using
> JBOSS AS 7.1.1
> teiid-8.0.0.Final-jboss-dist
> teiid-designer-8.0.0.Beta1-v20121114-1958-H144.zip
> jbossws-cxf-4.1.0.Final
> I am getting error while creating CXF-WAR for my VDB
> As
> java.lang.RuntimeException: File SimpleDatatypes-instance does not exist.
> 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: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.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: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: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)
--
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-1567) WSDL for two different web services contains methods for both
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1567?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1567.
---------------------------------
Resolution: Rejected
The WSDL is generated based on the web service models in the VDB for which the web service WAR is generated. If both web service models are in the VDB, then the WSDL will be the same.
> WSDL for two different web services contains methods for both
> -------------------------------------------------------------
>
> Key: TEIIDDES-1567
> URL: https://issues.jboss.org/browse/TEIIDDES-1567
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 7.4.2
> Environment: Windows 7
> Reporter: Michael Conner
> Assignee: Ted Jones
> Priority: Minor
> Fix For: 8.1
>
>
> I create two different web services, each for a different procedure. I then generate the JBossWS-CXF war, and look at the wsdl. The wsdl for the services are identical, with each containing the other.
--
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-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1436:
--------------------------------
Fix Version/s: 8.2
(was: 8.1)
> Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1436
> URL: https://issues.jboss.org/browse/TEIIDDES-1436
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.2
>
> Attachments: foo.zip
>
>
> "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH
--
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-1637) Make selection of tables/columns less cumbersome in Teiid Designer Data Roles
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1637?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-2454 to TEIIDDES-1637:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-1637 (was: TEIID-2454)
Affects Version/s: (was: 8.3)
Component/s: Teiid Integration
(was: Tools)
> Make selection of tables/columns less cumbersome in Teiid Designer Data Roles
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1637
> URL: https://issues.jboss.org/browse/TEIIDDES-1637
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Environment: As used in SOA-P 5.3
> Reporter: Rick Wagner
> Assignee: Steven Hawkins
>
> Make selection of tables/columns less cumbersome in Teiid Designer Data Roles. For example, if you have view that contains say 100 columns and you want to setup a role to give only 5 columns (c1, c2, c3, c4, c5) access out of 100 columns, you can't select only c1, c2, c3, c4, c5 which throws an error "Cannot change Element state - the Parent element must be enabled first."
> So we need to select on view which automatically selects all 100 columns and then uncheck one by one all the 95 columns. Can this be fixed to select needed child columns in the view which should automatically select parent and no need to uncheck one by one all the 95 columns ?
--
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