April 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2114) Custom translators and resource-adapters are not correctly supported

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2114?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2114: ----------------------------------------- If the 'driver-name' property is available it will be used. > Custom translators and resource-adapters are not correctly supported > -------------------------------------------------------------------- > > Key: TEIIDDES-2114 > URL: https://issues.jboss.org/browse/TEIIDDES-2114 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.5, 8.3.3 > > > If user added a custom translator and resource-adapter to the server, they should be able to use them in Designer using Teiid Connection importer. > * Currently it seems like Teiid connection importer only works with known types that are hard coded with names. This restriction must be removed, should work with any resource-adapter that is added to Teiid system > * The class-name property is available with data source template properties, so default value for this must be selected from the provided list of properties. This must not be hard coded for any resource-adapters. > * Most every resource-adapter property comes with a small description, so we must show the description when the property is hi-lighted in the wizard. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2119) Issues with deploying/undeploying dynamic vdb during Teiid Connection importer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2119?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2119: ----------------------------------------- Yes deploymentName for dynamicVDB is like "import-vdb.xml". The vdbName is the name of the vdb within the file. > Issues with deploying/undeploying dynamic vdb during Teiid Connection importer > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2119 > URL: https://issues.jboss.org/browse/TEIIDDES-2119 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 8.5 > > > Teiid Connection Importer is not working at the moment. There seems to be a change in the ExecutionAdmin and TeiidImportManager logic around the naming of the importVDB-vdb.xml file and the undeploy does not work. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2114) Custom translators and resource-adapters are not correctly supported

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2114?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2114: ---------------------------------------- https://issues.jboss.org/browse/TEIID-2925 is Teiid 8.7 Final, which being released today. So this needs to re-opened fix with driver-name. > Custom translators and resource-adapters are not correctly supported > -------------------------------------------------------------------- > > Key: TEIIDDES-2114 > URL: https://issues.jboss.org/browse/TEIIDDES-2114 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.5, 8.3.3 > > > If user added a custom translator and resource-adapter to the server, they should be able to use them in Designer using Teiid Connection importer. > * Currently it seems like Teiid connection importer only works with known types that are hard coded with names. This restriction must be removed, should work with any resource-adapter that is added to Teiid system > * The class-name property is available with data source template properties, so default value for this must be selected from the provided list of properties. This must not be hard coded for any resource-adapters. > * Most every resource-adapter property comes with a small description, so we must show the description when the property is hi-lighted in the wizard. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2119) Issues with deploying/undeploying dynamic vdb during Teiid Connection importer

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2119?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2119: ---------------------------------------- To make sure we are all same page deploymentName = is the name of the deployment file like "import-vdb.xml" vdbName = Name given to the vdb in the vdb.xml file, like "foo" The deploy and undeploy operations are done using the "deploymentName", any SQL connections are done with "vdbName" I have not looked at the commit changes above, just wanted to clear any confusion. > Issues with deploying/undeploying dynamic vdb during Teiid Connection importer > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2119 > URL: https://issues.jboss.org/browse/TEIIDDES-2119 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 8.5 > > > Teiid Connection Importer is not working at the moment. There seems to be a change in the ExecutionAdmin and TeiidImportManager logic around the naming of the importVDB-vdb.xml file and the undeploy does not work. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2113) Replace 3 teiid client plugins in build/feature/config with org.teiid.runtime.client plugin

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2113?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-2113. --------------------------------------- Resolution: Done > Replace 3 teiid client plugins in build/feature/config with org.teiid.runtime.client plugin > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2113 > URL: https://issues.jboss.org/browse/TEIIDDES-2113 > Project: Teiid Designer > Issue Type: Task > Components: Build, Release Work > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.5 > > > Current Designer build includes a client feature which includes 3 client plugins. > Replace this feature (or remove it) and include the single *org.teiid.runtime.client* plugin instead -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2120 at 4/16/14 11:40 AM: ------------------------------------------------------------------ So currently XSD's are added to a VDB and treated as VdbModelEntrys complete with the corresponding Index files, which Teiid doesn't use anyway. We could : * Change to using the VdbEntry instead for XSD files and NOT add the index files for them * The XSD files would show up in the *Other Files* tab in the VDB editor. To handle old VDBs that include XSD files, we'd also have to add validation to detect these XSD files and allow a quick-fix to change from VdbModelEntrys to VdbEntrys was (Author: blafond): So currently XSD's are added to a VDB and treated as VdbModelEntrys complete with the corresponding Index files, which Teiid doesn't use anyway. We could : * Change to using the VdbEntry instead for XSD files and NOT add the index files for them * The XSD files would show up in the *Other Files* tab in the VDB editor. > unable to reference same name .xsd when saving .vdb > --------------------------------------------------- > > Key: TEIIDDES-2120 > URL: https://issues.jboss.org/browse/TEIIDDES-2120 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Johnathon Lee > Assignee: Paul Richardson > Fix For: 8.5, 8.3.3 > > > User can no longer add same name .xsd to a vdb (name same, location(s) different). > Results in: > java.lang.RuntimeException: javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 61; columnNumber: 168; Duplicate unique value [<name>] declared for identity constraint of element "vdb".] > at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50) > at org.teiid.designer.vdb.VdbUtil.getVdbManifest(VdbUtil.java:178) > at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:120) > at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:267) > at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:656) > at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:895) > at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:466) > at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) > at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) > at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) > at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) > at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) > Caused by: javax.xml.bind.UnmarshalException -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2120: ---------------------------------------- So currently XSD's are added to a VDB and treated as VdbModelEntrys complete with the corresponding Index files, which Teiid doesn't use anyway. We could : * Change to using the VdbEntry instead for XSD files and NOT add the index files for them * The XSD files would show up in the *Other Files* tab in the VDB editor. > unable to reference same name .xsd when saving .vdb > --------------------------------------------------- > > Key: TEIIDDES-2120 > URL: https://issues.jboss.org/browse/TEIIDDES-2120 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Johnathon Lee > Assignee: Paul Richardson > Fix For: 8.5, 8.3.3 > > > User can no longer add same name .xsd to a vdb (name same, location(s) different). > Results in: > java.lang.RuntimeException: javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 61; columnNumber: 168; Duplicate unique value [<name>] declared for identity constraint of element "vdb".] > at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50) > at org.teiid.designer.vdb.VdbUtil.getVdbManifest(VdbUtil.java:178) > at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:120) > at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:267) > at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:656) > at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:895) > at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:466) > at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) > at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) > at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) > at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) > at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) > Caused by: javax.xml.bind.UnmarshalException -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2121) Create a Connections editor dialog that can edit/maage a source model's connecition profile and translator info

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2121: -------------------------------------- Summary: Create a Connections editor dialog that can edit/maage a source model's connecition profile and translator info Key: TEIIDDES-2121 URL: https://issues.jboss.org/browse/TEIIDDES-2121 Project: Teiid Designer Issue Type: Feature Request Components: Datatools Integration, Modeling Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.5 Moved connection related actions to it's own sub-menu, *Connection* under *Modeling* action. After further thought, it would simplify things even more if we created a dialog that can edit/manage all connection-related tasks for source models. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2114) Custom translators and resource-adapters are not correctly supported

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2114?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2114. ------------------------------------- Fix Version/s: 8.5 8.3.3 Resolution: Done If the 'driver-name' property is not present, we have added code to find the driver name by iterating all available templates. The datasource 'class-name' is matched by iterating through all available templates and finding the template with 'managedconnectionfactory-class' defaultValue that matches. So when the 'driver-name' is available we will use it. (see linked JIRA). If not available we use the method above to determine. https://github.com/Teiid-Designer/teiid-designer/pull/325 > Custom translators and resource-adapters are not correctly supported > -------------------------------------------------------------------- > > Key: TEIIDDES-2114 > URL: https://issues.jboss.org/browse/TEIIDDES-2114 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.5, 8.3.3 > > > If user added a custom translator and resource-adapter to the server, they should be able to use them in Designer using Teiid Connection importer. > * Currently it seems like Teiid connection importer only works with known types that are hard coded with names. This restriction must be removed, should work with any resource-adapter that is added to Teiid system > * The class-name property is available with data source template properties, so default value for this must be selected from the provided list of properties. This must not be hard coded for any resource-adapters. > * Most every resource-adapter property comes with a small description, so we must show the description when the property is hi-lighted in the wizard. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2120: ------------------------------------------ The notion of a model is analogous to a schema for Teiid and is tracked by name. The marshalling logic just uses a map, so duplicates would end up overwriting each other. There are a couple of options from a design side. 1. don't track "other" model types as models - because they are not meaningful to the runtime as model entries (I believe that has already been raised as an issue). 2. just ensure that model entries have unique names. > unable to reference same name .xsd when saving .vdb > --------------------------------------------------- > > Key: TEIIDDES-2120 > URL: https://issues.jboss.org/browse/TEIIDDES-2120 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Johnathon Lee > Assignee: Paul Richardson > Fix For: 8.5, 8.3.3 > > > User can no longer add same name .xsd to a vdb (name same, location(s) different). > Results in: > java.lang.RuntimeException: javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 61; columnNumber: 168; Duplicate unique value [<name>] declared for identity constraint of element "vdb".] > at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50) > at org.teiid.designer.vdb.VdbUtil.getVdbManifest(VdbUtil.java:178) > at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:120) > at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:267) > at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:656) > at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:895) > at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:466) > at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) > at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) > at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) > at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) > at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70) > Caused by: javax.xml.bind.UnmarshalException -- 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

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2014