Eclipse Community Forums: XML Schema Definition (XSD)

Help

Home

Home » Archived » XML Schema Definition (XSD) » Cloning annotations

Show: Today's Messages :: Show Polls :: Message Navigator

Cloning annotations [message #77637]

Fri, 08 May 2009 05:50

Keshavrao

Messages: 34
Registered: July 2009

Member

Hello Ed,

We want to clone components from one schema to another and we found two
ways of doing it -
1)cloneConcreteComponent in XSDConcreteComponent
2)import the DOM node as bhuvan, shobana are doing the previous thread.

The first option doesnt have any problems, it clones the component well
and also it works with the DOM prefixes nicely because it builds the DOM
completely for itself, but it doesnt copy the annotations.

But we also want to copy the annotations and i have to go by the second
option which has all the weird problems with the prefixes when XSDs come
from different sources.

Can we have the cloneConcreteComponent method to also copy the annotations
reliably instead to go with the second option.

Or it would also be gr8 if you can suggest us some other way of cloning
the annotations.

Thanks and regards,
Keshav Veerapaneni.

Report message to a moderator

Re: Cloning annotations [message #77653 is a reply to message #77637]

Fri, 08 May 2009 14:03

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

Keshav,

Comments below.

Keshavrao wrote:
> Hello Ed,
>
> We want to clone components from one schema to another and we found
> two ways of doing it - 1)cloneConcreteComponent in XSDConcreteComponent
> 2)import the DOM node as bhuvan, shobana are doing the previous thread.
>
> The first option doesnt have any problems, it clones the component
> well and also it works with the DOM prefixes nicely because it builds
> the DOM completely for itself, but it doesnt copy the annotations.
Yes.
>
> But we also want to copy the annotations and i have to go by the
> second option which has all the weird problems with the prefixes when
> XSDs come from different sources.
You'd think DOM would have better ways to handle something like this.
Seems like a fairly straight forward thing one would like to do, but in
the end it's not. Which is of course made worse because the annotation
might contain things that are QNames but aren't known to be QNames...
>
> Can we have the cloneConcreteComponent method to also copy the
> annotations reliably instead to go with the second option.
No, because the cloning is done purely at the model level and hence
doesn't involve DOM. Annotations are not represented in any way other
than as DOM.
>
> Or it would also be gr8 if you can suggest us some other way of
> cloning the annotations.
I think I'm out of suggestions. It's a tricky problem and I just don't
have spare cycles to solve it for free. Contributions from the
community toward additional utilities or facilities will be welcome.
>
> Thanks and regards,
> Keshav Veerapaneni.
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator