June 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-37) Parse function for XSD datatypes for Web service procedures

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-37?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-37. --------------------------------- Resolution: Deferred > Parse function for XSD datatypes for Web service procedures > ----------------------------------------------------------- > > Key: TEIID-37 > URL: https://jira.jboss.org/jira/browse/TEIID-37 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #22201: for Web Service procedures and other places where xml document values are incoming, a function such as: > parseXSDType(<string: raw value>, <string: xsdtype>) is needed to convert the raw value into the expected runtime type for the given xsdtype. This alleviates the need for embedding potentially problematic formatting strings into the transformations. > See the logic that was already added for the output side of xsd types for defect 20717. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-63) Recursion Editor RECORD Feature When Limit Exceeded Does Not Work

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-63?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-63. --------------------------------- Resolution: Deferred > Recursion Editor RECORD Feature When Limit Exceeded Does Not Work > ----------------------------------------------------------------- > > Key: TEIID-63 > URL: https://jira.jboss.org/jira/browse/TEIID-63 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Dan Florian > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24367: Could not find where this is recorded to. Looking in the process log on the server, Tomcat log, and Query Builder debug log. I could've missed 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-17) Root criteria with sibling roots

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-17?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-17. --------------------------------- Resolution: Deferred > Root criteria with sibling roots > -------------------------------- > > Key: TEIID-17 > URL: https://jira.jboss.org/jira/browse/TEIID-17 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24824: The concept of a root context is unclear when there are sibling root mapping classes. From a document perspective it would be best to apply root criteria across all sibling roots by applying the criteria logically at a common parent. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-42) Correlated subqueries in XML criteria

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-42?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-42. --------------------------------- Resolution: Deferred > Correlated subqueries in XML criteria > ------------------------------------- > > Key: TEIID-42 > URL: https://jira.jboss.org/jira/browse/TEIID-42 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24338: Correlated subqueries in xml criteria do not resolve correctly. The xml query resolver should be rewritten to be built upon the SimpleQueryResolver -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-369) Connector properties page should have a "Test" button to test connector

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-369?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-369. ---------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > Connector properties page should have a "Test" button to test connector > ----------------------------------------------------------------------- > > Key: TEIID-369 > URL: https://jira.jboss.org/jira/browse/TEIID-369 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: NA > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.x > > > The Connector properties/configuration page should have a button/option to test the connector. This will allow the user to verify the connector prior to deploying it to the server. On an existing connector it allows them to test the connector prior to applying the 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-371) System state should reflect the state and allow start/stop/restart of Membership Domains

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-371?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-371. ---------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > System state should reflect the state and allow start/stop/restart of Membership Domains > ---------------------------------------------------------------------------------------- > > Key: TEIID-371 > URL: https://jira.jboss.org/jira/browse/TEIID-371 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Environment: MMServer 5.5.3 EA5 > MMConsole 5.5.3 EA5 > Server: RHEL5 Kernel 2.6.18-53.1.14.el5 > Console: Fedora 8 Kernel 2.6.26.3-14.fc8 > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.3.0 > > > When modifying properties for a membership domain a dialog appears and tells you that changes will not take affect until the provider is restarted in the System State Panel. This does not appear possible and the only method is to bounce the system. > Also, in cases where a membership domain provider fails to start due to property errors or conflicts, there is no indication of this in the Console. > The System State panel should be updated to show status and allow restart of membership domain providers. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-368) System state should give state details

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-368?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-368. ---------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > System state should give state details > -------------------------------------- > > Key: TEIID-368 > URL: https://jira.jboss.org/jira/browse/TEIID-368 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Environment: N/A > Reporter: Larry O'Leary > Priority: Minor > Fix For: 6.x > > > The system state displayed in the Console (or via the Admin API) should allow for displaying individual state details. For example, if I have a connector with the state of "Failed Initialization" I should be able to see information about the reason and cause of that sate including state change information: > State: Failed Initialization > State changed at 1:52 PM CDT by loleary > Details: [MetaMatrix][Oracle JDBC Driver]Error establishing socket. Unknown host: <host> > or > State: Running > State changed at 1:53 PM CDT by loleary > Details: Service started > or > State: Stopped > State changed at 1:54 PM CDT by MetaMatrixAdmin > Details: Service stopped > or > State: Data Source Unavailable > State changed at 1:59 PM CDT by DataSourceMonitor > Details: [MetaMatrix][Oracle JDBC Driver]Connection refused > Basically this would require all service state changes to be accompanied by a meaningful state message. In the case of an exception or warning base cause of the exception should be indicated as a message (no stack traces as that is what the logs are for). For successful state changes this would be just an indication message to show a generic state detail like "Started", "Stopped", "Restarted", etc. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-367) Add a validation step to security provider definition.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-367?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-367. ---------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > Add a validation step to security provider definition. > ------------------------------------------------------ > > Key: TEIID-367 > URL: https://jira.jboss.org/jira/browse/TEIID-367 > Project: Teiid > Issue Type: Feature Request > Components: Console, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > It would be good for the MembershipDomain provider wizard to offer an optional validation step where an instance of the membership domain is created, initialized, and asked for the groups. Any errors would be shown in the wizard. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-278) Upgrade Axis2 to Axis2 1.4

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-278?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-278. ---------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > Upgrade Axis2 to Axis2 1.4 > -------------------------- > > Key: TEIID-278 > URL: https://jira.jboss.org/jira/browse/TEIID-278 > Project: Teiid > Issue Type: Task > Components: Console, XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.3.0 > > > Need to upgrade from Axis2 1.3 to Axis2 1.4 to take advantage of bug fixes and performance improvements. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-18) Confusing dialog about missing extension module when importing connector binding

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-18?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-18. --------------------------------- Resolution: Deferred Console is now defunct. Further integration with JOPR should be logged against 6.3 > Confusing dialog about missing extension module when importing connector binding > -------------------------------------------------------------------------------- > > Key: TEIID-18 > URL: https://jira.jboss.org/jira/browse/TEIID-18 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.1.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #24362: When importing a connector binding that was exported from another server, an error dailog appears indicating the "connector_patch.jar" extension module is missing. However, there is no "Cancel" option in the dialog, and when you hit "OK", the wizard ends anyway. The specified module is not listed in either the source or target server's extension modules. Ramesh indicated everything will work despite the dialog, and this jar only exists for quick fixes, debugging, and testing, and should not cause this dialog to show up. > RReddy - Also while exporting the Connector Type using the console, since this file is not available the CAF file creation fails with a exception -- 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, 9 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