January 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1286) Invalid Link in Teiid Developer Guide

by Darrin Mison (JIRA)

Invalid Link in Teiid Developer Guide ------------------------------------- Key: TEIID-1286 URL: https://jira.jboss.org/browse/TEIID-1286 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins Section 1.4. Other Teiid Development "You may change the security subsystem for custom authentication and authorization." The "security" link points to the same page as the link. The underlying XML here is: <para>You may change the <link linkend="custom_security">security</link> subsystem for custom authentication and authorization.</para> There is no element in this document with the id of "custom_security". Unfortunately jDocBook doesn't fail when it encounters invalid items like this, it this case it creates a link that points to the same page. I would guess this should be referring to the Teiid Security chapter of the Administrator Guide which does have the id of "custom_security" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1236) Provide sample DS.xml files for all the data sources that Teiid supports.

by Ramesh Reddy (JIRA)

Provide sample DS.xml files for all the data sources that Teiid supports. ------------------------------------------------------------------------- Key: TEIID-1236 URL: https://jira.jboss.org/browse/TEIID-1236 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.1.1 Currently there are no sample -ds.xml files defined any where to create a LDAP, or SalesForce. Also Text and web Services are there but in a sample example. It would be nice to have one set of examples as JBoss AS does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value

by Cristiano Nicolai (JIRA)

VDBMetaDataInstanceClassFactory is using old value -------------------------------------------------- Key: TEIID-1331 URL: https://jira.jboss.org/browse/TEIID-1331 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.2 Environment: JbossAS 5.1 Reporter: Cristiano Nicolai Assignee: Steven Hawkins When updating ManagementComponent values via ProfileService, VDBMetaDataInstanceClassFactory class is using ManagedProperty.getValue to retrieve the updated value instead of MetaValue value received parameter. The value returned by ManagedProperty.getValue is the actual one, not the new value that was submitted. Basically should use: MetaValueFactory.getInstance().unwrap(value); Instead of: MetaValueFactory.getInstance().unwrap(property.getValue()); In all properties manipulated by the setValue method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIID-1235) The bind address 0.0.0.0 is always resolving to localhost

by Ramesh Reddy (JIRA)

The bind address 0.0.0.0 is always resolving to localhost --------------------------------------------------------- Key: TEIID-1235 URL: https://jira.jboss.org/browse/TEIID-1235 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 When bind address 0.0.0.0 used the server should allow connection using any IP address on that box. Including 127.0.0.1 or any number static or dynamic ip for that server. JBoss AS connects correctly, it is issue with address binding for the Teiid socket connections (JDBC, ADMIN, ODBC) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-1355) adminshell.bat cannot read script from stdin

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1355?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1355. --------------------------------- > adminshell.bat cannot read script from stdin > -------------------------------------------- > > Key: TEIID-1355 > URL: https://issues.jboss.org/browse/TEIID-1355 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 7.1 > Environment: windows > Reporter: Aleksandar Kostadinov > Assignee: Ramesh Reddy > > On windows adminshell doesn't read script if supplied on stdin. It looks like it is reading from terminal (unlike adminshell on linux). I see that one can supply expression as first argument to adminshell but it seems to accept only a single expression and additionally complex expressions are a hell to escape properly. > Assuming adminshell is intended to be used for automating administrative tasks, it needs a straightforward way to execute scripts non-interactively so current behavior on windows needs to be fixed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1347) Configuration Update for Teiid Engine Should Look for compName Instead of Name

by Ted Jones (JIRA)

Configuration Update for Teiid Engine Should Look for compName Instead of Name -------------------------------------------------------------------------------- Key: TEIID-1347 URL: https://jira.jboss.org/browse/TEIID-1347 Project: Teiid Issue Type: Bug Components: Jopr Plugin Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 When updating properties of the Teiid engine in Admin Console I get an NPE. This is due to the service component name changing, which is a property that Teiid has no control over. The compName property of the the component is explicitly set on the component so the plugin code needs to look for that value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1256) Clear caches when VDB with same version re-deployed

by Ramesh Reddy (JIRA)

Clear caches when VDB with same version re-deployed --------------------------------------------------- Key: TEIID-1256 URL: https://jira.jboss.org/browse/TEIID-1256 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 When a VDB with same name and version is re-deployed, the new re-deployed VDB may have its metadata changed. In this case if Teiid has any PreparedPlanCache ResultSetCache they need to flushed for that VDB, otherwise it will produce wrong results. One issue is there could be active connections on VDB, those need to be terminated also. Based on how failover is configured they may re-connect on the next query automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1231) Model visibility should only refer to whether entries are in metadata

by Steve Hawkins (JIRA)

Model visibility should only refer to whether entries are in metadata --------------------------------------------------------------------- Key: TEIID-1231 URL: https://jira.jboss.org/browse/TEIID-1231 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Visibility should only apply to whether a table/model shows up in the system tables and should have nothing to do with whether it can be accessed. If a designer user wants to make a model non-accessable with the ease of the visibility mechansim, then they should create a data role ("default") that does not have permissions for model. Our roles would then need a boolean attribute (any-authenticated) to denote that any authenticated user has the role. Designer/JOPR will also need to add support for the "any-authenticated" attribute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-1353) Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1353?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1353. --------------------------------- > Intermittent, recurring problem with EDS adminshell - seeing NPE - with [org.jboss.resource.connectionmanager.NoTxConnectionManager] exception maybe 20% of the time > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1353 > URL: https://issues.jboss.org/browse/TEIID-1353 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Len DiMaggio > Priority: Minor > > Seeing this about one time in 5 performing a query and then disconnecting a JDBC and admin connection. Will attacher server.log and pointer to test code. > Logging this as a minor issue as there does not seem to be any functional impact, but the server.log message may concern users. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1238) WS Connector config/configname should not be specific to ws-security

by Steven Hawkins (JIRA)

WS Connector config/configname should not be specific to ws-security -------------------------------------------------------------------- Key: TEIID-1238 URL: https://jira.jboss.org/browse/TEIID-1238 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Since the WS Connector config/configname can utilize the CXF configuration for more than just ws-security (logging, hostname verification, etc.). The property names should not be specific to WSSecurity. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2011