[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: Duplicate Issue
Duplicate of TEIIDDES-1862
> 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.3
>
>
> 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
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1870.
------------------------------------
Resolution: Done
Done
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ]
Paul Richardson resolved TEIIDDES-305.
--------------------------------------
Resolution: Done
> Create an importer for the LDAP Connector
> -----------------------------------------
>
> Key: TEIIDDES-305
> URL: https://issues.jboss.org/browse/TEIIDDES-305
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: Future
> Reporter: Michael Walker
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone.
> The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections.
> The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-305:
----------------------------------
Fix Version/s: 8.3
(was: Future)
> Create an importer for the LDAP Connector
> -----------------------------------------
>
> Key: TEIIDDES-305
> URL: https://issues.jboss.org/browse/TEIIDDES-305
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: Future
> Reporter: Michael Walker
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone.
> The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections.
> The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1887) Deploy and execute VDB throws exceptions if no server is defined
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIIDDES-1887:
-----------------------------------------
Summary: Deploy and execute VDB throws exceptions if no server is defined
Key: TEIIDDES-1887
URL: https://issues.jboss.org/browse/TEIIDDES-1887
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 8.2
Environment: Teiid Designer 8.2.0.Final, JBDS 7.0.0.GA, jdk 1.7
Reporter: Lucie Fabrikova
Assignee: Lucie Fabrikova
Priority: Minor
If no server is defined, deploy or execution of VDB causes an exception.
- rght click VDB: Modeling -> Deploy
Unhandled event loop exception
Caused by: java.lang.NullPointerException
at org.teiid.designer.runtime.ui.actions.DeployVdbAction.checkForConnectedServer(DeployVdbAction.java:221)
at org.teiid.designer.runtime.ui.actions.DeployVdbAction.run(DeployVdbAction.java:125)
- rght click VDB: Modeling -> Execute
java.lang.NullPointerException
at org.teiid.designer.runtime.ui.actions.ExecuteVDBAction.checkForConnectedServer(ExecuteVDBAction.java:127)
at org.teiid.designer.runtime.ui.actions.ExecuteVDBAction.run(ExecuteVDBAction.java:95)
- execute VDB via Guides view:
java.lang.NullPointerException
at org.teiid.designer.runtime.ui.vdb.ExecuteVdbAction.checkForConnectedServer(ExecuteVdbAction.java:88)
at org.teiid.designer.runtime.ui.vdb.ExecuteVdbAction.run(ExecuteVdbAction.java:60)
at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:556)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.launchGuidesAction(TeiidGuidesSection.java:252)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.access$1(TeiidGuidesSection.java:244)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection$3.doubleClick(TeiidGuidesSection.java:153)
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1886) Automatically modify a column name at creating view model from XML schema
by hisao furuichi (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1886?page=com.atlassian.jira.plu... ]
hisao furuichi updated TEIIDDES-1886:
-------------------------------------
> Automatically modify a column name at creating view model from XML schema
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-1886
> URL: https://issues.jboss.org/browse/TEIIDDES-1886
> Project: Teiid Designer
> Issue Type: Bug
> Components: Views
> Affects Versions: 7.7.2
> Environment: Fedora 18
> JBoss Developer Studio 5
> Reporter: hisao furuichi
>
> Teiid designer modify column names automatically even if it's not necessary. I'll write 2 examples to describe this issue.
> 1. In the case of the view model from following schema, even if there are the same column names on the different table, it is numbered automatically.
> (I think that the nameValidator object should be created as new instance every table or table's columns in GenerateVirtualFromXsdHelper.java.)
> <complexType name="table_a">
> <sequence>
> <element ref="tns:column_a" />
> <element ref="tns:column_b" />
> </sequence>
> </complexType>
> <complexType name="table_b">
> <sequence>
> <element ref="tns:column_a" />
> <element ref="tns:column_b" />
> </sequence>
> </complexType>
> 2. If there is a parent element to a column like the following schema, the parent element name is added before column names.
> (See GenerateVirtualFromXsdHelper.java line 213 [2].)
> <element name="table_a">
> <complexType>
> <sequence>
> <element ref="tns:column_a"/>
> <element ref="tns:column_b"/>
> </sequence>
> </complexType>
> </element>
> <element name="table_b">
> <complexType>
> <sequence>
> <element ref="tns:column_a"/>
> <element ref="tns:column_b"/>
> </sequence>
> </complexType>
> </element>
--
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, 6 months
[JBoss JIRA] (TEIIDDES-504) Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-504?page=com.atlassian.jira.plug... ]
Van Halbert reassigned TEIIDDES-504:
------------------------------------
Assignee: Barry LaFond (was: Van Halbert)
> Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-504
> URL: https://issues.jboss.org/browse/TEIIDDES-504
> Project: Teiid Designer
> Issue Type: Task
> Components: Documentation
> Reporter: Larry O'Leary
> Assignee: Barry LaFond
>
> The Intro to Designer training was originally written to use the MMFinancials schema for SQL Server. It appears that some data types are not imported the same way when the MySQL schema is used. This results in data type differences between the written instructions and the MySQL schema that is most commonly used in the Getting Started kit.
> For example, the ProductShares column in the AccountHoldings table is being imported as a biginteger when using SQL Server but as a bigdecimal when using MySQL. This difference then results in reconciler/transformation errors due to type incompatibility which require explicit conversions.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1632) validation problems with trim and concat used together - 7.7.x
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1632?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1632:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1017830
> validation problems with trim and concat used together - 7.7.x
> --------------------------------------------------------------
>
> Key: TEIIDDES-1632
> URL: https://issues.jboss.org/browse/TEIIDDES-1632
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 7.7
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
> Fix For: 7.7.3
>
> Attachments: Trimtest.zip
>
>
> Using the latest JBDS 5.0 and the attached simplified Model Project Set (Trimtest.zip).
> On the view model CCH_V.memmasV change the transformation to [1] and perform a Save/Validate. It will be rewritten to [2] and give a parsing error.
> [1]
> SELECT
> ltrim(Memb.LSTNAM) || ', ' || trim('foo') ||' '|| trim(Memb.MIDNAM) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
> [2]
> SELECT
> ((((ltrim(Memb.LSTNAM) || ', ') || trim( FROM )) || ' ') || trim( FROM Memb.MIDNAM)) AS MEMBER_NAME
> FROM
> CCH.MEMMAS AS Memb
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems for both source and view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1885 at 10/10/13 10:36 AM:
-------------------------------------------------------------------
I wasn't able to repeat the scenario as above in my IDE ... what I found was
1) Import attached DDL file
2) The DDL Importer comes up defaulted to TEIID dialect and Auto-Select == FALSE
* This results in a parsing error on Differences page since the DDL file does not contain Teiid Dialect and the importer was forced to try and parse the DDL using Modeshape DDL Parser
3) Turning Auto-select == TRUE and clicking NEXT
* This results in no error on the Differences page since the importer should have discovered/used the standard SQL92 dialect.
4) FINISH created the desired models
Also tested in a JBDS 7.0 GA + Designer 8.2.Final and got same expected behavior
was (Author: blafond):
I wasn't able to repeat the scenario as above... what I found was
1) Import attached DDL file
2) The DDL Importer comes up defaulted to TEIID dialect and Auto-Select == FALSE
* This results in a parsing error on Differences page since the DDL file does not contain Teiid Dialect and the importer was forced to try and parse the DDL using Modeshape DDL Parser
3) Turning Auto-select == TRUE and clicking NEXT
* This results in no error on the Differences page since the importer should have discovered/used the standard SQL92 dialect.
4) FINISH created the desired models
> DDL importer problems for both source and view models
> ------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
> Attachments: stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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, 6 months