May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-583) AccessNode is not passing connectorbindingid in multisource scenario

by Steven Hawkins (JIRA)

AccessNode is not passing connectorbindingid in multisource scenario -------------------------------------------------------------------- Key: TEIID-583 URL: https://jira.jboss.org/jira/browse/TEIID-583 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The connectorbindingid is set by the multisourceplantoprocessconverter and needs to be sent to the datamanager by the accessnode. -- 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-171) Add SQLXML Function for Extract()

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-171: --------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) Complexity: Medium (was: Low) > 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.1.1 > > > 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-561) Having multiple copies of "configuration.xml" is error prone

by Ramesh Reddy (JIRA)

Having multiple copies of "configuration.xml" is error prone ------------------------------------------------------------ Key: TEIID-561 URL: https://jira.jboss.org/jira/browse/TEIID-561 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Fix For: 6.1.0 Currently Teiid has two different configuration.xml files, one for the server and one for Embedded. The server xml contains more information than the embedded and it partially is auto generated based on the cdk files of the connectors. The Embedded does not have this feature, and needs to be modified manually. these both should be combined to have a single "configuration" file. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-581) Embedded is creating a uber jar of the classes in the Engine side, this is no longer necessary

by Ramesh Reddy (JIRA)

Embedded is creating a uber jar of the classes in the Engine side, this is no longer necessary ---------------------------------------------------------------------------------------------- Key: TEIID-581 URL: https://jira.jboss.org/jira/browse/TEIID-581 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 Currently embedded kit builds the uber jar of all the query side modules. This is originally designed to keep all the classes under one jar, so that it is easier to deploy in the "classpath" profile. However, this not provided any benefits and obscured the fact that what modules were actually part of Embedded and their versions. Also, this required two separate sets of kitting sub-modules, one to pull the project jars together and another to pull their dependencies together. These should be one. The only side effect of this is, Embedded will now have more jar files in "lib" directory. If tooling is accessing this file directory directly it should be replaced with all "teiid-xxx.jar" files in the "lib" directory. "lib" is considered internal, so no tooling or deployment should be explicitly copying or having class path entries into this at all. -- 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] Created: (TEIID-528) java.lang.NumberFormatException thrown by LogConfigurationProvider due to missing properties in Configuration

by Van Halbert (JIRA)

java.lang.NumberFormatException thrown by LogConfigurationProvider due to missing properties in Configuration ------------------------------------------------------------------------------------------------------------- Key: TEIID-528 URL: https://jira.jboss.org/jira/browse/TEIID-528 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert The NumberFormatException is being thrown because the metamatrix.log property does not exist in the Configuration object. This is a newly exposed issue due to the system properties in the config.xml were removed and were relying on the Configuration component type to provide the defaults. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-571) Need new method to expose ConnectorBinding for Configuring

by Van Halbert (JIRA)

Need new method to expose ConnectorBinding for Configuring ---------------------------------------------------------- Key: TEIID-571 URL: https://jira.jboss.org/jira/browse/TEIID-571 Project: Teiid Issue Type: Feature Request Components: AdminApi, Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Need new method to expose ConnectorBindings for Configuring. The current methods expose the bindings in the context of the host and vm, which is used for monitoring. -- 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-579) NPE is being thrown in ConnectorManager trying to get the status for a connector that couldn't start (bad classpath)

by Van Halbert (JIRA)

NPE is being thrown in ConnectorManager trying to get the status for a connector that couldn't start (bad classpath) -------------------------------------------------------------------------------------------------------------------- Key: TEIID-579 URL: https://jira.jboss.org/jira/browse/TEIID-579 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert May 12, 2009 14:25:10.881 [ServiceMonitoringThread|0] INFO <CONFIG|0> Data source is now unavailable for connector binding ID Bad Connector Binding<myhost|MMProcess|1205>. State changed to "Data Source Unavailable". Exception in thread "ServiceMonitoringThread" java.lang.NullPointerException at org.teiid.dqp.internal.datamgr.impl.ConnectorManager.getStatus(ConnectorManager.java:279) at com.metamatrix.server.connector.service.ConnectorService.checkState(ConnectorService.java:359) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.metamatrix.platform.registry.ServiceRegistryBinding$StateAwareProxy.invoke(ServiceRegistryBinding.java:60) at $Proxy34.checkState(Unknown Source) at com.metamatrix.platform.registry.ProcessMonitor$2.run(ProcessMonitor.java:125) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-522) JDBC DatabaseMetadata methods do not accept empty string as catalog name

by Greg Haber (JIRA)

JDBC DatabaseMetadata methods do not accept empty string as catalog name ------------------------------------------------------------------------- Key: TEIID-522 URL: https://jira.jboss.org/jira/browse/TEIID-522 Project: Teiid Issue Type: Bug Components: JDBC Driver Environment: http://anonsvn.jboss.org/repos/teiid/trunk/client-jdbc/src/main/java/com/... rev 809 Reporter: Greg Haber Assignee: Steven Hawkins This is related to internal support ticket I-T #212065 (which was against MetaMatrix 5.5SP2). To resolve that ticket (where a third party software package expected different behavior from the MetaMatrix JDBC driver than it actually had), we made three changes: 1) DatabaseMetaData.supportsSchemaInDataManipulation() was changed to return true (which is correct) - looks like this change was also brought over to Teiid 2) DatabaseMetaData.supportsCatalogInDataManipulation() was changed to return the value of the boolean driver property "supportsCatalog". This change didn't come over to Teiid (in Teiid this method always returns "false"). I'm fine with the current Teiid behavior, since we don't have a notion of catalog, so really "false" is the correct response here. 3) The DatabaseMetaData methods getColumns, getExportedKeys, getImportedKeys, getIndexInfo, getPrimaryKeys, getProcedureColumns, getProcedures, and getTables all have a parameter for catalog name. In the current Teiid implementation of MMDatabaseMetaData, if catalog is non-null an empty response is returned. This is actually incorrect behavior according to both 1.5 and 1.6 javadoc - see http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getT... where it says: catalog - a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog; null means that the catalog name should not be used to narrow the search So, since Teiid does not have the notion of a catalog, it should accept either null or the empty string as valid values for the catalog parameter. In the MMx 5.5.x code base, all of these methods were changed to only return empty responses if catalog was non-null, and also was not the empty string: if ((catalog != null) && (catalog.length() > 0)) { This same change should be made to Teiid. -- 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] Updated: (TEIID-75) SqlQueryWebService WSDL updates

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-75?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-75: -------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) > SqlQueryWebService WSDL updates > ------------------------------- > > Key: TEIID-75 > URL: https://jira.jboss.org/jira/browse/TEIID-75 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.1.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The WSDL is not WS-I Compliant and it needs to have operations removed per FEDERATE-8. See also tracker defect 25075 -- 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] 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: -------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) > 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, XML Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.1.1 > > > 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009