December 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ] Debbie Steigner closed TEIIDDES-2748. ------------------------------------- Resolution: Won't Fix > ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2748 > URL: https://issues.jboss.org/browse/TEIIDDES-2748 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected. > On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked. > On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation> > The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ] Debbie Steigner commented on TEIIDDES-2748: ------------------------------------------- Closing per Ted, we still do not support RPC only document literal for wsdls. > ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2748 > URL: https://issues.jboss.org/browse/TEIIDDES-2748 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected. > On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked. > On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation> > The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Convert WS models to procedures when exporting Dynamic VDB

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2720: ------------------------------------------ [~blafond] not really sure, I created this jira based on your comment on TEIIDDES-2699 : https://issues.jboss.org/browse/TEIIDDES-2699?focusedCommentId=13126949&p... > Convert WS models to procedures when exporting Dynamic VDB > ---------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2.1 > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2720) Convert WS models to procedures when exporting Dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2720: ---------------------------------------- [~asmigala] What would the virtual procedure look like based on a WS model? Interfaces, Operations, Input/Output messages, SQL statement? > Convert WS models to procedures when exporting Dynamic VDB > ---------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2.1 > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2389. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/2cdfe764e25a64f54... > Add ui support for whole texttable no trim > ------------------------------------------ > > Key: TEIIDDES-2389 > URL: https://issues.jboss.org/browse/TEIIDDES-2389 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Patch Release, Teiid Integration, Transformations > Environment: Teiid 8.8.0 Final > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: File-connector, TEXTTABLE, TRIM > Fix For: 9.2.1 > > > TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example: > a , "b" > would be parsed as > a ,b - such that the space is preserved after a, but the qualified entry is unaffected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1988) Create a Data Source Guide

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1988?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1988. ---------------------------------- Resolution: Won't Do > Create a Data Source Guide > -------------------------- > > Key: TEIIDDES-1988 > URL: https://issues.jboss.org/browse/TEIIDDES-1988 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 10.1 > > > Create a Data Source guide to capture all the aspects of data source management from the tooling perspective. > * Include info on Teiid Translators and resource adapters > * Include details and screenInclude details and screen caps for all available Connection Profile wizards from: > ** Data Tools project > ** BIRT (MongoDB, HIVE, POJO, etc...) > ** Teiid Designer caps for all available Connection Profile wizards from: > First draft at: http://docs.jboss.org/teiid/designer/8.3/connections-guide/en-US/html/ind... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2610) Add some default values to importer properties in Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2610?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2610. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/9e69a7b532d1bff92... > Add some default values to importer properties in Teiid Connection Importer > --------------------------------------------------------------------------- > > Key: TEIIDDES-2610 > URL: https://issues.jboss.org/browse/TEIIDDES-2610 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Patch Release > Affects Versions: 9.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2.1 > > Attachments: SelectTranslatorPage.patch, TeiidPropertyDefinition.patch > > > Importing JDBC sources via Teiid Connection importer can be streamlined by providing/setting certain default import property values. > 2 such properties are: > *Table Types* > *TABLE* > *use Qualified Name* > *false* > This will help in the most common use-case to reduce the number of steps to importer and improve the experience of first-time users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2635) Provide manageability of DDL based models/vdb's and .xmi models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2635?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2635. ---------------------------------- Resolution: Won't Do Dynamic VDB import/export features were intended to be the temporary fix until Komodo work progresses with VDB Builder (CLI) and another UI Editor/Navigator. Adding a companion DDL file for each model will open a can of worms, and a boatload of work, to keep in sync while editing/saving the models. Marking as Won't Do and banking on the upcoming releases of Komodo tools. > Provide manageability of DDL based models/vdb's and .xmi models > ---------------------------------------------------------------- > > Key: TEIIDDES-2635 > URL: https://issues.jboss.org/browse/TEIIDDES-2635 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Reporter: Van Halbert > Assignee: Barry LaFond > > Copying comments from planning: > Per Ramesh, the suggestion/proposal (we talked about this couple times) is to keep a DDL version of the Model along with the XMI model in separate tab in the Designer and let users check in the DDL version into the SVN/GIT using "team" feature in the Eclipse. Since DDL file will be text based, the merge and diff are facilities provided through Eclipse tools. We need to use the team import feature to update the XMI model when reading from SVN/GIT. This will give us closest collaboration platform we are looking for without waiting for Komodo and I believe it is fairly achievable goal. > Barry: > The initial import/export (generate) features for dynamic vdbs perform the needed operations. Now that we have both *.vdb and -vdb.xml resources we can think more about how to assist the user. CSV/GIT in Eclipse is certainly an attractive option. Linking a -vdb.xml file to a *.vdb and auto-saving both is also an option. And as Van said, differencing via CSV/GIT would be the direction I'd vote for. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2388: ----------------------------------- Component/s: Teiid Integration > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release, Teiid Integration > Affects Versions: 8.6.1 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Blocker > Fix For: 9.2.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2326: ---------------------------------------- Possibly break up the wizard and provide option to persist/save the json/xml artifacts in the workspace (project) ? > REST/SOAP importers - Re use of the connection profile after restart > -------------------------------------------------------------------- > > Key: TEIIDDES-2326 > URL: https://issues.jboss.org/browse/TEIIDDES-2326 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 9.2.1 > > Attachments: nomodel.png > > > Often times, as user I start the import of WSDL based or REST (with new one, or old with file and URL selection) service and go through the wizard, something does not work right. So, I typically remove the models generated, and then try the import process again. However, next time when I select the same connection profile I created before, I very seldom get same results. If I restarted the Designer for any reason, the previously created connection profile for sure does not work. > It seems to me that, designer stores a temp XML/JSON file from where it starts processing, during the restart that gets deleted and import process instead of sending another request for the results document it fails with arbitrary error. There is no way to recover form it. IMO, REST and SOAP needs to be treated differently from XML File type sources and issue the query to get response document, not store it anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2015