May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1704) IllegalArgumentException getting CommandHelper.getProjectedSymbols(). getResultSetColumns() may be null

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1704: -------------------------------------- Summary: IllegalArgumentException getting CommandHelper.getProjectedSymbols(). getResultSetColumns() may be null Key: TEIIDDES-1704 URL: https://issues.jboss.org/browse/TEIIDDES-1704 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 8.2 If SQL contains CREATE VIRTUAL PROCEDURE BEGIN END, validation will result in an Illegal Arg exception because CreateProcedureCommand.getResultSetColumns() will return null and CommandHelper isn't checking for that. Need to add the check -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1703) Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1703?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1703: ----------------------------------- Fix Version/s: 8.2 Description: The new Refactor logic utilizes Eclipse's refactor/preview framework. Works GREAT. Problem is, unlike deleting folders and projects, deleting a model will result in the default behavior of deleting any and all dependent models. For a WS model, this may include XSD files, XML Files and Source models. Users can click "Preview>>" to view and deselect items for deletion, but this operation is probably NOT for the faint of heart. Suggest maybe adding some verbage/warning on the FIRST page of the wizard so user knows that DEPENDENT files will be deleted. Maybe add a "check-box" to change the default behavior to NOT delete dependent models. Affects Version/s: 8.2 Component/s: Modeling > Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1703 > URL: https://issues.jboss.org/browse/TEIIDDES-1703 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 8.2 > Reporter: Barry LaFond > Fix For: 8.2 > > > The new Refactor logic utilizes Eclipse's refactor/preview framework. Works GREAT. > Problem is, unlike deleting folders and projects, deleting a model will result in the default behavior of deleting any and all dependent models. For a WS model, this may include XSD files, XML Files and Source models. > Users can click "Preview>>" to view and deselect items for deletion, but this operation is probably NOT for the faint of heart. > Suggest maybe adding some verbage/warning on the FIRST page of the wizard so user knows that DEPENDENT files will be deleted. > Maybe add a "check-box" to change the default behavior to NOT delete dependent 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1703) Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1703: -------------------------------------- Summary: Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case Key: TEIIDDES-1703 URL: https://issues.jboss.org/browse/TEIIDDES-1703 Project: Teiid Designer Issue Type: Enhancement Reporter: Barry LaFond -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1702) VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1702?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1702. ------------------------------------ Assignee: Barry LaFond (was: Paul Richardson) Resolution: Done Fixed visitor logic to properly check for model files and to return TRUE if project or folder so children get checked. > VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1702 > URL: https://issues.jboss.org/browse/TEIIDDES-1702 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.2 > > Attachments: TestRenameModel.zip > > > Open the attached project and the build will result in VDB Warning markers that models in VDB are not found in workspace. > WorkspaceResourceFinderUtil.getProjectFileResources() is not finding any models in the project, hence the warnings. > This worked in 8.1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1702) VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1702?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1702: ----------------------------------- Attachment: TestRenameModel.zip > VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1702 > URL: https://issues.jboss.org/browse/TEIIDDES-1702 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.2 > > Attachments: TestRenameModel.zip > > > Open the attached project and the build will result in VDB Warning markers that models in VDB are not found in workspace. > WorkspaceResourceFinderUtil.getProjectFileResources() is not finding any models in the project, hence the warnings. > This worked in 8.1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1702) VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1702?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1702: ---------------------------------------- OLD Project Visitor: {code} final FileResourceCollectorVisitor visitor = new FileResourceCollectorVisitor(); if (getWorkspace() != null && getWorkspace().getRoot() != null) { final IProject[] projects = getWorkspace().getRoot().getProjects(); for (final IProject project : projects) try { project.accept(visitor); } catch (final CoreException e) { // do nothing } } {code} New Project visitor: {code} FileResourceCollectorVisitor visitor = new FileResourceCollectorVisitor() { @Override public boolean visit(IResource resource) { if (! resource.exists() || resource.getType() != IResource.FILE || getResourceFilter().accept(resource)) return false; if (ModelUtil.isXsdFile(resource)) return false; XMIHeader header = ModelUtil.getXmiHeader(resource); if (header != null && stringifiedUuid.equals(header.getUUID())) addResource(resource); return true; } }; {code} > VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1702 > URL: https://issues.jboss.org/browse/TEIIDDES-1702 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.2 > > > Open the attached project and the build will result in VDB Warning markers that models in VDB are not found in workspace. > WorkspaceResourceFinderUtil.getProjectFileResources() is not finding any models in the project, hence the warnings. > This worked in 8.1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1702) VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1702?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1702: ----------------------------------- Assignee: Paul Richardson > VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1702 > URL: https://issues.jboss.org/browse/TEIIDDES-1702 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.2 > > > Open the attached project and the build will result in VDB Warning markers that models in VDB are not found in workspace. > WorkspaceResourceFinderUtil.getProjectFileResources() is not finding any models in the project, hence the warnings. > This worked in 8.1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1702) VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1702: -------------------------------------- Summary: VdbUtil.validateVdbModelsInWorkspace() failing because WorkspaceResourceFinderUtil does not find any models in project via visitor Key: TEIIDDES-1702 URL: https://issues.jboss.org/browse/TEIIDDES-1702 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 8.2 Reporter: Barry LaFond Priority: Critical Fix For: 8.2 Open the attached project and the build will result in VDB Warning markers that models in VDB are not found in workspace. WorkspaceResourceFinderUtil.getProjectFileResources() is not finding any models in the project, hence the warnings. This worked in 8.1 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1348) Investigate Adding Additional VDB Properties

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1348?page=com.atlassian.jira.plu... ] Dan Florian commented on TEIIDDES-1348: --------------------------------------- Would you like the VDB editor to accept *any* VDB property name (generic solution)? Or do you want an enumerated list of known properties? The vdb.xml schema allows any property so seems like former solution would be best. If a generic approach is taken, the value would always be a string and be required to be non-empty (no other validation). We could also provide some known property names to choose from (like the query timeout). > Investigate Adding Additional VDB Properties > -------------------------------------------- > > Key: TEIIDDES-1348 > URL: https://issues.jboss.org/browse/TEIIDDES-1348 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 7.7 > Reporter: Ted Jones > Assignee: Dan Florian > Priority: Minor > Fix For: 8.2 > > > We currently allow the user to set the query timeout on the VDB. We had a request from the field to see if there were other properties we could set at that level and add to the tab. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1701) Deleting model open in dirty editor results in org.eclipse.swt.SWTException: Invalid thread access

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1701: -------------------------------------- Summary: Deleting model open in dirty editor results in org.eclipse.swt.SWTException: Invalid thread access Key: TEIIDDES-1701 URL: https://issues.jboss.org/browse/TEIIDDES-1701 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.2 Reporter: Barry LaFond Fix For: 8.2 1) Open Model in Editor 2) edit the model to make dirty (move object in diagram) 3) Select Model in Explorer and click DELETE 4) Get exception: Root exception: org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4361) at org.eclipse.swt.SWT.error(SWT.java:4276) at org.eclipse.swt.SWT.error(SWT.java:4247) at org.eclipse.swt.widgets.Display.error(Display.java:1157) at org.eclipse.swt.widgets.Display.checkDevice(Display.java:749) at org.eclipse.swt.widgets.Display.getShells(Display.java:1939) at org.eclipse.ui.internal.progress.ProgressManagerUtil.getModalShellExcluding(ProgressManagerUtil.java:286) at org.eclipse.ui.internal.progress.ProgressManagerUtil.getDefaultParent(ProgressManagerUtil.java:340) at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:950) at org.eclipse.ui.internal.SaveableHelper.waitForBackgroundSaveJobs(SaveableHelper.java:463) at org.eclipse.ui.internal.SaveablesList.promptForSaving(SaveablesList.java:466) at org.eclipse.ui.internal.Workbench.saveAll(Workbench.java:3291) at org.teiid.designer.ui.common.util.UiUtil.saveDirtyEditors(UiUtil.java:534) at org.teiid.designer.ui.refactor.AbstractResourcesRefactoring.closeDirtyEditors(AbstractResourcesRefactoring.java:163) at org.teiid.designer.ui.refactor.delete.DeleteResourcesRefactoring.checkInitialConditions(DeleteResourcesRefactoring.java:138) -- 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, 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 May 2013