May 2014 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2126) Even Teiid instance is running, user still needs to click "start the server" button to establish a connection with a teiid instance

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2126?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2126: ------------------------------------------- The actual result is as expected. The jboss tools paradigm is always to click the play/start button of the selected jboss server (in the Servers View) before expecting to do anything with the server. The reason no packets were sent is because designer first checks whether the parent jboss server model is in a started state. This model's state is only modified with the pressing of the play/start button. Can think of it in terms of proxy stubs needing to be initialised in the IDE even though the server is up and running. > Even Teiid instance is running, user still needs to click "start the server" button to establish a connection with a teiid instance > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2126 > URL: https://issues.jboss.org/browse/TEIIDDES-2126 > Project: Teiid Designer > Issue Type: Bug > Components: Usability > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 8.5, 8.3.3 > > > Description of problem: > Even Teiid instance is running, user still needs to click "start the server" button to establish a connection with a teiid instance. Without an establishment, "test administration connection" nor "test JDBC connection" is failed. > Version-Release number of selected component (if applicable): > JBDS 7.1.1.GA with Teiid Designer 8.3.2.Final-v20140328-2123-B54 > Steps to Reproduce: > 1: Start JBoss DV 6.0.0 > 2: Start JBDS 7.1.1.GA > 3: Switch to Teiid Designer perspective > 4: On the "Default Teiid Instance" panel located at left side of window, click "mm://127.0.0.1:9999" > 5: On the Overview tab located at center of window, mark the check box with the text label "Server is externally managed. Assume server is started.", and save it > 6: Switch to "Teiid Instance" tab > 7: Click "Test Administration Connection" or "Test JDBC Connection" > Actual results: > "Unable to establish connection to server "mm://127.0.0.1:9999:admin(JDV 6.0.0)"" label is displayed. > Expected results: > "OK" label is displayed > Additional info: > I monitored packet using wireshark, and it looks JBDS didn't send any packet to a teiid instance. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2136) File Source (XML) importer reverses Root patch when typed (Windows)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2136?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2136: ----------------------------------- Fix Version/s: 8.3.3 > File Source (XML) importer reverses Root patch when typed (Windows) > -------------------------------------------------------------------- > > Key: TEIIDDES-2136 > URL: https://issues.jboss.org/browse/TEIIDDES-2136 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.1 > Environment: JBDS 7.1.1 with Teiid Designer 8.3.2.Final-v20140409-1638 installed on Windows > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.5, 8.3.3 > > > On the File Source(XML)>>Source and View Model Importer. On the XML Data Import Options screen, if you try to type in the Root path, cursor returns to the beginning of the field after ever character, so it's entered in reverse. > Same as in the table and view names in: > https://issues.jboss.org/browse/TEIIDDES-1484 > https://issues.jboss.org/browse/TEIIDDES-1421 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2127: ---------------------------------------- The revert is going to be the OPTION properties, schema validation is separate issue. If you add the new properties to SF MED both versions will work fine. > Problem with SF import using Teiid Connection importer - keys not resolved > -------------------------------------------------------------------------- > > Key: TEIIDDES-2127 > URL: https://issues.jboss.org/browse/TEIIDDES-2127 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl > > > There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2133) Query Parsing Error Missing Parameter

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2133?page=com.atlassian.jira.plu... ] Mark Drilling edited comment on TEIIDDES-2133 at 5/7/14 6:33 PM: ----------------------------------------------------------------- I was unable to come up with a transformation that generated the error, but found a problem in the messages.properties file - The placeholder in the below message should be 0, not 1 TeiidParser.teiid_version_failure=The given sql syntax is not supported by the Teiid client version {1} https://github.com/Teiid-Designer/teiid-designer/pull/339 was (Author: mdrillin): I was unable to come up with a transformation that generated the error, but found a problem in the messages.properties file - The placeholder in the below message should be {0}, not {1} TeiidParser.teiid_version_failure=The given sql syntax is not supported by the Teiid client version {1} https://github.com/Teiid-Designer/teiid-designer/pull/339 > Query Parsing Error Missing Parameter > ------------------------------------- > > Key: TEIIDDES-2133 > URL: https://issues.jboss.org/browse/TEIIDDES-2133 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 8.5 > > > When entering an invalid query in the transformation editor, the error message is missing the Teiid version parameter: "The query is not parsable. > Error in parsing of sql - The given sql syntax is not supported by the Teiid client version {1}" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2133) Query Parsing Error Missing Parameter

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2133?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2133. ------------------------------------- Resolution: Done > Query Parsing Error Missing Parameter > ------------------------------------- > > Key: TEIIDDES-2133 > URL: https://issues.jboss.org/browse/TEIIDDES-2133 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 8.5 > > > When entering an invalid query in the transformation editor, the error message is missing the Teiid version parameter: "The query is not parsable. > Error in parsing of sql - The given sql syntax is not supported by the Teiid client version {1}" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2133) Query Parsing Error Missing Parameter

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2133?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2133: ----------------------------------------- I was unable to come up with a transformation that generated the error, but found a problem in the messages.properties file - The placeholder in the below message should be {0}, not {1} TeiidParser.teiid_version_failure=The given sql syntax is not supported by the Teiid client version {1} https://github.com/Teiid-Designer/teiid-designer/pull/339 > Query Parsing Error Missing Parameter > ------------------------------------- > > Key: TEIIDDES-2133 > URL: https://issues.jboss.org/browse/TEIIDDES-2133 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 8.5 > > > When entering an invalid query in the transformation editor, the error message is missing the Teiid version parameter: "The query is not parsable. > Error in parsing of sql - The given sql syntax is not supported by the Teiid client version {1}" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2133) Query Parsing Error Missing Parameter

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2133?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-2133: --------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) > Query Parsing Error Missing Parameter > ------------------------------------- > > Key: TEIIDDES-2133 > URL: https://issues.jboss.org/browse/TEIIDDES-2133 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 8.5 > > > When entering an invalid query in the transformation editor, the error message is missing the Teiid version parameter: "The query is not parsable. > Error in parsing of sql - The given sql syntax is not supported by the Teiid client version {1}" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2069) Improve Default Server naming and make it consistent

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2069?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2069. ------------------------------------- Resolution: Done Reworked the Default Teiid Instance section - changed title to Default Server, moved change button into toolbar. - Using separate Server status and Teiid status icons - Using JBoss server name to make consistent with server view Changed dialog wordings in several places - to make more consistent. Simplified the Change Default combo box selections - now using server names https://github.com/Teiid-Designer/teiid-designer/pull/338 > Improve Default Server naming and make it consistent > ---------------------------------------------------- > > Key: TEIIDDES-2069 > URL: https://issues.jboss.org/browse/TEIIDDES-2069 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: ServerDefaultView.png, SetDefaultServerDialog.png > > > We are inconsistent in the way we name/display the default teiid instances in designer. > We supply a 'Display Name' on the server teiid instance panel, but it is empty by default. So when you have multiple local JBoss servers (and dont supply a display name) they are all displayed as 'mm://localhost:9999' in the default server view. This is really confusing as to which instance you've selected as the default. > Also, in the 'Change Default Dialog'. The names in the dropdown get really long and ugly - especially if you provide a teiid instance name. See attached screenshot. > I'm thinking, just set a default for the teiid instance 'display name' initially. Either just use the JBoss server name or something based on it. Then use that name consistently in the Default server view and selection dialog. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-279) UUID values being created and stored in memory for XSD Schema elements.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-279?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-279. --------------------------------- > UUID values being created and stored in memory for XSD Schema elements. > ----------------------------------------------------------------------- > > Key: TEIIDDES-279 > URL: https://issues.jboss.org/browse/TEIIDDES-279 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Barry LaFond > > Noticed that adding XML Document models to VDB and saving created validation errors indicating the XML Doc elements contained href's with UUID's to XSD elements that did NOT have uuid's in stored/saved models. > Talked to John and we are currently still creating UUID's for All schema model objects but just not "saving" them to file system. We need to fix this, of course. > The simple use case is to create take any Schema model and generate an XML Doc model from it and SAVE. The validation error won't show up unless you fix all errors (i.e. transformations) and add to a VDB and save, so there is probably a problem with Validation rules??? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-279) UUID values being created and stored in memory for XSD Schema elements.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-279?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-279. ----------------------------------- Resolution: Out of Date > UUID values being created and stored in memory for XSD Schema elements. > ----------------------------------------------------------------------- > > Key: TEIIDDES-279 > URL: https://issues.jboss.org/browse/TEIIDDES-279 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Barry LaFond > > Noticed that adding XML Document models to VDB and saving created validation errors indicating the XML Doc elements contained href's with UUID's to XSD elements that did NOT have uuid's in stored/saved models. > Talked to John and we are currently still creating UUID's for All schema model objects but just not "saving" them to file system. We need to fix this, of course. > The simple use case is to create take any Schema model and generate an XML Doc model from it and SAVE. The validation error won't show up unless you fix all errors (i.e. transformations) and add to a VDB and save, so there is probably a problem with Validation rules??? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2014