June 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-78) Need to support SOAP 1.2 in next release across all web service implementations

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-78?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-78: -------------------------------- Component/s: (was: XML Connector) Fix Version/s: 6.2.0 (was: 6.1.1) > Need to support SOAP 1.2 in next release across all web service implementations > ------------------------------------------------------------------------------- > > Key: TEIID-78 > URL: https://jira.jboss.org/jira/browse/TEIID-78 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.2.0 > > > Defect Tracker #20946: This will involve changing our implementations over to use the new SOAP fault rules in the 1.2 release as far as i can tell. > We will also need to use the SOAP 1.2 namespaces in our SOAP messages in order to be compliant. > test -- 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

16 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-595?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-595: --------------------------------- Component/s: SOAP Services (was: Server) Fix Version/s: 6.2.0 (was: 6.1.1) > 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: SOAP Services > Affects Versions: 6.x > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.2.0 > > > 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-104) Connector development documentation out-of-date

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-104?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-104: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.1) > Connector development documentation out-of-date > ----------------------------------------------- > > Key: TEIID-104 > URL: https://jira.jboss.org/jira/browse/TEIID-104 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > The included diagrams and documentation are not up-to-date with the limit, intersect, and except features. Documentation needs to be added for GlobalCapabilitiesProvider 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-421) Membership Domain Provider reference still exists after Provider deleted

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-421?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-421. -------------------------------- Resolution: Deferred > Membership Domain Provider reference still exists after Provider deleted > ------------------------------------------------------------------------ > > Key: TEIID-421 > URL: https://jira.jboss.org/jira/browse/TEIID-421 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Assignee: Li Liang > Fix For: 6.1.1 > > > 1. Had two Membership Domain Providers in Console. > 2. Deleted 1 Provider. > 3. Exit Console > 4. Started Console > 5. Started to add more Admin Roles. > 6. The Select Group (Step 1) screen has a drop down for Domain. > 7. The drop down still shows the previously deleted Membership Domain Provider even though it doesn't exist. -- 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

16 years, 10 months

1
0
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.2.0 (was: 6.1.1) > 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.2.0 > > > 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-607) Connectors with invalid connection properties should show Source Unavailable at startup

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-607?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-607: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.1) > Connectors with invalid connection properties should show Source Unavailable at startup > --------------------------------------------------------------------------------------- > > Key: TEIID-607 > URL: https://jira.jboss.org/jira/browse/TEIID-607 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Environment: MMServer: Fedora 8 Kernel 2.6.26.6-49.fc8 > Connector: Oracle JDBC Connector > Reporter: Larry O'Leary > Fix For: 6.2.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > If invalid connection properties are used in a connector binding the connector status shows "Running" at startup of the connector. When the first query is executed against the MMSystem that needs this connector an exception is thrown indicating that the connector wasn't found. This is due to the connector state changing to "Data Source Unavailable". > Although this is the expected behavior it is very mis-leading to the administrator after creating/adding a new connector or bouncing the system. The MMConsole gives the appearance that everything is okay until users actually start running queries. > What should be occurring is the current behavior and if Data Source Monitoring is enabled on the connector we should then check the data source available during connector startup. In other words, start the monitor thread with a timer of 0 instead a timer of monitoring interval. The idea is to show the connector as "Data Source Unavailable" at connector startup if the source isn't can't be reached due to invalid connection properties. > TEST: > To test this issue you simply need to have a connector deployed to a running MMSystem and verify that it is actually starting correctly with correct properties (ie verify you can run queries using this connector). > Now, change the password on the connector to something that is invalid. Stop and then start the connector. The connector will show a "Running" state yet as soon as you execute the query the query will fail and the status of the connector will change to "Source Unavailable". > EXPECTED RESULT: > When you start a connector using an invalid password (or other connection type property like SID, DatabaseName, etc) the connector state should immediately reflect "Data Source Unavailable". -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-409) server port number should be checked for availability when creating a second mmprocess

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-409?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-409: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.1) > server port number should be checked for availability when creating a second mmprocess > -------------------------------------------------------------------------------------- > > Key: TEIID-409 > URL: https://jira.jboss.org/jira/browse/TEIID-409 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.x > Reporter: Marc Shirley > Fix For: 6.2.0 > > > Creating a second process on a server increments the port number by one from the primary process. This port number does not seem to be checked for availability, and so, if the second process's port is already in use, then status of the second process will be unreliable (it flickers between "Running" and "Not Started" states). One or more of the below actions should be taken: > 1) A check should be added to the process of adding a second process to detect whether a port is already in use. > 2) A KI entry should be made to cover the issue. > 3) Steps should be added to the Console User's Guide and/or Server Tuning Guide to advise the reader to make sure the port assigned to the second process is not in use by another application. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-171) Add SQLXML Function for Extract()

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-171: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.1) > Add SQLXML Function for Extract() > --------------------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > > We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-315) Add JDBC Connector developers guide

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-315?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-315: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.1) > Add JDBC Connector developers guide > ----------------------------------- > > Key: TEIID-315 > URL: https://jira.jboss.org/jira/browse/TEIID-315 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.2.0 > > -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-517) Deploying VDB attempts by Product Admin has unnecessary steps before advising user they are "not authorized"

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-517?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-517. -------------------------------- Resolution: Deferred > Deploying VDB attempts by Product Admin has unnecessary steps before advising user they are "not authorized" > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-517 > URL: https://jira.jboss.org/jira/browse/TEIID-517 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running Console and Windows server running MetaMatrix server > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.1.1 > > > ReadOnly Admin is not authorized to deploy VDBs and is presented all grayed out buttons on the Virtual Databases screen except for the Export button. > ProductAdmin is also not authrized to deploy VDBs but all the buttons on the Virtual Databases screen are activated and the user can go through several steps in the New Virtual Database Wizard before selecting the Finish button at which time they are informed: "The client is not authorized to attempt this operation". The ProductAdmin interface should be the same as the ReadOnly Admin since they are both not authorized to deploy VDBs. -- 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

16 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2009