June 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1752) Creating a Teiid Connection for an 8.4 Server Fails Due to Wrong Version

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1752: ----------------------------------- Summary: Creating a Teiid Connection for an 8.4 Server Fails Due to Wrong Version Key: TEIIDDES-1752 URL: https://issues.jboss.org/browse/TEIIDDES-1752 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 8.2 Reporter: Ted Jones Priority: Blocker Fix For: 8.2 Trying to create a ds for a VDB on an 8.4 server fails since the connection info has 8.3.Final instead of 8.4. java.lang.IllegalStateException: No Teiid Driver (org.teiid.jdbc.TeiidDriver) available for version 8.3.0.Final at org.teiid.designer.core.ModelerCore.getTeiidDriver(ModelerCore.java:2156) at org.teiid.datatools.connectivity.TeiidJDBCConnection.createConnection(TeiidJDBCConnection.java:87) at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105) at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54) at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:73) at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:23) at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83) at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359) at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76) at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1548: -------------------------------------- Assignee: Barry LaFond > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.2 > > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. > {code:title=vdb.xml snippet} > <data-role name="base-role" any-authenticated="true"> > <description>Conditional access</description> > > <permission> > <resource-name>modelName.tblName</resource-name> > <condition constraint="false">column1=user()</condition> > </permission> > > </data-role> > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1548: ----------------------------------- Fix Version/s: 8.2 > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Fix For: 8.2 > > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. > {code:title=vdb.xml snippet} > <data-role name="base-role" any-authenticated="true"> > <description>Conditional access</description> > > <permission> > <resource-name>modelName.tblName</resource-name> > <condition constraint="false">column1=user()</condition> > </permission> > > </data-role> > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1548: ----------------------------------- Description: A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: <permission> <resource-name>...</resource-name> <condition>sql</condition> ... </permission> The sql should resolve against the resource specified, ideally designer would check that as well. See TEIID-2311 and the reference for how these conditions are applied. {code:title=vdb.xml snippet} <data-role name="base-role" any-authenticated="true"> <description>Conditional access</description> <permission> <resource-name>modelName.tblName</resource-name> <condition constraint="false">column1=user()</condition> </permission> </data-role> {code} was: A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: <permission> <resource-name>...</resource-name> <condition>sql</condition> ... </permission> The sql should resolve against the resource specified, ideally designer would check that as well. See TEIID-2311 and the reference for how these conditions are applied. > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. > {code:title=vdb.xml snippet} > <data-role name="base-role" any-authenticated="true"> > <description>Conditional access</description> > > <permission> > <resource-name>modelName.tblName</resource-name> > <condition constraint="false">column1=user()</condition> > </permission> > > </data-role> > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1672) Invalid procedure in relational view model refering to web service translator procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1672?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1672. ------------------------------------ Resolution: Rejected Use-case was in-complete and described results appeared to be normal (i.e. errors). > Invalid procedure in relational view model refering to web service translator procedure > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-1672 > URL: https://issues.jboss.org/browse/TEIIDDES-1672 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.1 > Environment: teiid designer 8.1.beta > JBDS 6.0.1.GA > Reporter: Lucie Fabrikova > > I created a relational view model with a procedure, which referenced (in transformation sql) web service translator procedures from another relational source model. In JBD6, the view model is set as invalid. Transformation is invalid with empty message, so is the Error log. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1678) Jboss as7 can not deploy VDB with Relational model (XML Format)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1678?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1678: ---------------------------------------- Not sure this test case was valid. The VDB had no JNDI name? > Jboss as7 can not deploy VDB with Relational model (XML Format) > ---------------------------------------------------------------- > > Key: TEIIDDES-1678 > URL: https://issues.jboss.org/browse/TEIIDDES-1678 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.1 > Environment: JBDS6.0.1.GA, teiid designer 8.1.beta, jboss as 7.1 > Reporter: Lucie Fabrikova > Attachments: YahooStocksXML.xml, YahooVDB.vdb > > > I created an empty relational source model: > - Import -> designer text file -> src or view models, option Relational Model (XML Format) > JNDI Name: none, translator: yahoo (previously installed as module to jboss as 7) > I added the model to a vdb and tried to deploy it: > Error log: > TEIID70006 {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL: Failed to process phase INSTALL of deployment \"YahooVDB.vdb\""}} > org.teiid.adminapi.AdminProcessingException: TEIID70006 {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"YahooVDB.vdb\".INSTALL: Failed to process phase INSTALL of deployment \"YahooVDB.vdb\""}} > at org.teiid.adminapi.AdminFactory$AdminImpl.execute(AdminFactory.java:439) > at org.teiid.adminapi.AdminFactory$AdminImpl.deploy(AdminFactory.java:695) > at org.teiid83.runtime.ExecutionAdmin.doDeployVdb(ExecutionAdmin.java:198) > at org.teiid83.runtime.ExecutionAdmin.deployVdb(ExecutionAdmin.java:176) > at org.teiid.designer.runtime.TeiidServer.deployVdb(TeiidServer.java:528) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:279) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:248) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1750) Deleting model object with closed editor results in ArrayIndexOutOfBounds exception

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1750?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1750: ---------------------------------------- If "Link with Editor" navigator button is OFF then this AIOOB will not occur. > Deleting model object with closed editor results in ArrayIndexOutOfBounds exception > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-1750 > URL: https://issues.jboss.org/browse/TEIIDDES-1750 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.2 > > > With no model editors open, select a Table in a model in the explorer and click DELETE key. > Results in: ava.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.core.refactor.ObjectDeleteCommand.getModelResource(ObjectDeleteCommand.java:184) > at org.teiid.designer.core.refactor.ObjectDeleteCommand.checkDependentResources(ObjectDeleteCommand.java:228) > at org.teiid.designer.core.refactor.ObjectDeleteCommand.execute(ObjectDeleteCommand.java:350) > at org.teiid.designer.ui.actions.workers.DeleteWorker$1.execute(DeleteWorker.java:206) > at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Looks like the action may be getting it's selection updated during the async process of opening the editor so the Model get's selected instead of the original table -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1748) Account for Data Source Type Names Change in Teiid 8.4

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1748?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1748: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/177 > Account for Data Source Type Names Change in Teiid 8.4 > ------------------------------------------------------ > > Key: TEIIDDES-1748 > URL: https://issues.jboss.org/browse/TEIIDDES-1748 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Ted Jones > Fix For: 8.2 > > > Teiid changed the data source source type names in 8.4 which prevents Designer from creating some data sources. > Prior to 8.4: [teiid-local, teiid-connector-file.rar, teiid, teiid-connector-salesforce.rar, teiid-connector-infinispan.rar, teiid-connector-ldap.rar, teiid-connector-ws.rar, teiid-connector-google.rar, h2] > 8.4: [teiid-local, teiid, google, ldap, infinispan, file, salesforce, mongodb, webservice, h2] > Need to account for this difference. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1748) Account for Data Source Type Names Change in Teiid 8.4

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1748?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1748. --------------------------------- Assignee: Ted Jones Resolution: Done > Account for Data Source Type Names Change in Teiid 8.4 > ------------------------------------------------------ > > Key: TEIIDDES-1748 > URL: https://issues.jboss.org/browse/TEIIDDES-1748 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > Teiid changed the data source source type names in 8.4 which prevents Designer from creating some data sources. > Prior to 8.4: [teiid-local, teiid-connector-file.rar, teiid, teiid-connector-salesforce.rar, teiid-connector-infinispan.rar, teiid-connector-ldap.rar, teiid-connector-ws.rar, teiid-connector-google.rar, h2] > 8.4: [teiid-local, teiid, google, ldap, infinispan, file, salesforce, mongodb, webservice, h2] > Need to account for this difference. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1748) Account for Data Source Type Names Change in Teiid 8.4

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1748?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1748: -------------------------------- Comment: was deleted (was: Changed to webservice, ldap, file, and salesforce for 8.4.x connections. ) > Account for Data Source Type Names Change in Teiid 8.4 > ------------------------------------------------------ > > Key: TEIIDDES-1748 > URL: https://issues.jboss.org/browse/TEIIDDES-1748 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Ted Jones > Fix For: 8.2 > > > Teiid changed the data source source type names in 8.4 which prevents Designer from creating some data sources. > Prior to 8.4: [teiid-local, teiid-connector-file.rar, teiid, teiid-connector-salesforce.rar, teiid-connector-infinispan.rar, teiid-connector-ldap.rar, teiid-connector-ws.rar, teiid-connector-google.rar, h2] > 8.4: [teiid-local, teiid, google, ldap, infinispan, file, salesforce, mongodb, webservice, h2] > Need to account for this difference. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2013