[JBoss JIRA] (TEIIDDES-2620) Add validation rule to check for circular dependencies in view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2620?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2620:
--------------------------------------
Assignee: Dan Florian
> Add validation rule to check for circular dependencies in view models
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2620
> URL: https://issues.jboss.org/browse/TEIIDDES-2620
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 9.1, 9.0.3
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Fix For: 9.2, 9.0.4
>
> Attachments: CircularDependencyTest.zip
>
>
> Designer currently allows defining transformations (view models) that depend on each other.
> Need to add a validation rule (ERROR) that will detect this circular dependency.
> The result is some actions like *delete* table/column, etc.. will end up in a StackOverflowException here: at org.teiid.designer.core.workspace.WorkspaceResourceFinderUtil.getResourcesThatUse(WorkspaceResourceFinderUtil.java:747)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2616) Additional performance improvements in admin factory
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2616?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2616.
------------------------------------
Labels: commit-9.0.x commit-master (was: commit-master)
Resolution: Done
> Additional performance improvements in admin factory
> -----------------------------------------------------
>
> Key: TEIIDDES-2616
> URL: https://issues.jboss.org/browse/TEIIDDES-2616
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 9.0.2, 9.0.3
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: commit-master, commit-9.0.x
> Fix For: 9.2, 9.0.4
>
>
> There were a couple of issues that arose with testing the changes in TEIIDDES-2592 in Komodo Admin8Factory. There were some issues with certain connection factories that didn't have properties that ended up stopping loading of data source definitions.
> So needed to catch intermediate exceptions and allow caching/loading of what data sources were on the server. This lead to caching DS names and XA-DS names separately, similar to resource names.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2612) Cannot delete a model project with a read-only model in it.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2612?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2612 at 8/24/15 12:20 PM:
------------------------------------------------------------------
master: https://github.com/Teiid-Designer/teiid-designer/commit/c648e538cd953db18...
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/827bb38ed996dd2fb...
Added check-box options to DDL importer and Teiid Connection Importer where default behavior if TEiid DDL is to remove redundant Unique Constraints (i.e. if PK's already exist for the same columns)
was (Author: blafond):
master: https://github.com/Teiid-Designer/teiid-designer/commit/c648e538cd953db18...
Added check-box options to DDL importer and Teiid Connection Importer where default behavior if TEiid DDL is to remove redundant Unique Constraints (i.e. if PK's already exist for the same columns)
> Cannot delete a model project with a read-only model in it.
> -----------------------------------------------------------
>
> Key: TEIIDDES-2612
> URL: https://issues.jboss.org/browse/TEIIDDES-2612
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 9.0, 9.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.2, 9.0.4
>
> Attachments: 0001-TEIIDES-2612-Refactor-deleting-response-to-related-r.patch, AbstractRefactorAction.patch, DeleteResourceRefactoring.patch, ModelExplorerResourceNavigator.patch
>
>
> I set up a 2 projects with a single model in it. Project 1 has a read-only -model, Project 2 has a writeable model.
> I can delete Project 2, but Project 1 sends up a error message dialog that it can't delete because the project has a read-only file in it.
> Looking at DeleteResourcesRefactoring.checkResource(), it starts with checking if the resource is in the selected list. If not selected, it'll be an ERROR if a child resources is READ-ONLY, rather than a WARNING.
> Further down the method it checks for read-only state of the resource and will set the message.
> Problem is the Selected/Top-level Project should determine the severity of the read-only check. At most, the message should be an OK/Warning dialog to ask the user "Read-only resources found... do you still wish to delete?"
> adding a method to check that *allProjectsSelected()* and switching the ERROR read-only status to WARNING at the start of the method seems to work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months