August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-558) When creating WAR file, get: File not found, ...eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources

by Paul Nittel (JIRA)

When creating WAR file, get: File not found, ...eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-558 URL: https://jira.jboss.org/browse/TEIIDDES-558 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid 7.1 M1 Designer Reporter: Paul Nittel Attachments: NoWarFile.zip I had previously modeled the Yahoo UDF VDB which contains a Web service. I right-clicked the VDB > Modeling > Create JBossWS CXF War. When I went to locate the file, I couldn't locate it or the directory in which it was to be created. Selecting alternate, existing directories also did not work as anticipated. Finally, I noticed I had been receiving errors in the Designer's message log: Error 2010-08-16 09:19:53.163 An error occurred while creating WAR file, check log for detail java.io.FileNotFoundException: The web lib directory, /home/pnittel/TDes71M1/eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources, does not exist on the file system. at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.getWebLibDirectoryPath(DefaultWebArchiveBuilderImpl.java:524) at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.getWebFiles(DefaultWebArchiveBuilderImpl.java:372) at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:222) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:184) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.teiid.designer.runtime.ui.GenerateWarAction.run(GenerateWarAction.java:93) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) I'll attach a Model Project Set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-452) Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function.

by Van Halbert (JIRA)

Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function. ------------------------------------------------------------------------------------------------- Key: TEIIDDES-452 URL: https://jira.jboss.org/browse/TEIIDDES-452 Project: Teiid Designer Issue Type: Feature Request Reporter: Van Halbert Fundamental rework of existing MetaMatrix materialized views functionality to make mat views first class objects in the system. The changes for this feature include: 1.Moving away from the automagic creation of materialized view source/physical model and ddl scripts upon VDB deployment 2.Making mat view source/physical models explictly modeled objects in Designer tooling. 3.Support external scripts to pull data from live sources and populate mat views. 4.Support virtual procedure logic to pull data from live sources and populate mat views. This will required DDL execution capabilities such that virtual procedures can perform the swap of staged data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-532) Usability: Please add a button to the Teiid view's toolbar to allow users to create a Teiid server instance

by Paul Nittel (JIRA)

Usability: Please add a button to the Teiid view's toolbar to allow users to create a Teiid server instance ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-532 URL: https://jira.jboss.org/browse/TEIIDDES-532 Project: Teiid Designer Issue Type: Task Components: Views Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Currently the only way to create a connection to a Teiid server is to right-click inside the Teiid view's blank text field and then click the New Teiid Instance menu item which appears. There is no text to guide a user to this action. A button on the toolbar would be clearer to the users. And SWTBot would have a fighting chance. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-587) Preview Data fails when model's DTP connection profile doesn't exist anymore. Password is not set.

by Barry LaFond (JIRA)

Preview Data fails when model's DTP connection profile doesn't exist anymore. Password is not set. -------------------------------------------------------------------------------------------------- Key: TEIIDDES-587 URL: https://jira.jboss.org/browse/TEIIDDES-587 Project: Teiid Designer Issue Type: Bug Components: Data Preview Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.1 Because DTP stands alone as a Connection Profile management tool Designer can't assume that CP's will alway be there when it needs them. In addition, Model Projects, Models/VDBs will be passed around between workspaces, so again, CP's are not guarenteed to exist in DTP. The PreviewManager currently expects them to exist in order to find password info for the data source. So, need a hook between PreviewManager and Preview data action so ask users for passwords if CP does not exists for each source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-496) Corretly fix NULL string value issues with VDB Editor. In particular, JNDI Name and Description values

by Barry LaFond (JIRA)

Corretly fix NULL string value issues with VDB Editor. In particular, JNDI Name and Description values ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-496 URL: https://jira.jboss.org/browse/TEIIDDES-496 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Priority: Blocker Fix For: 7.0 VDB Editor is not handling NULL string values correctly for JNDI name and Description. The current fix addresses the problem at the wrong level (i.e. VdbModelEntry). Needs to get fixed in the UI components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-406) Design Time Role Management

by Barry LaFond (JIRA)

Design Time Role Management --------------------------- Key: TEIIDDES-406 URL: https://jira.jboss.org/jira/browse/TEIIDDES-406 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 Role management in "Metamatrix" days was done via it's console. Today, JOPR/JON provides the console-type functionality. However, the data-role management is being pushed down to design-time. So Designer needs to take this on, allow data roles (authorization/entitlements) at the column, table and model levels. In addition there needs to be a way to manage higher-level "security" roles that will be mapped to actual roles when VDB's are deployed to the server. This will required injecting these roles into the VDB for transport and eventual mapping. -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-566) Inconsistent labeling of Teiid Designer actions and "Eclipse" level contributions.

by Barry LaFond (JIRA)

Inconsistent labeling of Teiid Designer actions and "Eclipse" level contributions. ---------------------------------------------------------------------------------- Key: TEIIDDES-566 URL: https://jira.jboss.org/browse/TEIIDDES-566 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration, Views Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.1 Various parts of Teiid Designer are named/labeled in different manners. Import wizard contributions, for instance use "XXXX to Relational Source Model", or "XXXX to relational model". The "New" options are not "Teiid/Designer" specific enough to be self explanatory. Make them more consistent and descriptive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-461) VDB Editor needs framework to display context actions for selected model entries

by Barry LaFond (JIRA)

VDB Editor needs framework to display context actions for selected model entries -------------------------------------------------------------------------------- Key: TEIIDDES-461 URL: https://jira.jboss.org/browse/TEIIDDES-461 Project: Teiid Designer Issue Type: Task Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 The VDB editor provides textual place-holders for translator-name and JNDI (data source) name. TEIIDDES-404 involves providing a Deploy VDB action to a desired Teiid Server instance. To facilitate this deployment, the "translator-name" and "JNDI" names have to match names of existing Translators and Data Sources on the desired server. So the VDB Editor needs to provide the hooks/actions to allow the user to "select" these items from the desired server. The VDB Editor needs to provide a context menu on selection of a row/cell in the model entry table. Upon right-click, the "fillContextMen()" call or something like that will query the SourceHandlerExtensionManager for a list of available actions which will be contributed via the VdbSourceHandler contribution in DQP plugin. Two actions will be returned to display for the user, 1) "Select Translator" and 2) "Select Data Source". Note that during these actions, the user will first have to "pick" or "connect" to a Teiid Instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-538) DDL Importer appears to be case-sensitive and likely should not.

by Paul Nittel (JIRA)

DDL Importer appears to be case-sensitive and likely should not. ---------------------------------------------------------------- Key: TEIIDDES-538 URL: https://jira.jboss.org/browse/TEIIDDES-538 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Environment: Fedora 12, current Designer build Reporter: Paul Nittel Attachments: ImportedDDL.png, motels.ddl I was familiarizing myself with the new DDL importer and found one of the sample DDL scripts I'd found defined "customerID" and then occasionally referenced it as "customerid". This all-lower-case reference generated errors indicating the column was not defined. Changing the case of the referring column name solved the problem. The importer should not be case-sensitive and the DDL should generate models without error. (At least not this error.) DDL and a screenshot are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-267) UDF-related changes

by Barry LaFond (JIRA)

UDF-related changes ------------------- Key: TEIIDDES-267 URL: https://jira.jboss.org/jira/browse/TEIIDDES-267 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.0 Teiid 7.0 has changed their UDF-related code requiring re-integrating their new framework into Designer. FunctionLibraryManager doesn't exist anymore, FunctionLibrary has changed. 1) Investigate changes to Teiid and how Designer is supposed to handle UDF models in workspace. -- 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, 8 months

1
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010