[JBoss JIRA] Created: (TEIIDDES-688) Closing project and saving dirty editor results in ResourceException
by Barry LaFond (JIRA)
Closing project and saving dirty editor results in ResourceException
--------------------------------------------------------------------
Key: TEIIDDES-688
URL: https://jira.jboss.org/browse/TEIIDDES-688
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Reporter: Barry LaFond
Assignee: Dan Florian
Fix For: 7.1.1
With Preview Data option enabled....
1) With open dirty editor (requires save)
2) Close it's project
3) Requires Save Dialog is presented, choose OK
4) Error stack trace below...
org.eclipse.core.internal.resources.ResourceException: Resource '/SimpleDatatypesTest' is not open.
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:137)
at org.eclipse.core.internal.resources.File.create(File.java:123)
at org.eclipse.core.internal.resources.File.create(File.java:196)
at org.teiid.designer.runtime.preview.jobs.CreatePreviewVdbJob.runImpl(CreatePreviewVdbJob.java:126)
at org.teiid.designer.runtime.preview.jobs.WorkspacePreviewVdbJob.runInWorkspace(WorkspacePreviewVdbJob.java:126)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Guessing the close project thread is completing before the CreatePreviewVdbJob gets to check it's project status.
--
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, 5 months
[JBoss JIRA] Created: (TEIIDDES-696) Clicking "Restore Default" in Editor Prefs deletes entries from list of tables
by Paul Nittel (JIRA)
Clicking "Restore Default" in Editor Prefs deletes entries from list of tables
------------------------------------------------------------------------------
Key: TEIIDDES-696
URL: https://jira.jboss.org/browse/TEIIDDES-696
Project: Teiid Designer
Issue Type: Bug
Components: Dialogs
Affects Versions: 7.1.1
Environment: Windows, JBDS 4.0 Beta 1
Reporter: Paul Nittel
Fix For: 7.1.1
I was testing the Windows > Preferences > Teiid Designer > Editor - Table Tab and went to restore the default values, after reordering columns in the Columns table. When I did so, the entry for the Columns table vanished! Tried it again on a couple of other table entries and they, too, were removed from the list. I clicked OK. Looked again and they were gone. Restarted the Designer and they were still gone.
Had I canceled, it would have been OK, but it shouldn't have happened anyway.
Happy Halloween? (Screenshots are attached. No exceptions were noted.)
--
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, 5 months
[JBoss JIRA] Resolved: (TEIIDDES-68) In Procedure, once an alias is established, must use alias, not fully qualified name
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-68?page=com.atlassian.jira.plugin.... ]
Steven Hawkins resolved TEIIDDES-68.
------------------------------------
Resolution: Rejected
I think the expectation here is wrong. The SQL is not valid. Once aliases are used, column references must use the correlation name.
> In Procedure, once an alias is established, must use alias, not fully qualified name
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-68
> URL: https://jira.jboss.org/browse/TEIIDDES-68
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 6.0.0
> Reporter: Paul Nittel
> Assignee: Steven Hawkins
> Fix For: Future
>
>
> I was using the Northwind DB (for a change) and created a procedure that returns the orders where the quantity ordered is more than the available units in stock. I started by creating the criteria using the Criteria Builder, added aliases to the FROM, then defined the specific columns (was '*' before that). I wound up with:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT od.OrderID, p.ProductName, od.Quantity, p.UnitsInStock FROM NWind.Order_Details AS od, NWind.Products AS p WHERE (NWind.Order_Details.ProductID = NWind.Products.ProductID) AND (NWind.Order_Details.Quantity > NWind.Products.UnitsInStock);
> END
> This won't validate, because, "Resolver Error: Symbol NWind.Order_Details.ProductID is specified with an unknown group context". If I change the criteria to use the 'od' and 'p' aliases, it'll validate. Seems like the use of fully qualified names should be valid.
--
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, 5 months
[JBoss JIRA] Created: (TEIIDDES-698) MarshalException when saving VDB with both "other" files and data roles
by Paul Nittel (JIRA)
MarshalException when saving VDB with both "other" files and data roles
-----------------------------------------------------------------------
Key: TEIIDDES-698
URL: https://jira.jboss.org/browse/TEIIDDES-698
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Environment: Windows, JBDS 4.0 Beta 1
Reporter: Paul Nittel
Fix For: 7.1.1
If I have a VDB which contains both data roles and an "other" type file, I get an exception like this:
Warning 2010-10-29 14:09:02.828 Save Failed
java.lang.RuntimeException: javax.xml.bind.MarshalException
- with linked exception:
[org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'data-role'. One of '{entry}' is expected.]
at com.metamatrix.core.modeler.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:75)
at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:48)
at org.teiid.designer.vdb.Vdb.save(Vdb.java:402)
at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:877)
at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151)
at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:277)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2600)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:285)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:264)
at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156)
at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1369)
at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3334)
at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3347)
at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:76)
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$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: javax.xml.bind.MarshalException
- with linked exception:
[org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'data-role'. One of '{entry}' is expected.]
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(Unknown Source)
at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(Unknown Source)
at org.teiid.designer.vdb.Vdb$2.tryToDo(Vdb.java:431)
at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:38)
... 45 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'data-role'. One of '{entry}' is expected.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(Unknown Source)
at org.xml.sax.helpers.XMLFilterImpl.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(Unknown Source)
... 50 more
--
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, 5 months
[JBoss JIRA] Commented: (TEIIDDES-68) In Procedure, once an alias is established, must use alias, not fully qualified name
by Barry LaFond (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-68?page=com.atlassian.jira.plugin.... ]
Barry LaFond commented on TEIIDDES-68:
--------------------------------------
Steve,
Could you take a quick look and see if this JIRA is still valid? Thx.
> In Procedure, once an alias is established, must use alias, not fully qualified name
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-68
> URL: https://jira.jboss.org/browse/TEIIDDES-68
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 6.0.0
> Reporter: Paul Nittel
> Assignee: Steven Hawkins
> Fix For: Future
>
>
> I was using the Northwind DB (for a change) and created a procedure that returns the orders where the quantity ordered is more than the available units in stock. I started by creating the criteria using the Criteria Builder, added aliases to the FROM, then defined the specific columns (was '*' before that). I wound up with:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT od.OrderID, p.ProductName, od.Quantity, p.UnitsInStock FROM NWind.Order_Details AS od, NWind.Products AS p WHERE (NWind.Order_Details.ProductID = NWind.Products.ProductID) AND (NWind.Order_Details.Quantity > NWind.Products.UnitsInStock);
> END
> This won't validate, because, "Resolver Error: Symbol NWind.Order_Details.ProductID is specified with an unknown group context". If I change the criteria to use the 'od' and 'p' aliases, it'll validate. Seems like the use of fully qualified names should be valid.
--
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, 5 months
[JBoss JIRA] Assigned: (TEIIDDES-68) In Procedure, once an alias is established, must use alias, not fully qualified name
by Barry LaFond (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-68?page=com.atlassian.jira.plugin.... ]
Barry LaFond reassigned TEIIDDES-68:
------------------------------------
Assignee: Steven Hawkins
> In Procedure, once an alias is established, must use alias, not fully qualified name
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-68
> URL: https://jira.jboss.org/browse/TEIIDDES-68
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 6.0.0
> Reporter: Paul Nittel
> Assignee: Steven Hawkins
> Fix For: Future
>
>
> I was using the Northwind DB (for a change) and created a procedure that returns the orders where the quantity ordered is more than the available units in stock. I started by creating the criteria using the Criteria Builder, added aliases to the FROM, then defined the specific columns (was '*' before that). I wound up with:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT od.OrderID, p.ProductName, od.Quantity, p.UnitsInStock FROM NWind.Order_Details AS od, NWind.Products AS p WHERE (NWind.Order_Details.ProductID = NWind.Products.ProductID) AND (NWind.Order_Details.Quantity > NWind.Products.UnitsInStock);
> END
> This won't validate, because, "Resolver Error: Symbol NWind.Order_Details.ProductID is specified with an unknown group context". If I change the criteria to use the 'od' and 'p' aliases, it'll validate. Seems like the use of fully qualified names should be valid.
--
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, 5 months