July 2014 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2198?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2198. ------------------------------------ Resolution: Done Done > 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 > Security Level: Public(Everyone can see) > Components: Transformations, Validation > Affects Versions: 8.3.2 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > > 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.6#6264)

11 years, 3 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2198?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2198: ---------------------------------------- tweaked T-form listener to invalidate a t-root when virtual parameter changed. Fixed in 8.5.x and master > 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 > Security Level: Public(Everyone can see) > Components: Transformations, Validation > Affects Versions: 8.3.2 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > > 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.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2165) User can not use '.' for VDB name in order to version the VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2165?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2165: ---------------------------------------- I guess it comes down to what's a "version". We've already enabled setting the version in the vdb.xml (manifest). Does Teiid use this version? My understanding is that Teiid runtime does not support multiple versioned VBD's with the same name, so in essence, they do not support multiple versions. So Teiid runtime gets around it by supporting VDB's with '.' separator and a version #? Does Teiid runtime actually treat this as a Version or is it really just a different VDB name? > User can not use '.' for VDB name in order to version the VDB > ------------------------------------------------------------- > > Key: TEIIDDES-2165 > URL: https://issues.jboss.org/browse/TEIIDDES-2165 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5.1 > > > User can not use '.' for VDB name. > According to the Official document[1], user should be able to use '.' to specify the version for VDB. > [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir... > Version-Release number of selected component (if applicable): > Steps to Reproduce: > 1. Create a new VDB named "test1.1" > Actual results: > error occurs. Please check attached screenshot named vdb_versioning_error.png > Expected results: > User can use '.' for VDB name. > Additional info: > Teiid Designer 8.3.2.Final-v20140328-2123-B54 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2239) Spontaneous shutdown of designer

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-2239: -------------------------------------- Summary: Spontaneous shutdown of designer Key: TEIIDDES-2239 URL: https://issues.jboss.org/browse/TEIIDDES-2239 Project: Teiid Designer Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.5.1 Reporter: Tom Johnston Designer just shutdown.. (happens various times just had the time to log this particular one) java.lang.NullPointerException at org.eclipse.ui.internal.statushandlers.InternalDialog.refreshDialogSize(InternalDialog.java:384) at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:273) at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197) at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156) at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101) at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57) at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106) at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242) at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326) at org.eclipse.ui.internal.Workbench$3.eventLoopException(Workbench.java:491) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.handle(PartRenderingEngine.java:1134) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1124) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2224) web service returns 500 when concurrent access

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2224?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2224: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1101449|https://bugzilla.redhat.com/show_bug.cgi?id=1101449] from NEW to MODIFIED > web service returns 500 when concurrent access > ---------------------------------------------- > > Key: TEIIDDES-2224 > URL: https://issues.jboss.org/browse/TEIIDDES-2224 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services Support > Affects Versions: 8.5 > Reporter: Hisanobu Okuda > Assignee: Ted Jones > Fix For: 8.6, 8.5.1 > > Attachments: reproducer.tar.gz > > > Description of problem: > web service returns 500 when concurrent access. It works fine with a single access. > Version-Release number of selected component (if applicable): > How reproducible: > Please find the attached reproducer kit reproducer.tar.gz which contains > reproducer > ├── accounts.csv // data source > ├── command.log // test result > ├── SampleJDV.zip // project source code > ├── server.log // test result > ├── SOAP_TEST2.jmx // config file for JMeter > ├── WSTest.vdb // VDB which contains web service model > └── WSTest.war // generated JBossWS-CXF War > Steps to Reproduce: > 0. add user/user in teiid-security-users.properties > 1. add datasource in standalone.xml > <datasource jndi-name="java:/WSTest" pool-name="WSTest" enabled="true"> > <connection-url>jdbc:teiid:WSTest</connection-url> > <driver>teiid</driver> > <pool> > <min-pool-size>100</min-pool-size> > <max-pool-size>100</max-pool-size> > <use-strict-min>true</use-strict-min> > </pool> > <security> > <user-name>user</user-name> > <password>user</password> > </security> > 2. unjar WSTest.vdb, change the path to accounts.csv in SampleJDV/sandbox/WSTest_Source.xmi, rejar WSTest.vdb. > 3. deploy WSTest.vdb > 4. deploy WSTest.war > 5. run jmeter, and open SOAP_TEST2.jmx > 6. run test on jmeter > Actual results: > Expected results: > Additional info: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2165) User can not use '.' for VDB name in order to version the VDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2165?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2165: --------------------------------------- Is this being fixed in 8.5.x? > User can not use '.' for VDB name in order to version the VDB > ------------------------------------------------------------- > > Key: TEIIDDES-2165 > URL: https://issues.jboss.org/browse/TEIIDDES-2165 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5.1 > > > User can not use '.' for VDB name. > According to the Official document[1], user should be able to use '.' to specify the version for VDB. > [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir... > Version-Release number of selected component (if applicable): > Steps to Reproduce: > 1. Create a new VDB named "test1.1" > Actual results: > error occurs. Please check attached screenshot named vdb_versioning_error.png > Expected results: > User can use '.' for VDB name. > Additional info: > Teiid Designer 8.3.2.Final-v20140328-2123-B54 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2153) Create relational model from SOAP WS with Service Mode MESSAGE can't be finished

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2153?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2153: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1096741|https://bugzilla.redhat.com/show_bug.cgi?id=1096741] from NEW to MODIFIED > Create relational model from SOAP WS with Service Mode MESSAGE can't be finished > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2153 > URL: https://issues.jboss.org/browse/TEIIDDES-2153 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.5, 8.3.4 > > Attachments: bug.png > > > Description of problem: > When I select Service Mode MESSAGE during the proccess of creating the relational model from SOAP WS it gets stuck and can't be finished. > How reproducible: > 1. Guides -> Generate relational model from WSDL > 2. Select some Connection Profile and some Operations > 3. Select Service Mode: MESSAGE, click Next> > 4. Leave default settings and click Next> again > 5. Nothing changes on the window only new error message in the top section of the window is displayed "No columns are defined for the response procedure result set for the operation: ... " and both buttons "Next>" and "Finish" are disabled > [see attachment] > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2151) Create relational model from WS (SOAP) using default procedures generates both models in one subdirectory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2151?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2151: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1096255|https://bugzilla.redhat.com/show_bug.cgi?id=1096255] from NEW to MODIFIED > Create relational model from WS (SOAP) using default procedures generates both models in one subdirectory > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2151 > URL: https://issues.jboss.org/browse/TEIIDDES-2151 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.3.4, 8.6, 8.5.1 > > Attachments: bug.png, screen1.png, wsdl.xml > > > Steps to Reproduce: > 1. Generate relational model from WS (SOAP) > 2. Select connection profile and some operation click Next> > 3. Select different project subdirectories for source and view model. > 4. In the Procedure generation section select radio option "Default procedures" and click Finish > 5. Both models are saved in the same subdirectory > With User-specified procedures all works OK > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2126?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2126: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1089875|https://bugzilla.redhat.com/show_bug.cgi?id=1089875] from NEW to CLOSED > 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 > Security Level: Public(Everyone can see) > 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.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2139) 2 Connections to same VDB in JBDS seem to share one password

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2139?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2139: ----------------------------------- Assignee: Paul Richardson (was: Mark Drilling) > 2 Connections to same VDB in JBDS seem to share one password > ------------------------------------------------------------ > > Key: TEIIDDES-2139 > URL: https://issues.jboss.org/browse/TEIIDDES-2139 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.3.4, 8.6, 8.5.1 > > > Description of problem: > Connections to same VDB seem to share one password. > I have 2 connections to one VDB and each connection should use different username and password(one with longer password and the other one with shorter). > When I save the password in configuration of the first connection, the second connection doesn't work. In the preferences of the second one is obvious that the saved password is too long to be right, after retyping the password this connection works, but the other one doesn't... > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 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 July 2014