[JBoss JIRA] (TEIIDDES-1945) Unable to deploy and test a VDB with same name models with different extensions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1945?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-1945:
------------------------------------
Location of the xsds are causing unexpected failures in schema resolution of models. The Xsd files, while dealt differently from models, must be located in the same location as they are in the project hierarchy to preserve the efficacy of import statement locations.
> Unable to deploy and test a VDB with same name models with different extensions
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1945
> URL: https://issues.jboss.org/browse/TEIIDDES-1945
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation, VDB & Execution
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.5, 8.3.3
>
> Attachments: duplicate-file-names-problems-view.png, RecursiveXMLTest.tar.gz
>
>
> Followed the E2eRecursiveXmlTextSourceTestScript_Teiid7.odt test and created various models. When it came to creating the VDB on step 5.23 the vdb creation failed with below exception.
> There is no way to further proceed with the test without a VDB. I will also attach the MPS.
> Employees.xmi and Emloyees.xmi are both entered as "Employee" in the VDB's model name element. SAX parser validation will fail since the element names are not unique.
> {code}
> java.lang.RuntimeException: javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".]
> at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50)
> at org.teiid.designer.vdb.Vdb.save(Vdb.java:919)
> at org.teiid.designer.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:1768)
> at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:150)
> at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1818)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1815)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:263)
> at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:155)
> at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3769)
> at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3782)
> at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:53)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".]
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243)
> at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75)
> at org.teiid.designer.vdb.Vdb$4.tryToDo(Vdb.java:948)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> ... 60 more
> Caused by: org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:423)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3188)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$UniqueValueStore.checkDuplicateValues(XMLSchemaValidator.java:3823)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$ValueStoreBase.addValue(XMLSchemaValidator.java:3549)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.Field$Matcher.matched(Field.java:178)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.XPathMatcher.startElement(XPathMatcher.java:331)
> at com.sun.org.apache.xerces.internal.impl.xs.identity.Selector$Matcher.startElement(Selector.java:225)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2083)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:711)
> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:551)
> at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
> at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113)
> at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:274)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:663)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:306)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:561)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:290)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:462)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:314)
> ... 64 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2209:
----------------------------------------
K. this makes a little more sense than TEIIDDES-1846.
We could an an option in the DDL Importer when importing a View with no SQL AND a view with one or more columns like *Generate Default SQL* and give an example similar to above.
> anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2209
> URL: https://issues.jboss.org/browse/TEIIDDES-2209
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Tom Johnston
> Fix For: 8.6
>
> Attachments: order_test_ddl.txt
>
>
> I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
> If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
> My proposal is to generate SQL using the column metadata for the view itself.
> For example... I've attached a simple ddl but for order_header it'd be like:
> SELECT null AS Order_header_id, null AS order_header_name
> The primary purpose is to make the model deploy-able immediately.
> I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2209:
-----------------------------------
Component/s: Import/Export
> anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2209
> URL: https://issues.jboss.org/browse/TEIIDDES-2209
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Tom Johnston
> Fix For: 8.6
>
> Attachments: order_test_ddl.txt
>
>
> I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
> If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
> My proposal is to generate SQL using the column metadata for the view itself.
> For example... I've attached a simple ddl but for order_header it'd be like:
> SELECT null AS Order_header_id, null AS order_header_name
> The primary purpose is to make the model deploy-able immediately.
> I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2209:
-----------------------------------
Fix Version/s: 8.6
> anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2209
> URL: https://issues.jboss.org/browse/TEIIDDES-2209
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Fix For: 8.6
>
> Attachments: order_test_ddl.txt
>
>
> I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
> If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
> My proposal is to generate SQL using the column metadata for the view itself.
> For example... I've attached a simple ddl but for order_header it'd be like:
> SELECT null AS Order_header_id, null AS order_header_name
> The primary purpose is to make the model deploy-able immediately.
> I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ]
Tom Johnston updated TEIIDDES-2209:
-----------------------------------
Summary: anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable (was: anytime view models are created (I.e. DDL import as VIew) allow checkbox to make default transformation so that the model is deployable)
> anytime view models are created (I.e. DDL import as View) allow checkbox to make default transformation so that the model is deployable
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2209
> URL: https://issues.jboss.org/browse/TEIIDDES-2209
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Attachments: order_test_ddl.txt
>
>
> I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
> If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
> My proposal is to generate SQL using the column metadata for the view itself.
> For example... I've attached a simple ddl but for order_header it'd be like:
> SELECT null AS Order_header_id, null AS order_header_name
> The primary purpose is to make the model deploy-able immediately.
> I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as VIew) allow checkbox to make default transformation so that the model is deployable
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2209?page=com.atlassian.jira.plu... ]
Tom Johnston updated TEIIDDES-2209:
-----------------------------------
Attachment: order_test_ddl.txt
referenced within description.
> anytime view models are created (I.e. DDL import as VIew) allow checkbox to make default transformation so that the model is deployable
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2209
> URL: https://issues.jboss.org/browse/TEIIDDES-2209
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Tom Johnston
> Attachments: order_test_ddl.txt
>
>
> I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
> If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
> My proposal is to generate SQL using the column metadata for the view itself.
> For example... I've attached a simple ddl but for order_header it'd be like:
> SELECT null AS Order_header_id, null AS order_header_name
> The primary purpose is to make the model deploy-able immediately.
> I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2209) anytime view models are created (I.e. DDL import as VIew) allow checkbox to make default transformation so that the model is deployable
by Tom Johnston (JIRA)
Tom Johnston created TEIIDDES-2209:
--------------------------------------
Summary: anytime view models are created (I.e. DDL import as VIew) allow checkbox to make default transformation so that the model is deployable
Key: TEIIDDES-2209
URL: https://issues.jboss.org/browse/TEIIDDES-2209
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Tom Johnston
Attachments: order_test_ddl.txt
I have mentioned this before but now that DDL import can generate view models (the only mechanism I can see to bring in logical/conceptual models from other tools like PowerDesigner etc)
If the model is successful in that it brings all components it is still not a valid model to deploy to a vdb and start work against.
My proposal is to generate SQL using the column metadata for the view itself.
For example... I've attached a simple ddl but for order_header it'd be like:
SELECT null AS Order_header_id, null AS order_header_name
The primary purpose is to make the model deploy-able immediately.
I'd also like to see this 'feature' at the Model-->Generate stubs when right clicking the model.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2120:
-----------------------------------
Priority: Blocker (was: Major)
> unable to reference same name .xsd when saving .vdb
> ---------------------------------------------------
>
> Key: TEIIDDES-2120
> URL: https://issues.jboss.org/browse/TEIIDDES-2120
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Johnathon Lee
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.5, 8.3.3
>
> Attachments: Books_2120.vdb, Books_TEIIDDES_2120.zip
>
>
> User can no longer add same name .xsd to a vdb (name same, location(s) different).
> Results in:
> java.lang.RuntimeException: javax.xml.bind.UnmarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException; lineNumber: 61; columnNumber: 168; Duplicate unique value [<name>] declared for identity constraint of element "vdb".]
> at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50)
> at org.teiid.designer.vdb.VdbUtil.getVdbManifest(VdbUtil.java:178)
> at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:120)
> at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:267)
> at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:656)
> at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:895)
> at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:466)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
> Caused by: javax.xml.bind.UnmarshalException
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ]
Paul Richardson reopened TEIIDDES-2120:
---------------------------------------
Location of the xsds are causing unexpected failures in schema resolution of models. The Xsd files, while dealt differently from models, must be located in the same location as they are in the project hierarchy to preserve the efficacy of import statement locations.
> unable to reference same name .xsd when saving .vdb
> ---------------------------------------------------
>
> Key: TEIIDDES-2120
> URL: https://issues.jboss.org/browse/TEIIDDES-2120
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3
> Reporter: Johnathon Lee
> Assignee: Paul Richardson
> Fix For: 8.5, 8.3.3
>
> Attachments: Books_2120.vdb, Books_TEIIDDES_2120.zip
>
>
> User can no longer add same name .xsd to a vdb (name same, location(s) different).
> Results in:
> java.lang.RuntimeException: javax.xml.bind.UnmarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException; lineNumber: 61; columnNumber: 168; Duplicate unique value [<name>] declared for identity constraint of element "vdb".]
> at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50)
> at org.teiid.designer.vdb.VdbUtil.getVdbManifest(VdbUtil.java:178)
> at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:120)
> at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:267)
> at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:656)
> at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:895)
> at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:466)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
> Caused by: javax.xml.bind.UnmarshalException
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (TEIIDDES-2208) Column layout issue in RelationalEditorPanel
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2208:
--------------------------------------
Summary: Column layout issue in RelationalEditorPanel
Key: TEIIDDES-2208
URL: https://issues.jboss.org/browse/TEIIDDES-2208
Project: Teiid Designer
Issue Type: Bug
Components: Dialogs
Affects Versions: 8.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.5
The label and text entry widgets are not horizontally aligned in the RelationalEditorPanel's top panel.
Model File and model name are aligned vertically rather than side-by-side.
Probably a simple column value missing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months