[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 commented on TEIIDDES-2120:
-------------------------------------------
The offending constraint was added to the [vdb-deployer schema|https://github.com/Teiid-Designer/teiid-designer/blob/8.3.x/plugin...] for commit ["TEIIDDES-1209 upgraded Teiid jars to 8.1 Beta1"|https://github.com/Teiid-Designer/teiid-designer/commit/1e044a9063641fca4a1db0bbb61176d8506bd13d].
Specifically, this added the following schema constraint:
{code:xml}
<xs:unique name="modelNameUnique">
<xs:selector xpath="model"/>
<xs:field xpath="@name"/>
</xs:unique>
{code}
This constraint is used by the java's xerces marshaller and validator to check whether each model in the vdb has an unique name.
By changing it to the following it is possible to allow models from different directories to be added to the vdb:
{code:xml}
<xs:unique name="modelNameUnique">
<xs:selector xpath="model"/>
<xs:field xpath="@name"/>
<xs:field xpath="@path"/>
</xs:unique>
{code}
The question remains where do the rules for vdb-deployer.xsd come from, ie. are these imported from teiid? If the answer is yes then by allowing duplicate names in the vdb client-side, are we not just moving the problem server-side when the vdb is deployed?
> 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
>
>
> 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
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2094:
----------------------------------------
Now that we can get Property Definitions from the API... not sure what to do with that data. I see you are defining these properties view java @annotation attributes.
The application of extension properties to EMF (tags referencing actual objects) objects is pretty straight forward, but there also has to be some mapping between the Teiid property definitions and their target EMF object types.
* The extension properties coming from the Teiid runtime define *owner* objects like: *org.teiid.metadata.Column*
* In Designer, these relational objects are defined differently: *org.teiid.designer.metamodels.relational.impl.ColumnImpl*
However, without persisting the entire set of property definitions (either in the model on in the Designer workspace) it'd be impossible to re-edit a model and change the extension property values. There has to be a "schema- like- definition somewhere (aka MED) that is the frame of reference to make this possible.
So Designer options would be to create another type of MED OR somehow convert the runtime ext. properties into a MED.
Seems to me that we're bookkeeping extension properties using 2 methodologies and ... that we're missing something here in our design(s).
> Support for dynamic extension metadata
> ---------------------------------------
>
> Key: TEIIDDES-2094
> URL: https://issues.jboss.org/browse/TEIIDDES-2094
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Ramesh Reddy
> Priority: Critical
>
> Currently when Teiid core implements a new translator or customer/user implements a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it.
> With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator.
> Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server.
> I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties.
> Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them.
--
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
10 years, 5 months
[JBoss JIRA] (TEIIDDES-1782) DDL import wizard - add better control over selection of imported objects
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1782?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1782:
----------------------------------------
The DDL is eventually parsed into *Statements* which represent high-level schema objects (TABLE, VIEW, PROCEDURE etc..). We could insert a check-box table viewer that displayed each *statement* with *type* and *name*.
Issues would probably be in REFERENCEs related to PK/FK/UC and even SQL defined in VIEW objects.
> DDL import wizard - add better control over selection of imported objects
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-1782
> URL: https://issues.jboss.org/browse/TEIIDDES-1782
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Fix For: 8.5
>
>
> User request to provide better control over which object types are imported via the DDL importer:
> It would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options.
--
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
10 years, 5 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:
-----------------------------------
Fix Version/s: 8.5
8.3.3
> 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
>
>
> 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
10 years, 5 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:
-----------------------------------
Assignee: Paul Richardson
> 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
>
> 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
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2120?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2120:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087989
> 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
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb
by Johnathon Lee (JIRA)
[ 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
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2120) unable to reference same name .xsd when saving .vdb
by Johnathon Lee (JIRA)
Johnathon Lee created TEIIDDES-2120:
---------------------------------------
Summary: 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
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
--
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
10 years, 5 months