February 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-1472) EDS exceptions are very vague

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1472?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2920 to TEIID-1472: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1472 (was: SOA-2920) Issue Type: Enhancement (was: Quality Risk) Affects Version/s: 7.1.1 (was: 5.1.0.CR1) Component/s: Server (was: EDS) Security: (was: Public) > EDS exceptions are very vague > ----------------------------- > > Key: TEIID-1472 > URL: https://issues.jboss.org/browse/TEIID-1472 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 7.1.1 > Reporter: Martin Vecera > > Exceptions thrown by EDS are not very helpful and descriptive. The messages are like "Error occured". > User might not recognize where a problem is. It is hard to develop applications with EDS since the bug tracking is very difficult without proper error message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1470: --------------------------------------- why would it have to be blocking? the initial metadata load code is not. it would just have to keep it in an inactive status until the load finished. > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.4 > > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1470: ------------------------------------- Should it try to retrieve metadata, or keep it as in_active based on metadata non-availability? If we try to retrieve, then it is a blocking operation for other processes. IMO, it should be in_active until user re-deploys the vdb, at which time the metadata is loaded. > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.4 > > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1470: ---------------------------------- Fix Version/s: 7.4 The logic that currently sets the active flag does not consider whether the metadata has been retrieved. > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.4 > > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1469) EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-1469?page=com.atlassian.jira.plugin... ] Ted Jones resolved TEIID-1469. ------------------------------ Resolution: Done Changed session id (and transaction id) from Long to String > EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation > -------------------------------------------------------------------------------------------------- > > Key: TEIID-1469 > URL: https://issues.jboss.org/browse/TEIID-1469 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.4 > > > The Terminate Session operation validates the session id parameter as an integer when it is actually alpha-numeric, making it impossible to execute the operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1469) EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-1469?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-1469: ----------------------------- Fix Version/s: 7.4 > EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation > -------------------------------------------------------------------------------------------------- > > Key: TEIID-1469 > URL: https://issues.jboss.org/browse/TEIID-1469 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.4 > > > The Terminate Session operation validates the session id parameter as an integer when it is actually alpha-numeric, making it impossible to execute the operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1306) Add support for JSON data sources (JSON translator, JSON-to-table mapping functions).

by Ken Johnson (JIRA)

Add support for JSON data sources (JSON translator, JSON-to-table mapping functions). ------------------------------------------------------------------------------------- Key: TEIID-1306 URL: https://jira.jboss.org/browse/TEIID-1306 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.1 Reporter: Ken Johnson Assignee: Steven Hawkins Fix For: 7.2 Consider adding support in Teiid to consume services (as data sources) that return JSON payloads rather than XML payloads. This is an increasingly common integration scenario. The approach used for XML processing seems to be a compatible pattern for this use case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Resolved: (TEIID-1467) Procedures in Teiid are not Resolvable if Their Models are Marked as Not Visible

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1467?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1467. ----------------------------------- Labels: procedure visibility (was: ) Fix Version/s: 7.4 Resolution: Done Updated the procedure resolving logic to correctly check for the fully qualified case. > Procedures in Teiid are not Resolvable if Their Models are Marked as Not Visible > -------------------------------------------------------------------------------- > > Key: TEIID-1467 > URL: https://issues.jboss.org/browse/TEIID-1467 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1.1 > Reporter: Ted Jones > Labels: visibility, procedure > Fix For: 7.4 > > > If a model containing procedures is marked as not visible, the queryplanner cannot resolve them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-1470: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2909 to TEIID-1470: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1470 (was: SOA-2909) Affects Version/s: 7.1.1 (was: 5.1.0.CR1) Component/s: Server (was: EDS) Security: (was: Public) > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Van Halbert > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2011