February 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2436: ----------------------------------- Attachment: JdbcImoprtObjectsPage_TEIIDDES_2436.patch > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Attachments: JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2436: ---------------------------------------- 2 Workaround options: * Run the JDBC Importer for a valid JDBC source first * When user reaches the *Select Database Objects* page, select the *Show All Schema* option * click *<Back* twice then re-select your VDB's connection profile and proceed with the import or * Exit Teiid Designer/Eclipse * On the file system, edit the *dialog_settings.xml* file located under your *workspace* folder at: *.metadata/.plugins/org.teiid.designer.ui* * You'll find one or more of these 3 dialog setting values: ** <item value="false" key="showAllSchemasValue"/> ** <item value="true" key="showSelectedSchemasValue"/> ** <item value="false" key="showFilteredSchemasValue"/> * Set *showSelectedSchemasValue* value to *false* * Set *showAllSchemasValue* value to *true* * save the file * Restart Eclipse and re-launch the JDBC import wizard > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2028: --------------------------------------------------- asmigala(a)redhat.com changed the Status of [bug 1056756|https://bugzilla.redhat.com/show_bug.cgi?id=1056756] from ON_QA to VERIFIED > Teiid tooling fails to create metamodel for web service > ------------------------------------------------------- > > Key: TEIIDDES-2028 > URL: https://issues.jboss.org/browse/TEIIDDES-2028 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: Future > > > Description of problem: > Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached. > I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard. > Version-Release number of selected component (if applicable): > JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2 > How reproducible: > Everytime > Steps to Reproduce: > 1. Create Teiid Model Project > 2. Import WSDL under schemas folder > 3. Use Teiid Metamodel wizard to consume WSDL > see BZ for attachments. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2436: ----------------------------------- Summary: StackOverflow Exception Importing VDB via JDBC Importer Key: TEIIDDES-2436 URL: https://issues.jboss.org/browse/TEIIDDES-2436 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 9.0.1 Reporter: Ted Jones Assignee: Barry LaFond Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: 1. Import a JDBC source (any source) a. On page 3, select "Show Selected Schemas". 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2435: ------------------------------------- Summary: [Usability] The default user when connecting to server should be blanked out Key: TEIIDDES-2435 URL: https://issues.jboss.org/browse/TEIIDDES-2435 Project: Teiid Designer Issue Type: Enhancement Components: Teiid Integration Affects Versions: 9.0.1 Reporter: Van Halbert Assignee: Barry LaFond In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000

by Jeff Bride (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ] Jeff Bride commented on TEIIDDES-2174: -------------------------------------- Thank you for fixing this ! Confirmed working in Teiid Designer 9.0.1.Final > Hard Coded teiid jdbc server port 31000 > --------------------------------------- > > Key: TEIIDDES-2174 > URL: https://issues.jboss.org/browse/TEIIDDES-2174 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3.2 > Reporter: Jason Marley > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.6.1, 9.0.1, 9.1 > > Attachments: teiid-instance-editor-page.png > > > There is no where to change the port the teiid server is talking with. I will provide a video to show. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2431) Designer generated REST WAR handles the LOBS incorrectly

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2431?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2431. ------------------------------------ Verified in 9.0.1 > Designer generated REST WAR handles the LOBS incorrectly > -------------------------------------------------------- > > Key: TEIIDDES-2431 > URL: https://issues.jboss.org/browse/TEIIDDES-2431 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Priority: Critical > Fix For: 9.0.1 > > > The REST war generated when dealing with XML, CLOBs and BLOBs materializes the content to a string before posting to a response. This can lead to OOM in the JVM. It needs to write the contents as a stream to HTTP Response object. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2392) Don't allow override name to be the same name as existing translator name

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2392?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2392: -------------------------------------- While it is now impossible to create an override that has the same name as the translator that is being overriden, it is still possible to create a translator override that has the same name as a *different* translator. > Don't allow override name to be the same name as existing translator name > ------------------------------------------------------------------------- > > Key: TEIIDDES-2392 > URL: https://issues.jboss.org/browse/TEIIDDES-2392 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.6.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1, 9.0.1 > > > When creating a translator override, the name of the override should not be able to be set to the name of an existing translator (or translator override). > In this case, the translator override was set to "teradata". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2230) Update 8.6.x Designer branch to build Teiid 8.7 version client from Teiid 8.7.x branch

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2230?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2230. ------------------------------------ > Update 8.6.x Designer branch to build Teiid 8.7 version client from Teiid 8.7.x branch > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-2230 > URL: https://issues.jboss.org/browse/TEIIDDES-2230 > Project: Teiid Designer > Issue Type: Task > Components: Build, Teiid Integration > Affects Versions: 8.5.1, 8.6.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.6.1, 9.0.1 > > > Teiid 8.6.x branches will need to target Teiid 8.7.x branch to pull appropriate client source code for future 8.5.x releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2403) Relax BIRT version range to 4.4.0 from 4.4.1

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2403?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2403. ------------------------------------ > Relax BIRT version range to 4.4.0 from 4.4.1 > -------------------------------------------- > > Key: TEIIDDES-2403 > URL: https://issues.jboss.org/browse/TEIIDDES-2403 > Project: Teiid Designer > Issue Type: Task > Components: Teiid Integration > Affects Versions: 9.0.1 > Reporter: Paul Leacu > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0, 9.0.1 > > > The JBT unified TP 4.41.0.Final pulls in BIRT 4.4.0. It can't pull in BIRT 4.4.1 until after SR1 goes final. The associated JBTIS/ JBDSIS TPs must back off to 4.4.0 (from 4.4.1) its BIRT plugins if we want to install into Eclipse SR0 cleanly or we will have to forge an Eclipse SR1 remediation dialog for it (messy). So - since JBTIS TP must go .Final before we can legally pull in a 4.4.1 Birt, please: > Update meta-data ranges and feature references of BIRT 4.4.1 to use/include 4.4.0. > Thanks! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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 2015