February 2010 - teiid-designer-issues

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-291?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1026 to TEIIDDES-291: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-291 (was: JBEDSP-1026) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.2) (was: 5.5.3) > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-290) The SOAP-Relational Connector should put the SOAPAction header in double qoutes.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-290?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-283 to TEIIDDES-290: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-290 (was: JBEDSP-283) Component/s: Import/Export (was: Connectors) (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.1) (was: 5.5.2) (was: 5.5) > The SOAP-Relational Connector should put the SOAPAction header in double qoutes. > -------------------------------------------------------------------------------- > > Key: TEIIDDES-290 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-290 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > > The SOAP-Relational connector does not put the SOAPAction header in quotes. According to the SOAP 1.1 specification, double-quotes are required. This can cause some services to throw the following exception: > Soap method is not allowed to invoke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-289) Designer shows view for Cheat Sheets which no longer exists

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-289?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-766 to TEIIDDES-289: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-289 (was: JBEDSP-766) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > Designer shows view for Cheat Sheets which no longer exists > ----------------------------------------------------------- > > Key: TEIIDDES-289 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-289 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Designer RC2 Windows environment > Reporter: Warren Gibson > Priority: Minor > > Designer still shows a view for Cheat Sheet. You can get to it via: Windows/Show View/Other/Cheat Sheet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-288) Navigation Problem In Search Result View When Multiple Resources Involved

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-288?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-860 to TEIIDDES-288: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-288 (was: JBEDSP-860) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: (was: Westport) > Navigation Problem In Search Result View When Multiple Resources Involved > ------------------------------------------------------------------------- > > Key: TEIIDDES-288 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-288 > Project: Teiid Designer > Issue Type: Bug > Reporter: Dan Florian > Assignee: Dan Florian > > When using tree layout in the search results view, if matches are shown from multiple resources, the up/down toolbar navigation buttons will not navigate to the previous/next match if the match is in a different resource. This was not entirely implented. See MetadataSearchResultPage. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-287) The modeler doesn't use the same criteria for displaying properties as the console

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-287?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-302 to TEIIDDES-287: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-287 (was: JBEDSP-302) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: (was: Westport) > The modeler doesn't use the same criteria for displaying properties as the console > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-287 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-287 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Minor > > The console uses the 'Hidden' property to hide/show additional properties. Whereas the modeler shows an 'Expert' toggle. It would be good if they had consistent properties displays. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-286) Query Plan Viewer does not show dependent access node's source queries in query plan

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-286?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-381 to TEIIDDES-286: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-286 (was: JBEDSP-381) Component/s: Diagrams (was: Designer) Fix Version/s: 7.1 (was: Westport) Affects Version/s: (was: 5.5) > Query Plan Viewer does not show dependent access node's source queries in query plan > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-286 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-286 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Reporter: Michael Walker > Assignee: Barry LaFond > Fix For: 7.1 > > Attachments: depdenentaccess.JPG > > > In a dependent join situation, the query plan shows the source query for the dependent feeder node, but does not show the source query for the dependent "access" or "wait" node. This is not consistent behavior. see screenshot. > By accessing the "wait" node's properties, the source query can be found. However, if the source query is long, it will be truncated, and there is no way to view the entire query if it is displayed in this properties window only (due to another bug). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-285) Designer install into folder containing spaces results in VDB creation errors

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-285?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1001 to TEIIDDES-285: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-285 (was: JBEDSP-1001) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: (was: Westport) (was: 5.5.3) (was: 5.5.4) (was: 5.5.3 CCE) > Designer install into folder containing spaces results in VDB creation errors > ------------------------------------------------------------------------------ > > Key: TEIIDDES-285 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-285 > Project: Teiid Designer > Issue Type: Bug > Environment: Windows > Reporter: Mark Drilling > Assignee: Barry LaFond > > This Issue has been encountered multiple times. > If the Designer is installed in a directory that contains spaces in its name, we are unable to build/save a VDB. > For example, if the Designer is installed in C:\Program Files\MetaMatrix\EnterpriseDesigner and we create a new VDB and add models to it, everything appears fine. When we perform a Save, we see an error indicated on the VDB Overview page. > ERROR - This VDB cannot be deployed for data access > On the VDB Problems page we see an error message: > Missing model import to resource ../../../../../../../../../../../Program%2520Files/MetaMatrix/EnterpriseDesigner/workspace/.metadata/.plugins/com.metamatrix.vdb.edit/vdbWorkingFolder/1174623145637_392809865332324117/builtInDataTypes.xsd > No log file is produced and no errors seem to be logged to Designer's Problems view. > It appears the space in the referenced file name may not be encoded properlly. The URL encoded value used is %2520. I think it should be %20 (decimal 32) however this may be wchar or UTF-8. In either case, the space is the cause of the issue. If I rename the Program Files directory to ProgramFiles, all is fine. (i.e. C:\ProgramFiles\MetaMatrix\EnterpriseDesigner. > The use case for the client suggests that the client toosl should be installed according to standard business logic and placed in a common location. This common location may contain spaces in the path name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-284) Transformation editor should preserve any valid text formatting created by the user, especially when working with virtual procedures

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-284?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-365 to TEIIDDES-284: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-284 (was: JBEDSP-365) Component/s: Diagrams (was: Designer) Fix Version/s: 7.1 (was: Westport) > Transformation editor should preserve any valid text formatting created by the user, especially when working with virtual procedures > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-284 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-284 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Reporter: Michael Walker > Fix For: 7.1 > > Attachments: transformationexample.JPG > > > In the transformation editor, we should preserve any valid formatting created by the user, including: > i. Whitespace > ii. Tabs > iii. Spaces > iv. Capitalization > v. Name qualification (e.g. if they don't use fully-qualified names and it's not required for validation, then preserve it) > This is especially important for virtual procedure editing, though it should extend to any transformation editing. Currently, when a user validates their virtual procedure, we wipe out all these changes, which drives them crazy. > Even worse, if the procedure doesn't validate correctly, we remove our standard tabbed/spaced formatting, and the entire procedure becomes one gigantic string without carriage returns. This is very difficult to read, especially when working with any sizable procedure, and makes the debugging process nearly impossible. See screenshot. > Most users at Genentech that develop stored procedures are literally copying and pasting the procedure code back and forth between notepad and Designer to avoid this issue. This is a severe usability defect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-283) Request better error messaging in Designer

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-283?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1158 to TEIIDDES-283: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-283 (was: JBEDSP-1158) Component/s: (was: Designer) Fix Version/s: (was: Westport) (was: Future Versions) Affects Version/s: 7.1 (was: 5.5.3) > Request better error messaging in Designer > ------------------------------------------ > > Key: TEIIDDES-283 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-283 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > > When a connector binding has been incorrectly configured (incorrect password) to a database, invoking a query in the Designer results in the following error: > "Unable to create a connection for request com.metamatrix.dqp.message.CapabilitiesMessage@1a41809" > This message needs to be made more intuitive if possible. Otherwise I foresee many MMTS calls resulting that might otherwise be handled by the customer. > Steps to Reproduce: Edit a working connector binding & change the password to an incorrect one. Run a query against it. > Actual results: Obscure message above. > Expected results: "Access to data resource [blah] denied. Incorrect username or password." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-282) XML Modeling Enhancement - preview of memory management

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-282?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1156 to TEIIDDES-282: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-282 (was: JBEDSP-1156) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.1) (was: Future Versions) > XML Modeling Enhancement - preview of memory management > ------------------------------------------------------- > > Key: TEIIDDES-282 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-282 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 7.1 > Reporter: Debbie Steigner > > XML Modeling - when building by schema component we need to have some kind of a preview or work on the memory management because even taking one root element from JC3IEDM and building from schema caused the Designer to lock up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2010