September 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1830) When deleting a project from Teiid Designer the associated preview* files are not removed from the server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1830?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1830: ----------------------------------- Assignee: Mark Drilling (was: Steven Hawkins) > When deleting a project from Teiid Designer the associated preview* files are not removed from the server > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1830 > URL: https://issues.jboss.org/browse/TEIIDDES-1830 > Project: Teiid Designer > Issue Type: Bug > Environment: Eclipse Kepler w/ Teiid Designer 8.2, Mac Mountain Lion OS 10.8.4, Oracle Java 1.7.0_25, EAP 6.1, Teiid 8.4 components on EAP 6 > Reporter: Blaine Mincey > Assignee: Mark Drilling > Fix For: 8.2.x-prod-eds6.0 > > > I create a Teiid Model Project with a variety of virtual models. I will select to preview several different views which in turn deploys the PREVIEW* VDBs to EAP 6 while it is running. I then choose to delete my Teiid Model Project. Then, I stop my running EAP 6 server and restart. The PREVIEW* components are still deployed to the server. I was expecting all of these artifacts from my deleted project to be cleaned up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1855) WSDL import File not Found Exception

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1855?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1855. ------------------------------------- Resolution: Done Problem was occurring in WSDLSchemaExtractor.findSchema - the passed in file string contained 'file:' prefix. Removed 'file:' prior to creating the File resolved the issue. Pull request - https://github.com/Teiid-Designer/teiid-designer/pull/240 > WSDL import File not Found Exception > ------------------------------------ > > Key: TEIIDDES-1855 > URL: https://issues.jboss.org/browse/TEIIDDES-1855 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Environment: JBTIS 4.1.2 with Teiid Designer 8.2.0 final, JBDS 7.0.0.GA > Reporter: Lucie Fabrikova > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.2.x-prod-eds6.0 > > > Import via "WSDL File or URL >> Source and View Model (SOAP)" sets proper path to WSDL (imported from file system) in step "Web service connection properties" (label Connection URL or File Path). > In next step, "Web Service end point property" the path to WSDL is malformed and causes java.io.FileNotFoundException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1861: ----------------------------------- Fix Version/s: 8.2.x-prod-eds6.0 > Designer deletes data role "condition" information > -------------------------------------------------- > > Key: TEIIDDES-1861 > URL: https://issues.jboss.org/browse/TEIIDDES-1861 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 8.2 > Environment: Windows 7, Eclipse kepler. > Reporter: Pablo Navascues > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > Create a VDB > Create a source model by importing from JDBC > Add model to VDB > Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)" > Synchronize, save VBD. > Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml. > Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well. > This has happened more than once and to more than one developer in the team. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1861: -------------------------------------- Assignee: Barry LaFond > Designer deletes data role "condition" information > -------------------------------------------------- > > Key: TEIIDDES-1861 > URL: https://issues.jboss.org/browse/TEIIDDES-1861 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 8.2 > Environment: Windows 7, Eclipse kepler. > Reporter: Pablo Navascues > Assignee: Barry LaFond > > Create a VDB > Create a source model by importing from JDBC > Add model to VDB > Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)" > Synchronize, save VBD. > Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml. > Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well. > This has happened more than once and to more than one developer in the team. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1730: ----------------------------------- Fix Version/s: 8.2.x-prod-eds6.0 > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1730: ----------------------------------- Assignee: Barry LaFond (was: Paul Richardson) > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1730: ----------------------------------- Description: >From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. was:From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Paul Richardson > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. > Make sense to create a new CreateTeiidVdbDataSource Modeling action to handle this and make it show up in Model Explorer for VDB selection as well as in the Teiid Server tree for selected VDB. > Key to this will be to circumvent the standard Create Data Source wizard knowing that this is a TEIID type data source for a specific VDB and that we'll need to remove the Host/Port info from the properties list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1730) Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1730?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1730: ----------------------------------- Summary: Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer (was: When creating datasource for Teiid VDB, default to using local Teiid connection) > Add Create Teiid VDB Data Source action to VDB selection in Teiid server and explorer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1730 > URL: https://issues.jboss.org/browse/TEIIDDES-1730 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration, Usability > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Paul Richardson > > From a usability issue, it would good if the default Teiid URL defined in the datasource that is created on the server is for the local connection. IMO, majority of the time when a Teiid datasource is defined in the server if for a local connection to be used by web applications or integration with other components (i.e, ESB) that will access Teiid via JNDI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information

by Pablo Navascues (JIRA)

Pablo Navascues created TEIIDDES-1861: ----------------------------------------- Summary: Designer deletes data role "condition" information Key: TEIIDDES-1861 URL: https://issues.jboss.org/browse/TEIIDDES-1861 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration, VDB & Execution Affects Versions: 8.2 Environment: Windows 7, Eclipse kepler. Reporter: Pablo Navascues Create a VDB Create a source model by importing from JDBC Add model to VDB Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)" Synchronize, save VBD. Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml. Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well. This has happened more than once and to more than one developer in the team. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1457) ERROR: SYSADMIN.logMsg does not exist.

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1457?page=com.atlassian.jira.plu... ] Hisanobu Okuda updated TEIIDDES-1457: ------------------------------------- Attachment: test.zip model project to reproduce the issue > ERROR: SYSADMIN.logMsg does not exist. > -------------------------------------- > > Key: TEIIDDES-1457 > URL: https://issues.jboss.org/browse/TEIIDDES-1457 > Project: Teiid Designer > Issue Type: Bug > Components: Testing > Affects Versions: 7.7 > Environment: Windows 7 64 bits > Reporter: Mónica L.A. > Assignee: Paul Richardson > Fix For: 8.2.x-prod-eds6.0 > > Attachments: test.zip > > > I've just put different calls to SYSADMIN.logMsg to trace a procedure and when I save, the transformation editor show the message: ERROR: SYSADMIN.logMsg does not exist -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2013