April 2010 - teiid-issues - Jboss List Archives

[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: 7.1 (was: 7.0) Priority: Critical (was: Blocker) Pushing to 7.1 and reducing the priority on this to critical. There are new schools thought to use tools like http://retroweaver.sourceforge.net/ to achieve the similar effect. This needs to be investigated and tested if the above approach is not taken. > 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: 8.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 7.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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-678) Document/test Alternative Means to Acheive Current XML Document Scenarios

by Ted Jones (JIRA)

Document/test Alternative Means to Acheive Current XML Document Scenarios ------------------------------------------------------------------------- Key: TEIID-678 URL: https://jira.jboss.org/jira/browse/TEIID-678 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.2.0 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around" 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure 3. Send an input document, produce and output document -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-675) Document/test a Means of Bottom-up Web Services in Teiid

by Ted Jones (JIRA)

Document/test a Means of Bottom-up Web Services in Teiid -------------------------------------------------------- Key: TEIID-675 URL: https://jira.jboss.org/jira/browse/TEIID-675 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Ted Jones 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-674) Document/test a Means of Top-down WSDL Consumption

by Ted Jones (JIRA)

Document/test a Means of Top-down WSDL Consumption -------------------------------------------------- Key: TEIID-674 URL: https://jira.jboss.org/jira/browse/TEIID-674 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 6.1.0 Reporter: Ted Jones 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

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1034) Convert Legacy Web Services to CXF

by Ted Jones (JIRA)

Convert Legacy Web Services to CXF ---------------------------------- Key: TEIID-1034 URL: https://jira.jboss.org/jira/browse/TEIID-1034 Project: Teiid Issue Type: Task Components: SOAP Services Affects Versions: 6.2.0 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.0 Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-208) LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-208?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-208. -------------------------------- Resolution: Out of Date With the JCA connectors this method of checking the connector alive status is no longer applicable. JOPR based tools already provide a way to show if a connection factory is alive or not. > LDAP Connector should implement Connection.isAlive(), in order to properly report connection status when monitored > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-208 > URL: https://jira.jboss.org/jira/browse/TEIID-208 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 7.0 > > > Connection.isAlive is currently implemented to always return "true". This means that connection status is not accurately reflected in the Console, and connection monitoring is not useful. We should implement this method, which may also require establishing a connection in the pool upon startup. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-137) Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-137?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-137. -------------------------------- Resolution: Won't Fix Now that SOAP execution moved into its own module the dependency list on xml-http connectors is very minimal. With out lot re-factoring this can not be achieved. There is no compelling reason to do so. Suggested path in future is to move this connector functionality to a ESB based connector and remove this entirely. > Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector > ----------------------------------------------------------------------------------- > > Key: TEIID-137 > URL: https://jira.jboss.org/jira/browse/TEIID-137 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ramesh Reddy > Fix For: 7.0 > > > Need to remove the HTTPClient usage from the XML Connector and use the Axis client in the Common XML Connector to reduce download size -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Ramesh Reddy reassigned TEIID-143: ---------------------------------- Assignee: Ramesh Reddy > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/jira/browse/TEIID-143 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Ramesh Reddy > Fix For: 7.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-143. -------------------------------- Resolution: Done see issue TEIID-861 > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/jira/browse/TEIID-143 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Ramesh Reddy > Fix For: 7.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-138) Convert Common XML Connector to Axis2

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-138?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-138. -------------------------------- Resolution: Won't Fix Based on the changes from JCA project, the future direction for the XML connectors is to use "apache-cxf". Usage of "Axis2" will not be pursued. > Convert Common XML Connector to Axis2 > ------------------------------------- > > Key: TEIID-138 > URL: https://jira.jboss.org/jira/browse/TEIID-138 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ramesh Reddy > Fix For: 7.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

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010