November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Van Halbert (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1160: ---------------------------------- Priority: Critical (was: Major) > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > Priority: Critical > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3612 to TEIIDDES-1160: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1160 (was: SOA-3612) Affects Version/s: 7.4.2 (was: JBDS) (was: 5.2.0 GA) Component/s: Import/Export (was: EDS) Security: (was: Public) > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1152) Model Extension Definition (MED) Management Dialog Should Allow Model MEDs To Be Updated From Registry And Saved To Workspace

by Dan Florian (Created) (JIRA)

Model Extension Definition (MED) Management Dialog Should Allow Model MEDs To Be Updated From Registry And Saved To Workspace ----------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1152 URL: https://issues.jboss.org/browse/TEIIDDES-1152 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 The MED management dialog needs to show when model MEDs are either (1) not registered, or (2) are of a different version than the one in the registry. For the former case, the dialog should offer to save that MED in the workspace. For the latter case, the dialog should ask if the MED in the model should be updated to the registry version. -- 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

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1158) CLONE - Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by Steven Hawkins (Created) (JIRA)

CLONE - Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-1158 URL: https://issues.jboss.org/browse/TEIIDDES-1158 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.2, 7.3, 7.4, 7.5 Environment: JBoss Developer Studio 4.0 JBoss Developer Studio 4.1 Reporter: Johnathon Lee /*+ cache */ CREATE VIRTUAL PROCEDURE SELECT 'winning'; BEGIN END The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: this.sqlText = sqlDisplayNode.toDisplayString(); -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1147) Create Model Extension Definition Resource Validation Rules

by Dan Florian (Created) (JIRA)

Create Model Extension Definition Resource Validation Rules ----------------------------------------------------------- Key: TEIIDDES-1147 URL: https://issues.jboss.org/browse/TEIIDDES-1147 Project: Teiid Designer Issue Type: Task Components: Validation Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 Validation rules need to be created for when MEDs are saved. These rules will run when a build is run. We may need to create our own builder also. Validation rules should exist for at least the following: 1. when a model contains a different version of a MED than the one in the registry (high priority) 2. when a model contains a MED that is not found in the registry (high priority) 3. move current problem marker creation out of MED Editor and into a validation rule (high priority) 3. when a model object has an extension property but does not have the MED stored in its model (low priority) 4. when a model object has an extension property that is not found in the corresponding MED (low priority) 5. any others that are needed -- 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

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1140) Model Extension Definition Validation Should Report All Validation Messages And Stop Stop When It Finds The First Error

by Dan Florian (Created) (JIRA)

Model Extension Definition Validation Should Report All Validation Messages And Stop Stop When It Finds The First Error ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1140 URL: https://issues.jboss.org/browse/TEIIDDES-1140 Project: Teiid Designer Issue Type: Task Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 8.0 The validation being done associated with MEDs is being done by the ModelExtensionDefinitionValidator. While the validator does perform validation in lots of different areas and reports issues in each of those areas, it does not report multiple issues within the same category. For instance, when the validator looks at all property definitions, it will only report the first error it finds in any of the property definitions. It should report all the problems from all the property definitions. Need to update ValidationStatus class so that it can contain multiple statuses and update the validator to report multiple statuses. -- 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

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1045) Teiid JDBC metadata import wizard does not show database schema checked when importing from MySQL

by Mark Drilling (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1045?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1045: ----------------------------------------- This is working ok for me in JBDS 4.1.0GA as well as current branch. I'll ask Ken Johnson for more info, since he originally logged the issue. > Teiid JDBC metadata import wizard does not show database schema checked when importing from MySQL > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1045 > URL: https://issues.jboss.org/browse/TEIIDDES-1045 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.5 > Environment: RHEL 6, x84_64, OpenJDK 1.6 > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 7.6 > > > When importing JDBC metadata from a MySQL database, the connection profile specifies the database name (schema). However, on the Select Database Objects page (4th page), the database name specified in the connection URL is not automatically selected. The user must select the correct schema to proceed. It should default to the database specified in the connection profile. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1055) Table Editor doesnt update correctly for extension property ADD / REMOVE

by Mark Drilling (JIRA)

Table Editor doesnt update correctly for extension property ADD / REMOVE ------------------------------------------------------------------------ Key: TEIIDDES-1055 URL: https://issues.jboss.org/browse/TEIIDDES-1055 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 7.6 Attachments: RestBooksToo.xmi The table editor doesnt refresh in all situations where extension properties are added or removed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1151) Model Extension Definition Version History Should Be Persisted Along With The Registry

by Dan Florian (Created) (JIRA)

Model Extension Definition Version History Should Be Persisted Along With The Registry -------------------------------------------------------------------------------------- Key: TEIIDDES-1151 URL: https://issues.jboss.org/browse/TEIIDDES-1151 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 8.0 Persisting a version history of MED stored in the registry will help determine if the MED the user wants to register is newer or older than the one in already in the registry. The MED business object does have a version number but there are problems with using that to determine if one MED is newer/older than another MED. For instance, in a multi-user environment the same MED could be updated by different users. Each user could end up with a MED with the same version but with different content. And those MEDs could end up in the hands of other users who could also create new versions. Of course an enterprise could be diligent about controlling MED versioning using their own version-control system and possibly get around this issue. With that said, persisting a MED version history by using something like a checksum/sha-1 would remove the problems associated with relying on the version number at least for a workspace. We might also look at writing an exporter/importer to export the version history and then import into another workspace. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1150) Model Extension Definition Problem Markers For Models Should Support Quick Fix

by Dan Florian (Created) (JIRA)

Model Extension Definition Problem Markers For Models Should Support Quick Fix ------------------------------------------------------------------------------ Key: TEIIDDES-1150 URL: https://issues.jboss.org/browse/TEIIDDES-1150 Project: Teiid Designer Issue Type: Enhancement Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 8.0 Model problem markers related to MEDs should have a quick fix option. Currently there are 2 MED problem markers: (1) MED found in model is not registry. Quick fix should offer to save that MED to a file in the workspace. (2) MED found in model is different than the same MED in the registry. Quick fix should offer to update the model to the registry copy of the MED. I'm thinking that the quick fix in each case would not offer to fix all markers of the same error at the same time. However, the quick fix for (1) could offer to save all MEDs in a common directory. And the quick fix for (2) could offer to update all models to the MED version. These options might be nice and deserve more thought. -- 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

14 years, 5 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 November 2011