August 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-1708) Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1708?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1708: --------------------------------------- The session invalidation would happen to your preview connection, not your admin connection. The physical connections are not lost. > What would happen if Designer re-deployed the Master VDB whenever a sub-VDB is re-deployed and re-merged? That is exactly what I'm suggesting as the workaround, and the result would be the same. Current sessions would be terminated. > Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure > --------------------------------------------------------------------------------------------- > > Key: TEIID-1708 > URL: https://issues.jboss.org/browse/TEIID-1708 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Attachments: MasterVDB.vdb, testMergeVDBs.groovy, TestVPVDB.vdb > > > If a preview is run on a virtual procedure, then the procedure is changed and saved the preview still gives the results from the previous transformation. You have to close Developer Studio and re-open to get the correct result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1710) Request better exception message when connecting to an invalid VDB name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1710?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1710: ------------------------------------- so what is the suggestions here? I do not think listing all the valid databases is good idea. We can it does not exist, so check your vdb name? > Request better exception message when connecting to an invalid VDB name > ----------------------------------------------------------------------- > > Key: TEIID-1710 > URL: https://issues.jboss.org/browse/TEIID-1710 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When accessing a VDB with the incorrect name (in my case, a typo), the exception suggests that it's either down to an invalid logon and/or access problems. This is mis-leading and time-consuming to track down: > 09:52:35,991 WARN [SECURITY] Processing exception 'VDB "XXX" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:228). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1711) Unify logger definitions used in SOA-P and Teiid

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1711?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-1711. -------------------------------- Resolution: Done > Unify logger definitions used in SOA-P and Teiid > ------------------------------------------------ > > Key: TEIID-1711 > URL: https://issues.jboss.org/browse/TEIID-1711 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.4.1 > Reporter: Boris Belovic > Assignee: Van Halbert > Priority: Minor > Fix For: 7.4.1 > > > Main LOG4J config file - jboss-log4j.xml - uses <category> elements for logger definition, Teiid comes with newer <logger> elements for particular logger definition. If customer installs Teiid into SOA-P then he gets two different logger definitions in jboss-log4j.xml - LOG4J config file contains both <category> and <logger> elements. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1708) Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-1708?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-1708: ------------------------------------- What would happen if Designer re-deployed the Master VDB whenever a sub-VDB is re-deployed and re-merged? > Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure > --------------------------------------------------------------------------------------------- > > Key: TEIID-1708 > URL: https://issues.jboss.org/browse/TEIID-1708 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Attachments: MasterVDB.vdb, testMergeVDBs.groovy, TestVPVDB.vdb > > > If a preview is run on a virtual procedure, then the procedure is changed and saved the preview still gives the results from the previous transformation. You have to close Developer Studio and re-open to get the correct result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1708) Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-1708?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-1708: ------------------------------------- Any disconnect/reconnect in Designer will clear and re-load our cache of VDB's, Data Sources and Translators Seems like a bit much for designer to have to do when re-deploying ONE VDB. Can we find some other fix? > Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure > --------------------------------------------------------------------------------------------- > > Key: TEIID-1708 > URL: https://issues.jboss.org/browse/TEIID-1708 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Attachments: MasterVDB.vdb, testMergeVDBs.groovy, TestVPVDB.vdb > > > If a preview is run on a virtual procedure, then the procedure is changed and saved the preview still gives the results from the previous transformation. You have to close Developer Studio and re-open to get the correct result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1710) Request better exception message when connecting to an invalid VDB name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1710?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1710. ----------------------------------- Resolution: Cannot Reproduce Bug The client exception I get (from squirrel) is: Remote org.teiid.client.security.LogonException: VDB "bqt" version "latest" does not exist. This is using a 7.4 client/server. I don't believe this would be any different on 7.1.1. > Request better exception message when connecting to an invalid VDB name > ----------------------------------------------------------------------- > > Key: TEIID-1710 > URL: https://issues.jboss.org/browse/TEIID-1710 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When accessing a VDB with the incorrect name (in my case, a typo), the exception suggests that it's either down to an invalid logon and/or access problems. This is mis-leading and time-consuming to track down: > 09:52:35,991 WARN [SECURITY] Processing exception 'VDB "XXX" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:228). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1711) Unify logger definitions used in SOA-P and Teiid

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1711?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3268 to TEIID-1711: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1711 (was: SOA-3268) Affects Version/s: 7.4.1 (was: 5.1.0 GA) Component/s: Build/Kits (was: Configuration) (was: EDS) Security: (was: Public) Fix Version/s: 7.4.1 (was: 5.2.0 GA) > Unify logger definitions used in SOA-P and Teiid > ------------------------------------------------ > > Key: TEIID-1711 > URL: https://issues.jboss.org/browse/TEIID-1711 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.4.1 > Reporter: Boris Belovic > Assignee: Van Halbert > Priority: Minor > Fix For: 7.4.1 > > > Main LOG4J config file - jboss-log4j.xml - uses <category> elements for logger definition, Teiid comes with newer <logger> elements for particular logger definition. If customer installs Teiid into SOA-P then he gets two different logger definitions in jboss-log4j.xml - LOG4J config file contains both <category> and <logger> elements. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-1711) Unify logger definitions used in SOA-P and Teiid

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1711?page=com.atlassian.jira.plugin... ] Work on TEIID-1711 started by Van Halbert. > Unify logger definitions used in SOA-P and Teiid > ------------------------------------------------ > > Key: TEIID-1711 > URL: https://issues.jboss.org/browse/TEIID-1711 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.4.1 > Reporter: Boris Belovic > Assignee: Van Halbert > Priority: Minor > Fix For: 7.4.1 > > > Main LOG4J config file - jboss-log4j.xml - uses <category> elements for logger definition, Teiid comes with newer <logger> elements for particular logger definition. If customer installs Teiid into SOA-P then he gets two different logger definitions in jboss-log4j.xml - LOG4J config file contains both <category> and <logger> elements. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1708) Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1708?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1708: ------------------------------------- I believe Designer reconnects automatically when the connection is lost. Barry can you confirm? > Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure > --------------------------------------------------------------------------------------------- > > Key: TEIID-1708 > URL: https://issues.jboss.org/browse/TEIID-1708 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Attachments: MasterVDB.vdb, testMergeVDBs.groovy, TestVPVDB.vdb > > > If a preview is run on a virtual procedure, then the procedure is changed and saved the preview still gives the results from the previous transformation. You have to close Developer Studio and re-open to get the correct result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1710) Request better exception message when connecting to an invalid VDB name

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1710?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3266 to TEIID-1710: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1710 (was: SOA-3266) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: Server (was: EDS) Security: (was: Public) > Request better exception message when connecting to an invalid VDB name > ----------------------------------------------------------------------- > > Key: TEIID-1710 > URL: https://issues.jboss.org/browse/TEIID-1710 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When accessing a VDB with the incorrect name (in my case, a typo), the exception suggests that it's either down to an invalid logon and/or access problems. This is mis-leading and time-consuming to track down: > 09:52:35,991 WARN [SECURITY] Processing exception 'VDB "XXX" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:228). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 August 2011