[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
[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
[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
[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
[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