[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1417.
---------------------------------------
Resolution: Won't Fix
> Problems After Renaming Model Which Is A Dependency For Other Models
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1417
> URL: https://issues.jboss.org/browse/TEIIDDES-1417
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Dan Florian
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs:
> Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>"
> Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur.
> The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found.
> See forum post for more details.
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1417:
-------------------------------------------
Isolating the commits to backport them to 7.7.x is complex and far too prone to errors. The error can be worked around by cleaning the project then rebuilding. Thus, an upgrade to 8.2 is recommended when its released.
> Problems After Renaming Model Which Is A Dependency For Other Models
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1417
> URL: https://issues.jboss.org/browse/TEIIDDES-1417
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Dan Florian
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs:
> Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>"
> Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur.
> The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found.
> See forum post for more details.
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1440) Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1440?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1440.
---------------------------------------
Resolution: Out of Date
Since teiid is now tied into its parent jboss server using JBossTools, its startup/shutdown is no longer independent. Thus, shutting down the parent jboss server shuts down teiid.
Connection/disconnection is available using the UI.
> Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1440
> URL: https://issues.jboss.org/browse/TEIIDDES-1440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Eclipse Integration
> Affects Versions: 7.6
> Environment: JBDS 5 Beta 3 on Fedora 16
> Reporter: Joel Tosi
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> I connect to a remote Teiid Server (EDS) all is fine. I deploy, no issue. I then go to stop the server (right click on server, stop) and the log updates showing the server is shutting down, but never completes. In eclipse, it appears that the server is still running though I can verify that the process is no longer up.
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1739) Refactor DdlImporter into dialect-specific processors.
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1739:
--------------------------------------
Summary: Refactor DdlImporter into dialect-specific processors.
Key: TEIIDDES-1739
URL: https://issues.jboss.org/browse/TEIIDDES-1739
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 8.2
Reporter: Barry LaFond
Fix For: 8.2
Current DdlImporter handles multiple DDL dialects, including the new Teiid-related modifications.
Refactor this class to allow dialect-specific implementations of an Interface that can be handed an AstNode and either process the node, or not.
Also need to allow for handing off Teiid-DDL Options to the Extension Assistants to inject the extension properties into the models. This is currently not handled correctly
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1738) Data role editor modifications can result in duplicate roles being generated.
by Marc Shirley (JIRA)
Marc Shirley created TEIIDDES-1738:
--------------------------------------
Summary: Data role editor modifications can result in duplicate roles being generated.
Key: TEIIDDES-1738
URL: https://issues.jboss.org/browse/TEIIDDES-1738
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.7.3
Environment: This appears to be more prominent on Windows, but duplicate roles have been observed on both Windows and Linux machines.
Reporter: Marc Shirley
Editing the data roles through the VDB data roles editor can result in duplicate roles being generated, or the roles not being saved correctly in the current active copy of the role. Observed effects:
1) duplicate roles appearing
2) permissions being reset after VDB synchronization
3) duplicate roles appearing after attempting to delete a role
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1548:
------------------------------------------
Column masking is also now possible, so in addition to a condition (a boolean expression) you can also specify a mask expression for permission against a column (where the type of the expression should match the column being masked).
> Add GUI handling for permission conditions
> ------------------------------------------
>
> Key: TEIIDDES-1548
> URL: https://issues.jboss.org/browse/TEIIDDES-1548
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Steven Hawkins
>
> A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose:
> <permission>
> <resource-name>...</resource-name>
> <condition>sql</condition>
> ...
> </permission>
> The sql should resolve against the resource specified, ideally designer would check that as well.
> See TEIID-2311 and the reference for how these conditions are applied.
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1480) Add handling for language support in vdbs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1480?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1480:
------------------------------------------
> Would these languages be defined as part of other JBoss Tools/JBDS developer use-cases?
Anything is possible. With minor effort you can turn this mechanism into a way to call out to other JBoss technologies, such as rules. I'm not sure however what other use-cases rely on ScriptEngine integration.
> Seems like this is another case where users might want to define these "allowed-languages" outside of a VDB and re-use them by selecting them in a VDB Editor?
Possibly. More than likely any environment using additional script languages will be using a consistent set of them.
> Add handling for language support in vdbs
> -----------------------------------------
>
> Key: TEIIDDES-1480
> URL: https://issues.jboss.org/browse/TEIIDDES-1480
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 8.2
>
>
> Teiid 8.2 added support for an OBJECTTABLE table function TEIID-2141. To use the OBJECTTABLE construct, a vdb property allowed-languages and if applicable the data role language permission needs granted. See the reference https://docs.jboss.org/author/display/TEIID/XML+Definition for an example.
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1674) DDL Importer - does not handle extension properties
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1674:
-----------------------------------
Summary: DDL Importer - does not handle extension properties (was: DDL Importer - does not handle Teiid DDL Function Procedures)
Description:
The DDL Importer currently does not fully support import of Function Procedures from Teiid DDL. An example:
CREATE VIRTUAL FUNCTION F4(
flag boolean,
msg varchar
) RETURNS varchar
OPTIONS (
CATEGORY 'misc',
DETERMINISM 'DETERMINISTIC',
"NULL-ON-NULL" 'true',
JAVA_CLASS 'foo',
JAVA_METHOD 'bar'
);
The current DDL Importer cannot easily set properties which are implemented as extension properties. Examples are CATEGORY, JAVA_CLASS, JAVA_METHOD in the above example.
We should look into re-working the DDL Importer to use Barry's framework for creating relational objects. I believe that framework has built in support for the extension properties.
Importing for Salesforce connection will also not work, nor a simple DB where Native Query values are set on tables
was:
The DDL Importer currently does not fully support import of Function Procedures from Teiid DDL. An example:
CREATE VIRTUAL FUNCTION F4(
flag boolean,
msg varchar
) RETURNS varchar
OPTIONS (
CATEGORY 'misc',
DETERMINISM 'DETERMINISTIC',
"NULL-ON-NULL" 'true',
JAVA_CLASS 'foo',
JAVA_METHOD 'bar'
);
The current DDL Importer cannot easily set properties which are implemented as extension properties. Examples are CATEGORY, JAVA_CLASS, JAVA_METHOD in the above example.
We should look into re-working the DDL Importer to use Barry's framework for creating relational objects. I believe that framework has built in support for the extension properties.
> DDL Importer - does not handle extension properties
> ---------------------------------------------------
>
> Key: TEIIDDES-1674
> URL: https://issues.jboss.org/browse/TEIIDDES-1674
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Fix For: 8.2
>
>
> The DDL Importer currently does not fully support import of Function Procedures from Teiid DDL. An example:
> CREATE VIRTUAL FUNCTION F4(
> flag boolean,
> msg varchar
> ) RETURNS varchar
> OPTIONS (
> CATEGORY 'misc',
> DETERMINISM 'DETERMINISTIC',
> "NULL-ON-NULL" 'true',
> JAVA_CLASS 'foo',
> JAVA_METHOD 'bar'
> );
> The current DDL Importer cannot easily set properties which are implemented as extension properties. Examples are CATEGORY, JAVA_CLASS, JAVA_METHOD in the above example.
> We should look into re-working the DDL Importer to use Barry's framework for creating relational objects. I believe that framework has built in support for the extension properties.
> Importing for Salesforce connection will also not work, nor a simple DB where Native Query values are set on tables
--
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
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1658) NPE Viewing Transformation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1658?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1658:
-----------------------------------
Attachment: TpcrOrderChecking.wsdl
> NPE Viewing Transformation
> --------------------------
>
> Key: TEIIDDES-1658
> URL: https://issues.jboss.org/browse/TEIIDDES-1658
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.2
>
> Attachments: TpcrOrderChecking.wsdl
>
>
> Viewing/Editing a transformation for a web service model generated from WSDL without automatically generating the XML Document model results in the following NPE:
> java.lang.NullPointerException
> at java.util.AbstractCollection.addAll(AbstractCollection.java:303)
> at org.teiid.designer.query.sql.lang.util.CommandHelper.getProjectedSymbols(CommandHelper.java:33)
> at org.teiid.designer.transformation.util.TransformationSqlHelper.getProjectedSymbolNames(TransformationSqlHelper.java:1253)
> at org.teiid.designer.transformation.util.TransformationMappingHelper.compareQueryTargetAndSQLOutput(TransformationMappingHelper.java:201)
> at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setMessageDisplayForValidSQL(TransformationObjectEditorPage.java:2956)
> at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setEditorMessage(TransformationObjectEditorPage.java:1436)
> at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setEditorContent(TransformationObjectEditorPage.java:1022)
> at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.edit(TransformationObjectEditorPage.java:839)
> at org.teiid.designer.webservice.ui.editor.OperationObjectEditorPage.edit(OperationObjectEditorPage.java:410)
> at org.teiid.designer.ui.editors.ModelObjectEditorPanel.activateModelObjectEditor(ModelObjectEditorPanel.java:152)
> at org.teiid.designer.ui.editors.MultiPageModelEditor.editModelObject(MultiPageModelEditor.java:391)
> at org.teiid.designer.webservice.ui.editor.OperationEditorPage.openObjectEditor(OperationEditorPage.java:360)
> at org.teiid.designer.webservice.ui.editor.OperationEditorPage.updateUi(OperationEditorPage.java:465)
> at org.teiid.designer.webservice.ui.editor.OperationEditorPage$1.widgetSelected(OperationEditorPage.java:137)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
> at org.teiid.designer.ui.editors.MultiPageModelEditor.selectPage(MultiPageModelEditor.java:876)
> at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:181)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
--
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
11 years, 1 month