Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » XML Schema Definition (XSD) » progress... but still stuck
progress... but still stuck [message #32490] Thu, 30 October 2003 22:17 Go to next message
Lance Phillips is currently offline Lance PhillipsFriend
Messages: 210
Registered: July 2009
Senior Member
Ed,
We're making some progress. When I read in my legacy model, I'm able to
get references to XSD Simple datatypes via the GlobalResourceSet as you
suggested. I end up with hrefs that look like this :
<baseTypeDefinition
href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
..xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>



However, when I try to reload the xmi resource that contains this kind of
ref, the xmi resource is unable to resolve the reference. Any ideas on what
we're still missing? We've tried explicity loading the xsd file referenced
above into our resource set prior to trying to open the converted xmi model
and that didn't seem to help either.

thanks,

lp
Re: progress... but still stuck [message #32525 is a reply to message #32490] Fri, 31 October 2003 13:53 Go to previous messageGo to next message
Dennis Fuglsang is currently offline Dennis FuglsangFriend
Messages: 77
Registered: July 2009
Member
Ed,

We were able to get past the problem listed below by using an href of the
form :

href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
..xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"

The EObject proxies that are created are resolvable through the
EcoreUtil.resolve(...).

thanks,

-dennis


"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:bns2kh$ejr$1@eclipse.org...
> Ed,
> We're making some progress. When I read in my legacy model, I'm able
to
> get references to XSD Simple datatypes via the GlobalResourceSet as you
> suggested. I end up with hrefs that look like this :
> <baseTypeDefinition
>
href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
> .xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
>
>
>
> However, when I try to reload the xmi resource that contains this kind of
> ref, the xmi resource is unable to resolve the reference. Any ideas on
what
> we're still missing? We've tried explicity loading the xsd file
referenced
> above into our resource set prior to trying to open the converted xmi
model
> and that didn't seem to help either.
>
> thanks,
>
> lp
>
>
Re: progress... but still stuck [message #32594 is a reply to message #32490] Mon, 03 November 2003 12:10 Go to previous message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

--------------D8454CDEB562C138931FD7F6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lance,

I see that I should really take advantage of some of the latest features in EMF
that weren't available when I began the XSD work. It would be awfully nice if
the "global" references were of the form

http://www.w3.org/2001/XMLSchema#//..

rather than

platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema.xsd#//..

This could be accomplished with a URI map...

The XSD model's global resource set is populated on demand by calls like
XSDSchemaImpl.getSchemaForSchema. So if nothing has prompted the schema for
schema instance to be created, the XSD global resource set will be empty.
Probably that's the thing missing in your scenario.


Lance Phillips wrote:

> Ed,
> We're making some progress. When I read in my legacy model, I'm able to
> get references to XSD Simple datatypes via the GlobalResourceSet as you
> suggested. I end up with hrefs that look like this :
> <baseTypeDefinition
> href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
> .xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
>
> However, when I try to reload the xmi resource that contains this kind of
> ref, the xmi resource is unable to resolve the reference. Any ideas on what
> we're still missing? We've tried explicity loading the xsd file referenced
> above into our resource set prior to trying to open the converted xmi model
> and that didn't seem to help either.
>
> thanks,
>
> lp

--------------D8454CDEB562C138931FD7F6
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Lance,
<p>I see that I should really take advantage of some of the latest features
in EMF that weren't available when I began the XSD work.&nbsp; It would
be awfully nice if the "global" references were of the form
<blockquote><A HREF="http://www.w3.org/2001/XMLSchema#//">http://www.w3.org/2001/XMLSchema#//</A>..</blockquote>
rather than
<blockquote> platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema.xsd#//.. </blockquote>
This could be accomplished with a URI map...
<p>The XSD model's global resource set is populated on demand by calls
like XSDSchemaImpl.getSchemaForSchema. So if nothing has prompted the schema
for schema instance to be created, the XSD global resource set will be
empty.&nbsp; Probably that's the thing missing in your scenario.
<br>&nbsp;
<p>Lance Phillips wrote:
<blockquote TYPE=CITE>Ed,
<br>&nbsp;&nbsp;&nbsp; We're making some progress.&nbsp; When I read in
my legacy model, I'm able to
<br>get references to XSD Simple datatypes via the GlobalResourceSet as
you
<br>suggested.&nbsp; I end up with hrefs that look like this :
<br>&lt;baseTypeDefinition
<br>href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
<br>.xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
<p>However, when I try to reload the xmi resource that contains this kind
of
<br>ref, the xmi resource is unable to resolve the reference.&nbsp; Any
ideas on what
<br>we're still missing?&nbsp; We've tried explicity loading the xsd file
referenced
<br>above into our resource set prior to trying to open the converted xmi
model
<br>and that didn't seem to help either.
<p>thanks,
<p>lp</blockquote>
</html>

--------------D8454CDEB562C138931FD7F6--
Re: progress... but still stuck [message #580318 is a reply to message #32490] Fri, 31 October 2003 13:53 Go to previous message
Dennis Fuglsang is currently offline Dennis FuglsangFriend
Messages: 77
Registered: July 2009
Member
Ed,

We were able to get past the problem listed below by using an href of the
form :

href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
..xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"

The EObject proxies that are created are resolvable through the
EcoreUtil.resolve(...).

thanks,

-dennis


"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:bns2kh$ejr$1@eclipse.org...
> Ed,
> We're making some progress. When I read in my legacy model, I'm able
to
> get references to XSD Simple datatypes via the GlobalResourceSet as you
> suggested. I end up with hrefs that look like this :
> <baseTypeDefinition
>
href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
> .xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
>
>
>
> However, when I try to reload the xmi resource that contains this kind of
> ref, the xmi resource is unable to resolve the reference. Any ideas on
what
> we're still missing? We've tried explicity loading the xsd file
referenced
> above into our resource set prior to trying to open the converted xmi
model
> and that didn't seem to help either.
>
> thanks,
>
> lp
>
>
Re: progress... but still stuck [message #580367 is a reply to message #32490] Mon, 03 November 2003 12:10 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 31366
Registered: July 2009
Senior Member
--------------D8454CDEB562C138931FD7F6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Lance,

I see that I should really take advantage of some of the latest features in EMF
that weren't available when I began the XSD work. It would be awfully nice if
the "global" references were of the form

http://www.w3.org/2001/XMLSchema#//.

rather than

platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema.xsd#//..

This could be accomplished with a URI map...

The XSD model's global resource set is populated on demand by calls like
XSDSchemaImpl.getSchemaForSchema. So if nothing has prompted the schema for
schema instance to be created, the XSD global resource set will be empty.
Probably that's the thing missing in your scenario.


Lance Phillips wrote:

> Ed,
> We're making some progress. When I read in my legacy model, I'm able to
> get references to XSD Simple datatypes via the GlobalResourceSet as you
> suggested. I end up with hrefs that look like this :
> <baseTypeDefinition
> href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
> .xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
>
> However, when I try to reload the xmi resource that contains this kind of
> ref, the xmi resource is unable to resolve the reference. Any ideas on what
> we're still missing? We've tried explicity loading the xsd file referenced
> above into our resource set prior to trying to open the converted xmi model
> and that didn't seem to help either.
>
> thanks,
>
> lp

--------------D8454CDEB562C138931FD7F6
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Lance,
<p>I see that I should really take advantage of some of the latest features
in EMF that weren't available when I began the XSD work.&nbsp; It would
be awfully nice if the "global" references were of the form
<blockquote><A HREF="http://www.w3.org/2001/XMLSchema#//">http://www.w3.org/2001/XMLSchema#//</A>..</blockquote>
rather than
<blockquote> platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema.xsd#//.. </blockquote>
This could be accomplished with a URI map...
<p>The XSD model's global resource set is populated on demand by calls
like XSDSchemaImpl.getSchemaForSchema. So if nothing has prompted the schema
for schema instance to be created, the XSD global resource set will be
empty.&nbsp; Probably that's the thing missing in your scenario.
<br>&nbsp;
<p>Lance Phillips wrote:
<blockquote TYPE=CITE>Ed,
<br>&nbsp;&nbsp;&nbsp; We're making some progress.&nbsp; When I read in
my legacy model, I'm able to
<br>get references to XSD Simple datatypes via the GlobalResourceSet as
you
<br>suggested.&nbsp; I end up with hrefs that look like this :
<br>&lt;baseTypeDefinition
<br>href=" platform:/plugin/org.eclipse.xsd_1.1.1/cache/www.w3.org/2001 /XMLSchema
<br>.xsd#//NMTOKENS;XSDSimpleTypeDefinition=32"/>
<p>However, when I try to reload the xmi resource that contains this kind
of
<br>ref, the xmi resource is unable to resolve the reference.&nbsp; Any
ideas on what
<br>we're still missing?&nbsp; We've tried explicity loading the xsd file
referenced
<br>above into our resource set prior to trying to open the converted xmi
model
<br>and that didn't seem to help either.
<p>thanks,
<p>lp</blockquote>
</html>

--------------D8454CDEB562C138931FD7F6--


Ed Merks
Professional Support: https://www.macromodeling.com/
Previous Topic:NPE in XSDAnnotationItemProvider
Next Topic:NPE in XSDAnnotationItemProvider
Goto Forum:
  


Current Time: Wed Aug 12 22:05:17 GMT 2020

Powered by FUDForum. Page generated in 0.06578 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top