[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2028.
----------------------------------
Resolution: Done
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Future
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-2028:
------------------------------------
Assignee: Barry LaFond (was: Ted Jones)
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: Future
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1037:
---------------------------------------------------
Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1093210|https://bugzilla.redhat.com/show_bug.cgi?id=1093210] from ASSIGNED to VERIFIED
> Data types inported from flat file partially implemented in wizard
> ------------------------------------------------------------------
>
> Key: TEIIDDES-1037
> URL: https://issues.jboss.org/browse/TEIIDDES-1037
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 7.5
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Fix For: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, out.webm, sample.csv
>
>
> The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement.
> I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing.
> Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point.
> The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-1037.
----------------------------------
verified TD 9.0.1.Final
> Data types inported from flat file partially implemented in wizard
> ------------------------------------------------------------------
>
> Key: TEIIDDES-1037
> URL: https://issues.jboss.org/browse/TEIIDDES-1037
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 7.5
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Fix For: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, out.webm, sample.csv
>
>
> The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement.
> I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing.
> Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point.
> The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months