October 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2705) Remove from standalone.cli and domain.cli, the adding of the resource adapters

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2705?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-2705. -------------------------------- Resolution: Rejected It was determined this is not an issue > Remove from standalone.cli and domain.cli, the adding of the resource adapters > ------------------------------------------------------------------------------ > > Key: TEIID-2705 > URL: https://issues.jboss.org/browse/TEIID-2705 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > Remove the adding of the resource adapters in the cli configuration scripts. This is because: > 1. They don't define a specific instance > 2. When multiple instances are added, they each should have a different name, so that one can be removed without removing the other. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2687) Expose Translator override property definitions through Admin API

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2687?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2687. --------------------------------- Labels: alpha3 (was: ) Resolution: Done 1) Added "read-translator-properties" CLI command to read the translator extension properties 2) Added getTranslatorPropertyDefinitions method to the Admin API 3) Added getTranslatorPropertyDefinitions method in AdminShell interface > Expose Translator override property definitions through Admin API > ----------------------------------------------------------------- > > Key: TEIID-2687 > URL: https://issues.jboss.org/browse/TEIID-2687 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: alpha3 > Fix For: 8.6 > > > Currently in the admin api > {code} > public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName) throws AdminException; > {code} > only works with resource-adapters and data sources in terms of returning the properties that can be configured on them. > This request is to extend the functionality to return the "overridable" properties for "translators", such as > {code} > public Collection<PropertyDefinition> getTemplatePropertyDefinitions(String templateName, boolean isTranslator) throws AdminException; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2712. --------------------------------- Resolution: Rejected > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2712: ------------------------------------- Upon further investigation into code, the current code as designed is correct. The issue is Data Source Name != JNDI Name to Obtain a JNDI name, the client needs to do {code} Properties p = getDataSource(name); String jndiName = p.getProperty("jndi-name"); {code} > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2697) Change to use community bom

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2697?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2697: --------------------------------------- changed the cassandra module.xml to use the managed jackson version 1.9.9 instead of the datastax 1.9.2 - with limited query testing this still worked fine. We'll put more effort into handling the cassandra dependencies, especially the conflicting ones, with later productization. > Change to use community bom > --------------------------- > > Key: TEIID-2697 > URL: https://issues.jboss.org/browse/TEIID-2697 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.6 > > > Teiid should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2710) Rest procedures should support optional parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2710?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2710. ----------------------------------- Resolution: Done Changed the procedure call to use the same named parameter syntax that was added for odata. Optional parameters will only work for post procedures, which use FormParams - more work would be required use QueryParams instead of PathParams for optional get parameters. > Rest procedures should support optional parameters > -------------------------------------------------- > > Key: TEIID-2710 > URL: https://issues.jboss.org/browse/TEIID-2710 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > We need to test our rest logic to ensure it supports optional parameters in the uri pattern. > And then update the procedure call to use named parameters so that defaultable missing parameters will use defaults (similar to the TeiidProducer/LocalClient logic used for OData). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2697) Change to use community bom

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2697?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2697: ------------------------------------- ah! I was looking into fixing the deployment and was not sure why it was occurring? > Change to use community bom > --------------------------- > > Key: TEIID-2697 > URL: https://issues.jboss.org/browse/TEIID-2697 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.6 > > > Teiid should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2697) Change to use community bom

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2697?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2697: --------------------------------------- this also broke the cassandra kitting by forcing the managed version of jackson > Change to use community bom > --------------------------- > > Key: TEIID-2697 > URL: https://issues.jboss.org/browse/TEIID-2697 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.6 > > > Teiid should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2710) Rest procedures should support optional parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2710?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2710: --------------------------------------- After working through this it doesn't look like PathParams are supposed to be defaultable. QueryParams are viable though - but it would require additional metadata to indicate whether defaultable parameters should be query or path params. > Rest procedures should support optional parameters > -------------------------------------------------- > > Key: TEIID-2710 > URL: https://issues.jboss.org/browse/TEIID-2710 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > We need to test our rest logic to ensure it supports optional parameters in the uri pattern. > And then update the procedure call to use named parameters so that defaultable missing parameters will use defaults (similar to the TeiidProducer/LocalClient logic used for OData). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2710) Rest procedures should support optional parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2710?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2710: ---------------------------------- Description: We need to test our rest logic to ensure it supports optional parameters in the uri pattern. And then update the procedure call to use named parameters so that defaultable missing parameters will use defaults (similar to the TeiidProducer/LocalClient logic used for OData). was: We need to test our rest logic to ensure it supports optional parameters in the uri pattern: {code}@Path("/mypath{param1 : (/param2)?}"){code} And then update the procedure call to use named parameters so that defaultable missing parameters will use defaults (similar to the TeiidProducer/LocalClient logic used for OData). > Rest procedures should support optional parameters > -------------------------------------------------- > > Key: TEIID-2710 > URL: https://issues.jboss.org/browse/TEIID-2710 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > We need to test our rest logic to ensure it supports optional parameters in the uri pattern. > And then update the procedure call to use named parameters so that defaultable missing parameters will use defaults (similar to the TeiidProducer/LocalClient logic used for OData). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 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 October 2013