June 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2982: ------------------------------------- Ok, then second one is good, do not have to invent another type called "IMPORTED". Also thinking what other things users would be interested in overriding? may be addition of properties, source info? > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2462) WS-Security payload flow through "ws" resource adapter

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2462?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2462: ------------------------------------ Is this now being tracked under TEIID-2869? > WS-Security payload flow through "ws" resource adapter > ------------------------------------------------------ > > Key: TEIID-2462 > URL: https://issues.jboss.org/browse/TEIID-2462 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: cxf, ws-security > Fix For: 8.4 > > > Currently only HTTPBasic security credentials flow through the web services resource adapter from the configured security domain, and authorized Subject. > It is important to device a mechanism to enable security credentials flow through web services resource adapter for purposes ws-security. The idea is based on the Subject making resource adapter calls, the credential payload needs to be converted into CXF configuration. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2462) WS-Security payload flow through "ws" resource adapter

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2462?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2462: ------------------------------------ What's the status of testing SAML based auth? > WS-Security payload flow through "ws" resource adapter > ------------------------------------------------------ > > Key: TEIID-2462 > URL: https://issues.jboss.org/browse/TEIID-2462 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: cxf, ws-security > Fix For: 8.4 > > > Currently only HTTPBasic security credentials flow through the web services resource adapter from the configured security domain, and authorized Subject. > It is important to device a mechanism to enable security credentials flow through web services resource adapter for purposes ws-security. The idea is based on the Subject making resource adapter calls, the credential payload needs to be converted into CXF configuration. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2982: --------------------------------------- Either of these would be in the importing vdb. > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1675) Add capability to insert/update/delete multi-value attributes in LDAP connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1675?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1675: --------------------------------------- What I would propose is supporting string arrays. An array could be used to represent any multi-valued attribute for read or write. Then for example with the ddl: {code}create foreign table mmx_groups (objectClass string[], DN string, name string options (nameinsource 'cn'), uniqueMember string[]) options (nameinsource 'ou=groups,dc=metamatrix,dc=com', updatable true){code} you could issue: {code}insert into mmx_groups (objectClass, DN, name, uniqueMember) values (('top', 'groupOfUniqueNames'), 'cn=a,ou=groups,dc=metamatrix,dc=com', 'a', ('cn=Sam Smith,ou=people,dc=metamatrix,dc=com',)){code} Here both objectClass and uniqueMember are arrays. > Add capability to insert/update/delete multi-value attributes in LDAP connector > ------------------------------------------------------------------------------- > > Key: TEIID-1675 > URL: https://issues.jboss.org/browse/TEIID-1675 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: LDAP Connector > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.9, Open To Community > > > Add ability to insert/update/delete multi-value attributes through the LDAP connector. For example, this would present the opportunity for maintaining group membership through modifying the list of member attribute values in an LDAP groupOfNames object. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3012) ModeShape requires to use 'JOIN' instead of ', ' when joining 2 tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3012?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3012. ----------------------------------- Fix Version/s: 8.8 (was: 8.9) Resolution: Done Applied Van's changes to 8.7.x and master. > ModeShape requires to use 'JOIN' instead of ',' when joining 2 tables > --------------------------------------------------------------------- > > Key: TEIID-3012 > URL: https://issues.jboss.org/browse/TEIID-3012 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Issuing either query: > SELECT c.jcr_name FROM relational_table AS t, relational_column AS c WHERE JCR.JCR_ISCHILDNODE(c.jcr_path, t.jcr_path) > SELECT c.jcr_name FROM relational_table AS t JOIN relational_column AS c ON JCR.JCR_ISCHILDNODE(c.jcr_path,t.jcr_path) > produces the following exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_1."jcr:name", g_1."jcr:path" FROM "relational:table" AS g_0, "relational:column" AS g_1 WHERE ISCHILDNODE(g_1, g_0)" is not well-formed: Unexpected token ',' at line 1, column 66 > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) > at org.modeshape.jdbc.delegate.LocalRepositoryDelegate.execute(LocalRepositoryDelegate.java:139) > at org.modeshape.jdbc.JcrStatement.execute(JcrStatement.java:429) > ... 15 more > And after a discussion with Randall, it seems ModeShape needs JOIN in the syntax, and not ',' to join the tables. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3012) ModeShape requires to use 'JOIN' instead of ', ' when joining 2 tables

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3012?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3012: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/263 (was: https://github.com/teiid/teiid/pull/262) > ModeShape requires to use 'JOIN' instead of ',' when joining 2 tables > --------------------------------------------------------------------- > > Key: TEIID-3012 > URL: https://issues.jboss.org/browse/TEIID-3012 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Issuing either query: > SELECT c.jcr_name FROM relational_table AS t, relational_column AS c WHERE JCR.JCR_ISCHILDNODE(c.jcr_path, t.jcr_path) > SELECT c.jcr_name FROM relational_table AS t JOIN relational_column AS c ON JCR.JCR_ISCHILDNODE(c.jcr_path,t.jcr_path) > produces the following exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_1."jcr:name", g_1."jcr:path" FROM "relational:table" AS g_0, "relational:column" AS g_1 WHERE ISCHILDNODE(g_1, g_0)" is not well-formed: Unexpected token ',' at line 1, column 66 > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) > at org.modeshape.jdbc.delegate.LocalRepositoryDelegate.execute(LocalRepositoryDelegate.java:139) > at org.modeshape.jdbc.JcrStatement.execute(JcrStatement.java:429) > ... 15 more > And after a discussion with Randall, it seems ModeShape needs JOIN in the syntax, and not ',' to join the tables. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2982: ------------------------------------- {code} <model name="x" type="IMPORTED" visible="false"> {code} is that re-declaration of model in the target VDB? > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3012) ModeShape requires to use 'JOIN' instead of ', ' when joining 2 tables

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3012?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3012: ------------------------------- Fix Version/s: 8.9 (was: 8.7) > ModeShape requires to use 'JOIN' instead of ',' when joining 2 tables > --------------------------------------------------------------------- > > Key: TEIID-3012 > URL: https://issues.jboss.org/browse/TEIID-3012 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Issuing either query: > SELECT c.jcr_name FROM relational_table AS t, relational_column AS c WHERE JCR.JCR_ISCHILDNODE(c.jcr_path, t.jcr_path) > SELECT c.jcr_name FROM relational_table AS t JOIN relational_column AS c ON JCR.JCR_ISCHILDNODE(c.jcr_path,t.jcr_path) > produces the following exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_1."jcr:name", g_1."jcr:path" FROM "relational:table" AS g_0, "relational:column" AS g_1 WHERE ISCHILDNODE(g_1, g_0)" is not well-formed: Unexpected token ',' at line 1, column 66 > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) > at org.modeshape.jdbc.delegate.LocalRepositoryDelegate.execute(LocalRepositoryDelegate.java:139) > at org.modeshape.jdbc.JcrStatement.execute(JcrStatement.java:429) > ... 15 more > And after a discussion with Randall, it seems ModeShape needs JOIN in the syntax, and not ',' to join the tables. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3012) ModeShape requires to use 'JOIN' instead of ', ' when joining 2 tables

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3012?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3012: ------------------------------- Fix Version/s: 8.7.1 8.7 > ModeShape requires to use 'JOIN' instead of ',' when joining 2 tables > --------------------------------------------------------------------- > > Key: TEIID-3012 > URL: https://issues.jboss.org/browse/TEIID-3012 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.4.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7, 8.7.1 > > > Issuing either query: > SELECT c.jcr_name FROM relational_table AS t, relational_column AS c WHERE JCR.JCR_ISCHILDNODE(c.jcr_path, t.jcr_path) > SELECT c.jcr_name FROM relational_table AS t JOIN relational_column AS c ON JCR.JCR_ISCHILDNODE(c.jcr_path,t.jcr_path) > produces the following exception: > Caused by: javax.jcr.query.InvalidQueryException: The JCR-SQL2 query "SELECT g_1."jcr:name", g_1."jcr:path" FROM "relational:table" AS g_0, "relational:column" AS g_1 WHERE ISCHILDNODE(g_1, g_0)" is not well-formed: Unexpected token ',' at line 1, column 66 > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:146) > at org.modeshape.jcr.JcrQueryManager.createQuery(JcrQueryManager.java:101) > at org.modeshape.jdbc.delegate.LocalRepositoryDelegate.execute(LocalRepositoryDelegate.java:139) > at org.modeshape.jdbc.JcrStatement.execute(JcrStatement.java:429) > ... 15 more > And after a discussion with Randall, it seems ModeShape needs JOIN in the syntax, and not ',' to join the tables. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2014