January 2012 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-585) Remove XML Service metamodel as it is no longer used.

by Ken Johnson (JIRA)

Remove XML Service metamodel as it is no longer used. ----------------------------------------------------- Key: TEIIDDES-585 URL: https://jira.jboss.org/browse/TEIIDDES-585 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: JBTools Aug 26, 2010. Eclipse 3.6, RHEL 6 Beta Reporter: Ken Johnson The XML Service metamodel is no longer used for sourcing XML data. It should be removed from Designer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-434) Input sets in XML Document model don't have access to elements in parent mapping classes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-434?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-434: ---------------------------------- Fix Version/s: 7.7.1 Description: Input sets in XML Document model don't have access to elements in parent mapping classes, currently the only way something will show in any input set is if you have a mapping class and transformation at the root element. was: Input sets in XML Document model don't have access to elements in parent mapping classes, currently the only way something will show in any input set is if you have a mapping class and transformation at the root element. > Input sets in XML Document model don't have access to elements in parent mapping classes > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-434 > URL: https://issues.jboss.org/browse/TEIIDDES-434 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 7.7.1 > > > Input sets in XML Document model don't have access to elements in parent mapping classes, currently > the only way something will show in any input set is if you have a mapping class and transformation at the root element. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-387) Web Service to Relational Source Model importer - Validation of WSDL doesn't actually validate the WSDL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-387?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-387: ---------------------------------- Fix Version/s: 7.7.1 > Web Service to Relational Source Model importer - Validation of WSDL doesn't actually validate the WSDL > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-387 > URL: https://issues.jboss.org/browse/TEIIDDES-387 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Fedora 10, build 3252 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 7.7.1 > > > I've seen this on Windows and Fedora 10. > 1 - Create a project > 2 - Create a relational source model > 3 - Right-click the model > Import > Web service as relational source model > 4 - Enter a URL that is well-formed, but totally bogus (http://www.sdfdsf.com/asdfsdf.wsdl) > 5 - Click the Validate WSDL button > 6 - The wizard flashes briefly, but comes back with no error messages visible > 7 - Click Next > Now you get a WSDL parse error > I would think the Validate WSDL button would actually validate the WSDL, but apparently it does not. (It should.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-392) WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-392?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-392: ---------------------------------- Fix Version/s: 7.7.1 > WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs. > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-392 > URL: https://issues.jboss.org/browse/TEIIDDES-392 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0, 7.3 > Reporter: John Doyle > Fix For: 7.7.1 > > > The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate because SAP requires HTTP basic auth to get the WSDL. The importer should support this and the new Web Service connection profile should provide the credentials. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-362) add ability to import WSDLs from https sources

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-362?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-362: ---------------------------------- Fix Version/s: 7.7.1 > add ability to import WSDLs from https sources > ---------------------------------------------- > > Key: TEIIDDES-362 > URL: https://issues.jboss.org/browse/TEIIDDES-362 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Fix For: Future, 7.7.1 > > > I-T 278448. Request to add ability to import wsdl to relational from an https source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-354) WSDL to Relational Importer is not modeling attributes correctly.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-354?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-354: ---------------------------------- Fix Version/s: 7.7.1 > WSDL to Relational Importer is not modeling attributes correctly. > ----------------------------------------------------------------- > > Key: TEIIDDES-354 > URL: https://issues.jboss.org/browse/TEIIDDES-354 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: John Doyle > Labels: wsdltorelational > Fix For: 7.7.1 > > > Import the attached WSDL. In the find service table the generic, businessKey and maxRows columns should all have values in the DataAttributName property. Since they do not they are created as elements in the request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-325) Web Service As Relational importer cannot handle web services that have an input but no output

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-325?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-325: ---------------------------------- Fix Version/s: 7.7.1 > Web Service As Relational importer cannot handle web services that have an input but no output > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-325 > URL: https://issues.jboss.org/browse/TEIIDDES-325 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Environment: 5.5SP3 GA Designer on Linux > Reporter: Greg Haber > Assignee: Barry LaFond > Fix For: 7.7.1 > > Attachments: StockQuoteService-ghh.wsdl, StockQuoteService.wsdl > > > If you try to use the Web Service As Relational Importer on the attached StockQuoteService.wsdl file (a sample from the Axis2 1.3 distribution), you'll find that while it passes validation, if on the WSDL Operations Selection screen you leave the selections at their defaults (both of the SOAP 1.1 web services selected, and the SOAP 1.2 web services unchecked), when you press Finish you'll get an NPE. But if you uncheck the "update" service (leaving only getPrice selected), then you can click Finish and create the source model. > The issue with the "update" operation is that it is an operation with an input but no output. If you modify the WSDL so that this service does indeed have an output (per the StockQuoteService-greg.wsdl attached), both services will import successfully. > We should be able to handle such operations (ones with no output). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-319) Request for single table import option in Web Service As Relational web service

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-319?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-319: ---------------------------------- Fix Version/s: 7.7.1 > Request for single table import option in Web Service As Relational web service > ------------------------------------------------------------------------------- > > Key: TEIIDDES-319 > URL: https://issues.jboss.org/browse/TEIIDDES-319 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Environment: 5.5.3 GA on Linux > Reporter: Greg Haber > Assignee: Barry LaFond > Fix For: 7.7.1 > > > This is a longer term feature request - not expecting any near term resolution. > It would be great if the web service as relational importer could have an option to model a web service with a single table representing both the request and response, instead of as separate tables as today. Not sure if it makes sense to allow this for heirarchical response web services, or only simple ones returning a flat schema. > Whenever possible I always manually model web service connections this way because of the pros - but would be much better if the importer would do it for me. > Pros: > -Would avoid multiple queries to web service connector for a single web service call (since XML-Relational connectors don't support join pushdown) - simpler query plans > -With that single call it lessens use/paves way for disabling the XML-Relational connector internal doc cache (which, at least in 5.0SP2, was a _big_ bottleneck in the field with concurrent calls to the same web service, if the web service takes more than a few seconds to respond - I believe because the whole doc cache is locked on both read and write, effectively resulting in single threaded and blocking behavior. Anyway, just speculating on the cause, but it is established that in 5.0SP2 that single-table web services were much faster than multi-table ones). > -Would work in preview > Cons: > -Does not logically represent the way web services actually work > -Confusing as it jumbles together elements from two XML docs in a single relational base table -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-306) xsi:type attributes not being created in XML document instances when required

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-306?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-306: ---------------------------------- Fix Version/s: 7.7.1 > xsi:type attributes not being created in XML document instances when required > ----------------------------------------------------------------------------- > > Key: TEIIDDES-306 > URL: https://issues.jboss.org/browse/TEIIDDES-306 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: John Verhaeg > Priority: Minor > Fix For: 7.7.1 > > > When an XSD element or its type is marked as abstract, the concrete elements used in the instance document to represent the abstract element must contain an xsi:type attribute with a concrete type as a value. It seems the best way to handle this in the future would be to add a new "type criteria" property and editor to transformations that would behave somewhat like the choice criteria editor. The editor would prompt the user specify one or more concrete types along with criteria used by the server to determine which type to use for a given set of data. This defect is a carryover from defect 20067 in Defect Tracker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-291) XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-291: ---------------------------------- Fix Version/s: 7.7.1 > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://issues.jboss.org/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Priority: Minor > Fix For: 7.7.1 > > Attachments: XSDTest7.java > > > See the issue tracker: > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > Take a look at section 2.2.2.2 of the XSD spec. > http://www.w3.org/TR/xmlschema-1/ > Or this nice example: > http://www.w3schools.com/Schema/schema_complex_subst.asp > As I read the spec, these substitution groups have no effect on the structure of the XML defined by the XSD, only the names that allowed for a particular element in the XML. > We don't support this in the importer now. We would have to add functionality to find the substitution groups and add additional XPaths so that the connector could either /name or /navn in the xml document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2012