May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-576) When a property is optional, the multiplicity on the connector type needs to be set to "0..1", not "0"

by Van Halbert (JIRA)

When a property is optional, the multiplicity on the connector type needs to be set to "0..1", not "0" --------------------------------------------------------------------------------------------------------- Key: TEIID-576 URL: https://jira.jboss.org/jira/browse/TEIID-576 Project: Teiid Issue Type: Bug Components: JDBC Connector Reporter: Van Halbert Assignee: Steven Hawkins The jdbc connectors cannot have their username and passwords set in the console due to the multiplicity setting in the JDBC Connector type. The username and password (and possibliy others) have the multiplicity set to "0", thinking this meant optional. However, the correct setting should be "0..n", where n is the max number acceptable values (i.e., "0..1" in the case of username and paswordl). -- 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
2
0 / 0

[JBoss JIRA] Updated: (TEIID-575) MMx server should be started 'headless' to prevent AWT prompts

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-575?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-575: --------------------------------- Complexity: Low Priority: Minor (was: Major) There's no problem adding this to our vm startup command in the config. The workaround for now is to just have the customer add the entry to their startup command manually. > MMx server should be started 'headless' to prevent AWT prompts > -------------------------------------------------------------- > > Key: TEIID-575 > URL: https://jira.jboss.org/jira/browse/TEIID-575 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.1 > > > Per https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... customer request. > The JT400 JDBC driver (JTOpen) prompts the user with an AWT form when the credentials fail. When this happens, it blocks the MMx server thread until one remotes over to it graphically and enters the password. When one repeatedly ignores the prompt, typically DB2 disables the userid. This is time-consuming and it happens periodically. Although this is really JT400 braindamage, it points out that MMx appears not to be started in "headless" mode. To do this, do: > java -Djava.awt.headless=true > This should cause AWT prompts like this from JDBC drivers to go to the log as exceptions. See http://java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/ for more info. > If you could just enter this as a bug/feature request. -- 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-575) MMx server should be started 'headless' to prevent AWT prompts

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-575?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-1038 to TEIID-575: ---------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-575 (was: JBEDSP-1038) Component/s: Server (was: Server) Fix Version/s: 6.1.1 (was: Future Versions) > MMx server should be started 'headless' to prevent AWT prompts > -------------------------------------------------------------- > > Key: TEIID-575 > URL: https://jira.jboss.org/jira/browse/TEIID-575 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 6.1.1 > > > Per https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... customer request. > The JT400 JDBC driver (JTOpen) prompts the user with an AWT form when the credentials fail. When this happens, it blocks the MMx server thread until one remotes over to it graphically and enters the password. When one repeatedly ignores the prompt, typically DB2 disables the userid. This is time-consuming and it happens periodically. Although this is really JT400 braindamage, it points out that MMx appears not to be started in "headless" mode. To do this, do: > java -Djava.awt.headless=true > This should cause AWT prompts like this from JDBC drivers to go to the log as exceptions. See http://java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/ for more info. > If you could just enter this as a bug/feature request. -- 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-574) Remove the use of variablevalues on commands

by Steven Hawkins (JIRA)

Remove the use of variablevalues on commands -------------------------------------------- Key: TEIID-574 URL: https://jira.jboss.org/jira/browse/TEIID-574 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.1.0 Storing variable values is no longer needed, since it is only needed from a dynamic context which has access to the user command. -- 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] Resolved: (TEIID-105) MySQL capabilities should be made specific to version 4/5

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-105?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-105. ---------------------------------- Resolution: Done Added mysql support for bit operations and created a mysql 5 specific translator/capabilities. It looks like we need to add specific base version support to all of our connector template names i.e. "Oracle Connector" should really be "Oracle 9 Connector", etc. > MySQL capabilities should be made specific to version 4/5 > --------------------------------------------------------- > > Key: TEIID-105 > URL: https://jira.jboss.org/jira/browse/TEIID-105 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24746: The current mysql capabilities seem to have been written for version 5 (it initially included support for timestampdiff). The support for 4.x should be specifically refined or specifically removed from the docs. 4.x goes completely eol by the end of 2009, so it's unlikely many customers would care if this were done for 5.5.1. > see also http://www.mysql.com/company/legal/lifecycle/#calendar -- 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] Assigned: (TEIID-105) MySQL capabilities should be made specific to version 4/5

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-105?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-105: ------------------------------------ Assignee: Steven Hawkins > MySQL capabilities should be made specific to version 4/5 > --------------------------------------------------------- > > Key: TEIID-105 > URL: https://jira.jboss.org/jira/browse/TEIID-105 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24746: The current mysql capabilities seem to have been written for version 5 (it initially included support for timestampdiff). The support for 4.x should be specifically refined or specifically removed from the docs. 4.x goes completely eol by the end of 2009, so it's unlikely many customers would care if this were done for 5.5.1. > see also http://www.mysql.com/company/legal/lifecycle/#calendar -- 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-573) Embedded missing "Admin.vdb" file

by Ramesh Reddy (JIRA)

Embedded missing "Admin.vdb" file --------------------------------- Key: TEIID-573 URL: https://jira.jboss.org/jira/browse/TEIID-573 Project: Teiid Issue Type: Task Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 The embedded is missing the Admin.vdb file, which will be used to make connections to Embedded to make any configuration changes. -- 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-491) Cancelation of atomic requests should be based upon atomic requestid

by Steven Hawkins (JIRA)

Cancelation of atomic requests should be based upon atomic requestid -------------------------------------------------------------------- Key: TEIID-491 URL: https://jira.jboss.org/jira/browse/TEIID-491 Project: Teiid Issue Type: Quality Risk Components: AdminApi Affects Versions: 6.1.0 Reporter: Steven Hawkins Priority: Minor Fix For: 6.0.0 Atomic requests are currently canceled by node id, which is not unique. -- 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] Updated: (TEIID-400) SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-400?page=com.atlassian.jira.plug... ] John Doyle updated TEIID-400: ----------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) Affects Version/s: 6.0.0 (was: 6.1.1) > SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR > ----------------------------------------------------------------------------- > > Key: TEIID-400 > URL: https://jira.jboss.org/jira/browse/TEIID-400 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.1.1 > > > When executing a SOAP service and passing an empty SOAP body, the following exception is thrown. > org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-400) SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-400?page=com.atlassian.jira.plug... ] John Doyle updated TEIID-400: ----------------------------- Affects Version/s: 6.1.1 (was: 6.0.0) > SOAP Relational connector throws org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR > ----------------------------------------------------------------------------- > > Key: TEIID-400 > URL: https://jira.jboss.org/jira/browse/TEIID-400 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.1.1 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.1.0 > > > When executing a SOAP service and passing an empty SOAP body, the following exception is thrown. > org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009