May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-603) New LDAP membership provider ignored by server

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-603?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-603: --------------------------------- Fix Version/s: 6.1.0 Complexity: Low Priority: Blocker (was: Major) > New LDAP membership provider ignored by server > ---------------------------------------------- > > Key: TEIID-603 > URL: https://jira.jboss.org/jira/browse/TEIID-603 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.1.0 > Environment: Fedora 10 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 6.1.0 > > > Using the Console and Server from May 13, 2009, I added a new LDAP membership provider. After bouncing he server, I tried to access the new provider from the Admin Roles page. The provider combo box was empty (in prior versions, the provider would be listed, even if it were incorrectly defined and inaccessible). > I checked the process log files and there is no mention of the provider. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-599) Missing parameter in validation of non-comparable type

by Steven Hawkins (JIRA)

Missing parameter in validation of non-comparable type ------------------------------------------------------ Key: TEIID-599 URL: https://jira.jboss.org/jira/browse/TEIID-599 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 The validationvisitor checks for non-comparable types should have a parameter to the i18n message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (TEIID-177) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-177?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-177: ------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) Moving the testing until Teiid have stable Server build > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-177 > URL: https://jira.jboss.org/jira/browse/TEIID-177 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 6.1.1 > > > The jdbc driver needs to support jdk 1.5 on the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-596) Support for partial results mode and warnings in web services

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-596?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-192 to TEIID-596: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-596 (was: JBEDSP-192) Component/s: Server (was: Server) Fix Version/s: 6.1.1 (was: PostWestport) > Support for partial results mode and warnings in web services > ------------------------------------------------------------- > > Key: TEIID-596 > URL: https://jira.jboss.org/jira/browse/TEIID-596 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Marc Shirley > Assignee: Ted Jones > Fix For: 6.1.1 > > > Partial results mode can be set manually by adding it to the WSDL URL, but this should be an option in the WSDL generation page to include the mode, and support for the SQLWarnings for partial results should be included along with the ability to set the mode in the WSDL generation page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-594) Update Web Services Security Documentation for Security Setup in setupmm

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-594?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-878 to TEIID-594: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-594 (was: JBEDSP-878) Component/s: Documentation (was: Documentation) Fix Version/s: 6.1.1 (was: 5.5.4) Affects Version/s: (was: 5.5.3) > Update Web Services Security Documentation for Security Setup in setupmm > ------------------------------------------------------------------------ > > Key: TEIID-594 > URL: https://jira.jboss.org/jira/browse/TEIID-594 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.1 > > > Web Services security mechanism can be set manually by editing the axis2.xml file or set using setupmm. The documentation only describes the manual process and should be updated to include setupmm. The manual process should probably be removed from the documentation since this prevents the web service security system variable from being updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-595) Add VDB version as attribute to definitions tag of MM WSDL

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-595?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-596 to TEIID-595: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-595 (was: JBEDSP-596) Component/s: Server (was: Server) Fix Version/s: 6.1.1 (was: Westport) Affects Version/s: 6.x (was: 5.5.3) > Add VDB version as attribute to definitions tag of MM WSDL > ---------------------------------------------------------- > > Key: TEIID-595 > URL: https://jira.jboss.org/jira/browse/TEIID-595 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.x > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.1 > > > Would be helpful to add the VDB version to WSDL of a Web Service VDB. We have the VDB name in the definitions tag so that seems like a logical place for the version as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-593) Remove WSDL User Setup Verbiage from MM Documentation

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-593?page=com.atlassian.jira.plug... ] Ramesh Reddy moved JBEDSP-785 to TEIID-593: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-593 (was: JBEDSP-785) Component/s: Documentation (was: Documentation) Fix Version/s: 6.1.1 (was: Westport) Affects Version/s: 6.0.0 (was: Westport) > Remove WSDL User Setup Verbiage from MM Documentation > ----------------------------------------------------- > > Key: TEIID-593 > URL: https://jira.jboss.org/jira/browse/TEIID-593 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.1 > > > The WSDL User will be handled behind the scenes in Westport. Need to remove all security related documentation re the WSDL user. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-479) Teiid embedded non-delegating classloader issues

by Steven Hawkins (JIRA)

Teiid embedded non-delegating classloader issues ------------------------------------------------ Key: TEIID-479 URL: https://jira.jboss.org/jira/browse/TEIID-479 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Ramesh Reddy Priority: Critical Fix For: 6.0.0 The non-delegating classloader for lib and patches entries will create problems if any of the jars duplicate classes from a higher level classloader - without overriding all of the referenced classes. See TEIIDDES-141 for a similar situation in a designer install. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-568) Appears that join criteria not always propagated to dependent side of join.

by Ken Johnson (JIRA)

Appears that join criteria not always propagated to dependent side of join. --------------------------------------------------------------------------- Key: TEIID-568 URL: https://jira.jboss.org/jira/browse/TEIID-568 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Environment: Teiid 6.0.0 (Apr 27). Running in JBoss AS 4.2.3 but also happens in Designer during Preview or SQL Execution. VDB and model project set attached. Reporter: Ken Johnson Assignee: Steven Hawkins Getting exception in Teiid that suggests join criteria is not being propagated to the dependent side of the join in this case. This same query and model set/VDB work correctly in MMX 5.5.3 but error in Teiid. All data sources, drivers are the same, running on the same physical system. The problematic model is ReportingSchema.xmiin VirtualQueryLayer. All three views therein have the problem. The exception below is generated from this query: select * from AllData_Flattened Exception: May 08, 2009 11:21:09.246 [QueryProcessorQueue0|0] ERROR <DQP|0> ############# PW EXITING on 00000000-0000-0001-0000-000000000001.0 - error occurred ########### [MetaMatrixComponentException] ERR.015.006.0033: Unable to evaluate Products_DS.products.productdata.ProductID: No value was available at com.metamatrix.query.eval.Evaluator.internalEvaluate(Evaluator.java:500) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:475) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:195) at com.metamatrix.query.eval.Evaluator.evaluateTVL(Evaluator.java:109) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:98) at com.metamatrix.query.processor.relational.JoinNode.matchesCriteria(JoinNode.java:290) at com.metamatrix.query.processor.relational.MergeJoinStrategy.nextTuple(MergeJoinStrategy.java:245) at com.metamatrix.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:183) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:269) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:213) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-566) Unable to delete a connector binding using the console

by Van Halbert (JIRA)

Unable to delete a connector binding using the console ------------------------------------------------------ Key: TEIID-566 URL: https://jira.jboss.org/jira/browse/TEIID-566 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Steven Hawkins Trying to delete a connector binding and nothing happens. Process log showed no errors, nor did the console log. The logic in the console was to not allow the binding deletion as long as the binding was deployed. And with the changes to the console to remove PSC's and Poduct Type usage, there's no way to "Undeploy" a binding, and therefore (my guess) is the binding can't be removed as long as there's a deployed component for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009