June 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-377) Model visibility changes during VDB deployment wizards are not retained when moving forward and backward through wizard

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-377?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-377. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Model visibility changes during VDB deployment wizards are not retained when moving forward and backward through wizard > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-377 > URL: https://jira.jboss.org/jira/browse/TEIID-377 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Console 5.5.3 EA3 - Build 3079 > Linux Kernel 2.6.25.14-69 > Reporter: Larry O'Leary > Fix For: 6.2.0 > > Attachments: E2EModelVisibilityTestScript.projectset.zip > > > When deploying a VDB from within the Console and changing model visibility from the default settings stored in the VDB, the overridden settings are not kept if one navigates one step earlier in the VDB deployment wizard. It seems that most users would expect their setting to be retained if the go forward and backward through a wizard. Kind of defeats the purpose of Back if it has similar affects to Cancel. > Here is a more detail explanation of what I did. I was performing the E2E Model Visibility Test Script. > Create a VDB that contains multiple models. > From the MM Console, deploy the VDB using the "New VDB" or "New VDB Version" button and in Step 3 of the "New Virtual Database Definition Wizard" or "New Virtual Database Version Definition Wizard" change the visibility of the models (so as the defaults are not selected). > Click Next > Click Back > Click Back > Click Next > PROBLEM: The default visibility has been reselected and changes to visibility have been lost > I would expect that the changes made to model visibility would have been retained when going from Step 4 to Step 3 to Step 2 to Step 3. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-630) Add Support for UDDI V3 in WSDL Publishing Feature of Console

by Ted Jones (JIRA)

Add Support for UDDI V3 in WSDL Publishing Feature of Console ------------------------------------------------------------- Key: TEIID-630 URL: https://jira.jboss.org/jira/browse/TEIID-630 Project: Teiid Issue Type: Feature Request Components: Console Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.2.0 We currently only support UDDI V2 in our UDDI publishing within our console. We need to be able to support both V2 and V3. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-365) Console Error Message when logging into MM Server is confusing

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-365?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-365. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Console Error Message when logging into MM Server is confusing > -------------------------------------------------------------- > > Key: TEIID-365 > URL: https://jira.jboss.org/jira/browse/TEIID-365 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Logging into MetaMatrix Server slntmm07 with MetaMatrix Console > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.2.0 > > Attachments: slntmm07logon.jpg > > > When attempting to log into slntmm07 I am presented with a dialog box stating "Connection to mm://slntmm06:50201 for user metamatrixadmin already exists." > While it is true I am logged into slntmm06, that has nothing to do with me logging into slntmm07 and the dialog is confusing. See attached file slntmm07logon.jpg -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-378) Only synchronize referenced connector bindings when importing a new VDB

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-378?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-378. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Only synchronize referenced connector bindings when importing a new VDB > ----------------------------------------------------------------------- > > Key: TEIID-378 > URL: https://jira.jboss.org/jira/browse/TEIID-378 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Priority: Minor > Fix For: 6.2.0 > > > Synchronization with failed bindings causes an error dialog in Console. During a VDB import (and the default synchronization at the end), this causes a user to believe there is an issue with the newly imported VDB. > Per I-T #214848 by john lee: > Summary: > Syncronization of unrelated services during VDB Deployment may cause stacktraces unrelated to the current deployment > Description of problem: > Selecting synchronize during deployment of a VDB may cause a stacktrace due to an failing service unrelated to the deployed VDB. > How reproducible: > Deploy and sync a vdb on a server with an unrelated failing service. > Steps to Reproduce: > Actual results: > Expected results: > Additional info: > Per Van Halbert: only sync the required services w/the deployed VDB. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-228) Need to verify keystore/password when changing SSL resource props

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-228?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-228. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Need to verify keystore/password when changing SSL resource props > ----------------------------------------------------------------- > > Key: TEIID-228 > URL: https://jira.jboss.org/jira/browse/TEIID-228 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > > Defect Tracker #19027: Enhancement: It's very easy to hose up the server by enabling SSL and then setting the SSL properties to point to an invalid keystore or invalid password. We should, if possible, verify that the keystore and password is valid when applying the SSL resource property 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-28) VDB Wizard Layout Issues When Resizing

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-28?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-28. --------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > VDB Wizard Layout Issues When Resizing > -------------------------------------- > > Key: TEIID-28 > URL: https://jira.jboss.org/jira/browse/TEIID-28 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > > Defect Tracker #25013: Running console on Fedora 8. On the Virtual Database panel, click the "New VDB" button. When you resize the "Step 1" dialog the content does not resize. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-70) Bouncing server, then synchronize (during bounce) should be prohibited.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-70?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-70. --------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Bouncing server, then synchronize (during bounce) should be prohibited. > ----------------------------------------------------------------------- > > Key: TEIID-70 > URL: https://jira.jboss.org/jira/browse/TEIID-70 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > > Defect Tracker #19301: JPC 11/18/05 - Title was: Bouncing server, then synchronize connector bindings appears to duplicate the binding names in tree > 1) Turn on entitlements on slntmm07:43501 > 2) Bounce system > 3) The connector bindings need to be synched - synchronize > 4) The bindings now show up in duplicate, with everyother one highlighted in red - see print screen -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-193) MembershipService does not show failure in Console when unable to connect to LDAP database

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-193?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-193. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > MembershipService does not show failure in Console when unable to connect to LDAP database > ------------------------------------------------------------------------------------------ > > Key: TEIID-193 > URL: https://jira.jboss.org/jira/browse/TEIID-193 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Defect Tracker #2865 : Set up MembershipService to have MetaMatrix and LDAP users. Server PC was unable to communicate with Unix box hosting LDAP database. Server started and MembershipService showed Running even though it had failed to read LDAP users. There is an exception in MetaMatrixVM log but need a visual clue in Console. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-72) show authorization properties on the security summary

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-72?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-72. --------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > show authorization properties on the security summary > ----------------------------------------------------- > > Key: TEIID-72 > URL: https://jira.jboss.org/jira/browse/TEIID-72 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Defect Tracker #24717: For clarity the authorization properties in system properties should be also be located on the security summary. The should act as dependent properties of the enable authentication and authorization -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-362) Console - Create New Data Roles panel step 2 & 3 displays wrong VDB version #

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-362?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-362. ---------------------------------- Resolution: Deferred Deferring post 6.1.1 console work. > Console - Create New Data Roles panel step 2 & 3 displays wrong VDB version # > ----------------------------------------------------------------------------- > > Key: TEIID-362 > URL: https://jira.jboss.org/jira/browse/TEIID-362 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: MM Console in Windows environment on slntmm06 > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.2.0 > > > Creating New Data Roles: > Step 1 panel I selected the VDB and version 2 > Steps 2 & 3 panels show VDB version 1 > Step 4 shows VDB version 2 > Data Roles were actually created for VDB version 2 but steps 2 & 3 were displaying the wrong version # -- 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, 10 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