[
https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu...
]
Johnathon Lee updated TEIIDDES-2120:
------------------------------------
Description:
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
was:
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
and gets this:
http://pastebin.test.redhat.com/203593
<jolee> ^^^ is this driven by a changed design decision (it used to be allowed), or
should I pursue as a bug?
<blafond> jolee: it's a bug and it's not. VDB XML is defined such that the
model elements are named using the model names without extensions. We've been adding
XSD files to VDB's for quite some time and treating them as "model
elements".... The SAX parser logic barfs when 2 nodes have identical names.
<blafond> jolee: It's been that way for some time (years?) and only recently
been identified as an issue
<jolee> blafond: user states it worked in 5.3, was the path used as part of the
identifier previously?
* tejones (~tejones(a)68.177.128.179) has joined #teiiddesigner
<blafond> jolee: I'd have to check it out....
<jolee> blafond: that's why I'm asking, I'm getting a lot of hits when
I grep the git log and check the changes in the files in the stacktrace.
<jolee> blafond: but what I'm hearing is that they *should* be able to do this.
<blafond> jolee: Just verified with a 7.7.x designer that 2 Model elements could
have same name and the VDB saved just fine
* vhalbert has quit (Ping timeout: 2
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
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 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