February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-392) SAP WSDL URLs do not validate with the SOAP-Relational importer.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-392?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-771 to TEIIDDES-392: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-392 (was: JBEDSP-771) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > SAP WSDL URLs do not validate with the SOAP-Relational importer. > ---------------------------------------------------------------- > > Key: TEIIDDES-392 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-392 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: John Doyle > Assignee: John Doyle > > The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate. -- 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-390) Make com.metamatrix.modeler.dqp plugin and helper classes more testable

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-390?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-655 to TEIIDDES-390: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-390 (was: JBEDSP-655) Component/s: Housekeeping (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Make com.metamatrix.modeler.dqp plugin and helper classes more testable > ----------------------------------------------------------------------- > > Key: TEIIDDES-390 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-390 > Project: Teiid Designer > Issue Type: Bug > Components: Housekeeping > Reporter: Barry LaFond > Priority: Minor > > com.metamatrix.modeler.dqp contains unnecessary nested helper classes and methods that make it difficult to unit test. Spending some time to redesign and refactor makes a lot of sense. -- 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-391) Model Editor notification framework sometimes suppresses required change notifications

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-391?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-263 to TEIIDDES-391: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-391 (was: JBEDSP-263) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.4) > Model Editor notification framework sometimes suppresses required change notifications > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-391 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-391 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Barry LaFond > > A fix was implemented for Defect 22480 that covers the fact that performing a "rename" of an column in the same transaction as a "Move" within it's parent is not sending a rename notification. The fix was to break the transaction up into Two transactions, separating the rename into it's own. > This problem needs to get addressed at a later date from the txn/Model Editor framework standpoint. -- 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-388) Build XML Message Structure Wizard Creates Objects With Name Conflicts

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-388?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-83 to TEIIDDES-388: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-388 (was: JBEDSP-83) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.2) > Build XML Message Structure Wizard Creates Objects With Name Conflicts > ---------------------------------------------------------------------- > > Key: TEIIDDES-388 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-388 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Fedora 8 > Reporter: Dan Florian > Assignee: Dan Florian > Priority: Minor > > Execute step 4.s of the XSD Message Structure Visualization Test Spec differently than document by hitting the Next button instead of the Finish button. This time the XML document generated has the same name as the first XML document. When executing step 4.s as documented there is no name conflict. Since you can rename one of the documents this is not a critical 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-389) Query Plan Viewer: Double-clicking on a source query access node creates a screen that spans two windows in a multi-monitor display, but should default to single screen

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-389?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-380 to TEIIDDES-389: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-389 (was: JBEDSP-380) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Query Plan Viewer: Double-clicking on a source query access node creates a screen that spans two windows in a multi-monitor display, but should default to single screen > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-389 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-389 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > Attachments: screenshot-1.jpg > > > Double-click on a source query access node in the query plan viewer in Designer. If you are using a multiple-monitor display, the source query will span both screens. This is awkward and hard to read. The default should be single-screen if possible. Minor usability issue. -- 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-386) Add validation rule for missing names in source for physical tables

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-386?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-756 to TEIIDDES-386: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-386 (was: JBEDSP-756) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Add validation rule for missing names in source for physical tables > ------------------------------------------------------------------- > > Key: TEIIDDES-386 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-386 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Environment: All > Reporter: Paul Nittel > Assignee: Barry LaFond > Attachments: wtf_parts_porsche.png > > > I created a physical model and added names in source for the columns, forgetting the table. It validates OK. I wired it to a connector binding and tried to preview the data. This failed with a rather verbose, ugly Oracle error. See attached screenshot. > Should/Can we add a new rule to validate the presence of all names in source for source models. > (Once I defined the tables NIS, it worked fine.) -- 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-387) Web Service to Relational Source Model importer - Validation of WSDL doesn't actually validate the WSDL

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-387?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1112 to TEIIDDES-387: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-387 (was: JBEDSP-1112) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.4) > Web Service to Relational Source Model importer - Validation of WSDL doesn't actually validate the WSDL > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-387 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-387 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Fedora 10, build 3252 > Reporter: Paul Nittel > Assignee: Barry LaFond > > 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 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-385) Designer Preview function does not work on Materialized View tables

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-385?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-728 to TEIIDDES-385: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-385 (was: JBEDSP-728) Component/s: Modeling (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Designer Preview function does not work on Materialized View tables > ------------------------------------------------------------------- > > Key: TEIIDDES-385 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-385 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Environment: Designer on Win32 > Reporter: Steve Jacobs > Assignee: Mark Drilling > Attachments: PreviewMatViewException.txt, PreviewMatViewTables.bmp > > > Ran Preview function on a Virtual table. Then I set the table property Materialized = true and saved the model. Preview now fails with the message "does not exist". > Ramesh recommends that the preview functionality should add "OPTION NOCACHE" to the preview queries. -- 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-384) Merge Designer IDE towards JBoss Dev Studio

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-384?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1181 to TEIIDDES-384: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-384 (was: JBEDSP-1181) Component/s: Eclipse Integration (was: Designer) Fix Version/s: 6.0.0 (was: 6.0.0) > Merge Designer IDE towards JBoss Dev Studio > ------------------------------------------- > > Key: TEIIDDES-384 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-384 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Reporter: Marc Shirley > Fix For: 6.0.0 > > -- 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-383) Connector Binding/Connector Type property name display is inconsistent.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-383?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-724 to TEIIDDES-383: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-383 (was: JBEDSP-724) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Connector Binding/Connector Type property name display is inconsistent. > ----------------------------------------------------------------------- > > Key: TEIIDDES-383 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-383 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer on Linux, Windows > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > > The display of binding property names in the Properties window is inconsistent. The name of the property is correct derived from the connector type property DisplayName when a binding is selected in the Connectors view. The name of the property is incorrectly derived from the connector types property Name when a connector type is selected in the Connectors view. > eg, Clicking on the SalesforceConnector type, shows a 'username' property in the Properties view. Clicking on an active Salesforce binding, shows a 'User Name' property. -- 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