May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-620) VDB's configuration.def contains more info than needed/desired

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-620?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-620: -------------------------------------- The problem is occurring on the Teiid side in the DefReaderWriter. None of the property metadata is used to determine what properties should be written. > VDB's configuration.def contains more info than needed/desired > -------------------------------------------------------------- > > Key: TEIID-620 > URL: https://jira.jboss.org/jira/browse/TEIID-620 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 6.0.0 > Environment: fedora 10, Teiid 6.0.0, Teiid Designer 040709 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 6.1.0 > > > Because of changes in Connector API & connector type property changes, the VDB's ConfigurationInfo.def file is containing more info than it needs. > We need to filter the "default" properties because they are supplied by default on the server and in teiid embedded. > --------- Original Description --------------- > I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. > Ramesh will fill in the technical details. > This prevents using the VDB inside Teiid Embedded. > ---------------------------------------------------------- -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-620) VDB's configuration.def contains more info than needed/desired

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-620?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-620: ------------------------------------ Assignee: Steven Hawkins > VDB's configuration.def contains more info than needed/desired > -------------------------------------------------------------- > > Key: TEIID-620 > URL: https://jira.jboss.org/jira/browse/TEIID-620 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 6.0.0 > Environment: fedora 10, Teiid 6.0.0, Teiid Designer 040709 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 6.1.0 > > > Because of changes in Connector API & connector type property changes, the VDB's ConfigurationInfo.def file is containing more info than it needs. > We need to filter the "default" properties because they are supplied by default on the server and in teiid embedded. > --------- Original Description --------------- > I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. > Ramesh will fill in the technical details. > This prevents using the VDB inside Teiid Embedded. > ---------------------------------------------------------- -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-620) VDB's configuration.def contains more info than needed/desired

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-620?page=com.atlassian.jira.plug... ] Steven Hawkins moved TEIIDDES-136 to TEIID-620: ----------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-620 (was: TEIIDDES-136) Component/s: Common (was: VDB & Execution) Fix Version/s: 6.1.0 (was: Future) Affects Version/s: 6.0.0 (was: 6.0.0) > VDB's configuration.def contains more info than needed/desired > -------------------------------------------------------------- > > Key: TEIID-620 > URL: https://jira.jboss.org/jira/browse/TEIID-620 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 6.0.0 > Environment: fedora 10, Teiid 6.0.0, Teiid Designer 040709 > Reporter: Paul Nittel > Priority: Blocker > Fix For: 6.1.0 > > > Because of changes in Connector API & connector type property changes, the VDB's ConfigurationInfo.def file is containing more info than it needs. > We need to filter the "default" properties because they are supplied by default on the server and in teiid embedded. > --------- Original Description --------------- > I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. > Ramesh will fill in the technical details. > This prevents using the VDB inside Teiid Embedded. > ---------------------------------------------------------- -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-618) Minor connector config changes

by Steven Hawkins (JIRA)

Minor connector config changes ------------------------------ Key: TEIID-618 URL: https://jira.jboss.org/jira/browse/TEIID-618 Project: Teiid Issue Type: Task Components: Connector API Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Resultset cache max size should be an expert property - all others are marked as such. Connector classpath only needs to exist on the parent connector type, and does not need to be required on jdbc connectors (embedded deployments may not need to include an explicit jar) -- 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

15 years

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-619) Connector jar needed to be added to classpath: extensionjar:connector-jdbc-6.1.0-SNAPSHOT.jar

by Paul Nittel (JIRA)

Connector jar needed to be added to classpath: extensionjar:connector-jdbc-6.1.0-SNAPSHOT.jar --------------------------------------------------------------------------------------------- Key: TEIID-619 URL: https://jira.jboss.org/jira/browse/TEIID-619 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Environment: fedora 10 Reporter: Paul Nittel Assignee: Steven Hawkins After installing JBEDSP server (05/21/2009), my single Oracle connector binding would not start. I added the classes12_g.jar file to extension properties, but still no joy in Mudville. Van suggested adding connector-jdbc-6.1.0-SNAPSHOT.jar to the classpath and that did the trick. It must be missing underneath the covers. The binding's classpath wound up being: extensionjar:classes12_g.jar;extensionjar:connector-jdbc-6.1.0-SNAPSHOT.jar -- 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

15 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-617) Expose Security User/Password to AdminAPI

by Ted Jones (JIRA)

Expose Security User/Password to AdminAPI ----------------------------------------- Key: TEIID-617 URL: https://jira.jboss.org/jira/browse/TEIID-617 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.1.0 Need to expose the Security User/Password to the AdminApi. This is required for the new web-based 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

15 years

2
2
0 / 0

[JBoss JIRA] Assigned: (TEIID-518) Invalid Message in Console Deploying VDB

by Li Liang (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-518?page=com.atlassian.jira.plug... ] Li Liang reassigned TEIID-518: ------------------------------ Assignee: Li Liang > Invalid Message in Console Deploying VDB > ---------------------------------------- > > Key: TEIID-518 > URL: https://jira.jboss.org/jira/browse/TEIID-518 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Li Liang > Fix For: 6.1.1 > > Attachments: snapshot1.png > > > I deployed a new VDB in the console using a VDB from the repository that had connector binding defined. The message I received prior to deployment was the all models had binding associated with them and the VDB would be deployed with the status of INACTIVE. Should be ACTIVE (and was deployed as such). -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-421) Membership Domain Provider reference still exists after Provider deleted

by Li Liang (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-421?page=com.atlassian.jira.plug... ] Work on TEIID-421 started by Li Liang. > Membership Domain Provider reference still exists after Provider deleted > ------------------------------------------------------------------------ > > Key: TEIID-421 > URL: https://jira.jboss.org/jira/browse/TEIID-421 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Assignee: Li Liang > Fix For: 6.1.1 > > > 1. Had two Membership Domain Providers in Console. > 2. Deleted 1 Provider. > 3. Exit Console > 4. Started Console > 5. Started to add more Admin Roles. > 6. The Select Group (Step 1) screen has a drop down for Domain. > 7. The drop down still shows the previously deleted Membership Domain Provider even though it doesn't exist. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-421) Membership Domain Provider reference still exists after Provider deleted

by Li Liang (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-421?page=com.atlassian.jira.plug... ] Li Liang reassigned TEIID-421: ------------------------------ Assignee: Li Liang > Membership Domain Provider reference still exists after Provider deleted > ------------------------------------------------------------------------ > > Key: TEIID-421 > URL: https://jira.jboss.org/jira/browse/TEIID-421 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Assignee: Li Liang > Fix For: 6.1.1 > > > 1. Had two Membership Domain Providers in Console. > 2. Deleted 1 Provider. > 3. Exit Console > 4. Started Console > 5. Started to add more Admin Roles. > 6. The Select Group (Step 1) screen has a drop down for Domain. > 7. The drop down still shows the previously deleted Membership Domain Provider even though it doesn't exist. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-611) Virtual Database Import Wizard Step 1 - the NEXT button does not activate without clicking other areas

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-611?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-611. ---------------------------------- Resolution: Cannot Reproduce Bug I could not reproduce. I'm hoping that the fix for TEIID-609 addressed this as well. > Virtual Database Import Wizard Step 1 - the NEXT button does not activate without clicking other areas > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-611 > URL: https://jira.jboss.org/jira/browse/TEIID-611 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.1.0 > Environment: Console on Windows > Reporter: Warren Gibson > Fix For: 6.1.1 > > > When importing a VDB the first step of the import wizard will not activate the NEXT button until user clicks around in the file system selector and returns to select the 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009