October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3739. ----------------------------------- Fix Version/s: 8.12 8.11.5 Resolution: Done The removal of the switch service in cleanup seems to be the issue. Moving to undeploy addresses this. > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.5 > > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3741) Create an SAP JCo Translator

by Ted Jones (JIRA)

Ted Jones created TEIID-3741: -------------------------------- Summary: Create an SAP JCo Translator Key: TEIID-3741 URL: https://issues.jboss.org/browse/TEIID-3741 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Ted Jones Assignee: Ted Jones We will create an SAP JCo translator that will connect directly to SAP and leverage much of the functionality implemented by the Camel component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3739: ------------------------------------- I suspect this be may change in the EAP behavior, we need to double check > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3739: --------------------------------------- > So, in this case when the imported VDB comes back active, then the importing VDB should follow that, unless we configured as optional dependency. There is no attempt made to start the service. The behavior is the same whether redeploying the importing vdb or explicitly undeploying and then later redeploying. It does not appear that the service will be restarted once the original has been stopped. > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3739: ------------------------------------- When the dependency comes back, the original service that depends on it gets restarted again. So, in this case when the imported VDB comes back active, then the importing VDB should follow that, unless we configured as optional dependency. > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3717) Enable SNI (Server Name Indication) support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3717?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3717: --------------------------------------- > Netty doesn't add support until 4.x version. Should we patch it to make it work? Unfortunately I'm not clear on what is needed in general, so I can't say that we need explicit support from netty. > Also, isn't it just an option for the client to support SNI (even though it has limitations) or do we need to wait for: XNIO-227 Where does XNIO fit in? As for being a client change, that may be. As I say above, our usage of SSL can be configured to return to use a server key based upon the alias, so the host name does not need to be considered there. > Enable SNI (Server Name Indication) support > ------------------------------------------- > > Key: TEIID-3717 > URL: https://issues.jboss.org/browse/TEIID-3717 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.1 > > > Enable SNI support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3717) Enable SNI (Server Name Indication) support

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3717?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3717: ------------------------------------ Netty doesn't add support until 4.x version. Should we patch it to make it work? Also, isn't it just an option for the client to support SNI (even though it has limitations) or do we need to wait for: XNIO-227 > Enable SNI (Server Name Indication) support > ------------------------------------------- > > Key: TEIID-3717 > URL: https://issues.jboss.org/browse/TEIID-3717 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.1 > > > Enable SNI support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3739: --------------------------------------- Having a hard dependency on the imported vdb triggers the imported vdb service removal. Once the new imported vdb is available though nothing triggers the importing vdb service to restart. It looks like redeploying a translator would have the same effect - all vdbs that use it would need to be redeployed. Ramesh - should the importing vdb service not be removed when an import is removed (and have additional active/inactive handling for this), or does this seem like an EAP issue? > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3740) ldap post

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3740?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3740: --------------------------------------- Made a change so that the full set of validations from inherent updates are logged at an info level during vdb startup. If designer is not showing these warnings, then an issue is needed there. > ldap post > --------- > > Key: TEIID-3740 > URL: https://issues.jboss.org/browse/TEIID-3740 > Project: Teiid > Issue Type: Feature Request > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Attachments: testDelete.vdb > > > I created a virtual table from Ldap source table, and I am able to do a odata GET call. When I try to make POST on the same table. It is giving the below errors : > > { > "error": { > "code": "ServerErrorException", > "message": { > "lang": "en-US", > "value": "TEIID30492 TEIID30061 Insert is not allowed on the view LdapView.\"user\". A procedure may be needed to handle the Insert since: The query defining an updatable view has no valid target for INSERTs." > } > } > } > > My virtual table is a simple (select * from table) statement. and "Suports update" is checked for source and view. VDB file attached for reference > how do i make a successful post? > Thanks in advance, > Prashanthi -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3653) Create examples for the following web data sources

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3653?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-3653: ---------------------------------- Assignee: Kylin Soong (was: Van Halbert) > Create examples for the following web data sources > -------------------------------------------------- > > Key: TEIID-3653 > URL: https://issues.jboss.org/browse/TEIID-3653 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts > Reporter: Van Halbert > Assignee: Kylin Soong > > Create examples for the following web data sources: > LinkedIn, Twitter, Facebook, Wikipedia, and Data.gov -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015