June 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2200) In New VDB wizard, cant add model to VDB if its in a folder

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2200?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-2200: ------------------------------------ Fix Version/s: 8.5.1 (was: 8.5) > In New VDB wizard, cant add model to VDB if its in a folder > ----------------------------------------------------------- > > Key: TEIIDDES-2200 > URL: https://issues.jboss.org/browse/TEIIDDES-2200 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5.1 > > > Launch the New VDB wizard. Click Add button to add a source model to the VDB. > If the source model is within a folder in your workspace (eg sources), it's not available to select in the add dialog > Note - this only affects the New VDB wizard. If user has models under a folder, they can add them from the VDBEditor as a workaround. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2200) In New VDB wizard, cant add model to VDB if its in a folder

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2200?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-2200: ------------------------------------ Description: Launch the New VDB wizard. Click Add button to add a source model to the VDB. If the source model is within a folder in your workspace (eg sources), it's not available to select in the add dialog Note - this only affects the New VDB wizard. If user has models under a folder, they can add them from the VDBEditor as a workaround. was: Launch the New VDB wizard. Click Add button to add a source model to the VDB. If the source model is within a folder in your workspace (eg sources), it's not available to select in the add dialog Workaround Description: Add models from the VDB Editor > In New VDB wizard, cant add model to VDB if its in a folder > ----------------------------------------------------------- > > Key: TEIIDDES-2200 > URL: https://issues.jboss.org/browse/TEIIDDES-2200 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > > Launch the New VDB wizard. Click Add button to add a source model to the VDB. > If the source model is within a folder in your workspace (eg sources), it's not available to select in the add dialog > Note - this only affects the New VDB wizard. If user has models under a folder, they can add them from the VDBEditor as a workaround. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2200) In New VDB wizard, cant add model to VDB if its in a folder

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-2200: --------------------------------------- Summary: In New VDB wizard, cant add model to VDB if its in a folder Key: TEIIDDES-2200 URL: https://issues.jboss.org/browse/TEIIDDES-2200 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 8.5 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.5 Launch the New VDB wizard. Click Add button to add a source model to the VDB. If the source model is within a folder in your workspace (eg sources), it's not available to select in the add dialog -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2199) Designer deletes materialization setting in transformation Editor

by Jason Marley (JIRA)

Jason Marley created TEIIDDES-2199: -------------------------------------- Summary: Designer deletes materialization setting in transformation Editor Key: TEIIDDES-2199 URL: https://issues.jboss.org/browse/TEIIDDES-2199 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.3.2 Environment: fedora 19, Red Hat Data Virtualization 6, JBDS 7.1.1.GA Reporter: Jason Marley In transformation editor and add caching comment /*+ cache(ttl:300000) */, if there is a space before + and the beginning of comment, upon save designer deletes the line. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2198) Virtual procedure transformation not revalidated after changing parameter datatype

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2198?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2198: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1105117 > Virtual procedure transformation not revalidated after changing parameter datatype > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2198 > URL: https://issues.jboss.org/browse/TEIIDDES-2198 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations, Validation > Affects Versions: 8.3.2 > Reporter: Andrej Šmigala > > Changing the datatype of a virtual procedure parameter does not trigger revalidation. This means that errors caused by trying to convert the parameter to an incompatible datatype in the transformation do not disappear after fixing the datatype, and conversely, changing the datatype does not trigger validation errors when the new datatype is incompatible. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2198) Virtual procedure transformation not revalidated after changing parameter datatype

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2198: ---------------------------------------- Summary: Virtual procedure transformation not revalidated after changing parameter datatype Key: TEIIDDES-2198 URL: https://issues.jboss.org/browse/TEIIDDES-2198 Project: Teiid Designer Issue Type: Bug Components: Transformations, Validation Affects Versions: 8.3.2 Reporter: Andrej Šmigala Changing the datatype of a virtual procedure parameter does not trigger revalidation. This means that errors caused by trying to convert the parameter to an incompatible datatype in the transformation do not disappear after fixing the datatype, and conversely, changing the datatype does not trigger validation errors when the new datatype is incompatible. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2091) Allow selector to be used with fixed width

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2091?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2091: ---------------------------------------- See https://github.com/teiid/teiid/blob/master/engine/src/test/java/org/teiid... file with "testTestTableFixed" tests > Allow selector to be used with fixed width > ------------------------------------------ > > Key: TEIIDDES-2091 > URL: https://issues.jboss.org/browse/TEIIDDES-2091 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > > From TEIID-2898: To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. See the reference for more: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE > Also from TEIID-2896 fixed width parsing will now make an effort to parse lines that are too short, rather than immediately throwing an exception. If there is designer logic with that limitation, it should be lifted. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2091) Allow selector to be used with fixed width

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2091?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2091: ---------------------------------------- Can someone attach a sample data file and corresponding expected TEXTTABLE() function call? > Allow selector to be used with fixed width > ------------------------------------------ > > Key: TEIIDDES-2091 > URL: https://issues.jboss.org/browse/TEIIDDES-2091 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > > From TEIID-2898: To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. See the reference for more: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE > Also from TEIID-2896 fixed width parsing will now make an effort to parse lines that are too short, rather than immediately throwing an exception. If there is designer logic with that limitation, it should be lifted. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1243) When creating a web service model from WSDL, changing schema location to another project does not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1243?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1243: ---------------------------------------- 1) This wizard results in a WS model with a dependency to the generated XSD file 2) We're preventing any cross-project dependencies in Designer so the fix would be to prevent this by filtering the "..." location selection dialog 3) I verified that selecting a folder in the same project results in the XSD being created in the folder > When creating a web service model from WSDL, changing schema location to another project does not work > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1243 > URL: https://issues.jboss.org/browse/TEIIDDES-1243 > Project: Teiid Designer > Issue Type: Sub-task > Components: Modeling > Affects Versions: 7.4.2 > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > > Selections of target project in the New Model Wizard are not used when creating a Web Service Model. This originates with: https://issues.jboss.org/browse/JBEDSP-762 > 1. Right click on the project and select New -> Metadata Model. > 2. Create a file name for the new model. > 3. Choose the "Web Service" metamodel and make sure the "Virtual Model" model type is selected. > 4. Select the "Build from existing WSDL file(s)" model builder. > 5. Click "Next." > 6. Choose a WSDL. Click next, next, next. > 7. In Schema Workspace Location Selection, change the Folder to another project, click apply. > 8. Click "Next", and "Finish". > The XSD is still created in the same project, not in the one selected in step 7. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1243) When creating a web service model from WSDL, changing schema location to another project does not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1243?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1243: ----------------------------------- Fix Version/s: 8.6 8.5.1 (was: Future) > When creating a web service model from WSDL, changing schema location to another project does not work > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1243 > URL: https://issues.jboss.org/browse/TEIIDDES-1243 > Project: Teiid Designer > Issue Type: Sub-task > Components: Modeling > Affects Versions: 7.4.2 > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > > Selections of target project in the New Model Wizard are not used when creating a Web Service Model. This originates with: https://issues.jboss.org/browse/JBEDSP-762 > 1. Right click on the project and select New -> Metadata Model. > 2. Create a file name for the new model. > 3. Choose the "Web Service" metamodel and make sure the "Virtual Model" model type is selected. > 4. Select the "Build from existing WSDL file(s)" model builder. > 5. Click "Next." > 6. Choose a WSDL. Click next, next, next. > 7. In Schema Workspace Location Selection, change the Folder to another project, click apply. > 8. Click "Next", and "Finish". > The XSD is still created in the same project, not in the one selected in step 7. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2014