Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » bundleresource:// URL problem in library plugin
bundleresource:// URL problem in library plugin [message #263929] Tue, 27 July 2004 09:49 Go to next message
Eclipse UserFriend
I am moving code from an existing 2.1 plugin into a 3.0 RCP. Everything
worked fine under 2.1.

I am now seeing a call to getClass().getResource("file.xsd") in a dependant
DLL return a URL like bundleresource://2/file.xsd. The Xerces parser does
not like this at all, it gives a SAXParseException:

bundleresource://2/page-store-labeled.xsd' is not a valid 'anyURI' value

Anyone have any advice?
Thanks!
Rich
Re: bundleresource:// URL problem in library plugin [message #263941 is a reply to message #263929] Tue, 27 July 2004 11:23 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: chaves.nospam.inf.ufsc.br.ok

You can ensure the URL you handle to Xerces is a Java native one by
calling:

URL nativeURL = org.eclipse.core.runtime.Platform.resolve(pluginURL);

Rich Hume wrote:

> I am moving code from an existing 2.1 plugin into a 3.0 RCP. Everything
> worked fine under 2.1.

> I am now seeing a call to getClass().getResource("file.xsd") in a dependant
> DLL return a URL like bundleresource://2/file.xsd. The Xerces parser does
> not like this at all, it gives a SAXParseException:

> bundleresource://2/page-store-labeled.xsd' is not a valid 'anyURI' value

> Anyone have any advice?
> Thanks!
> Rich
Re: bundleresource:// URL problem in library plugin [message #264066 is a reply to message #263941] Tue, 27 July 2004 11:51 Go to previous messageGo to next message
Eclipse UserFriend
Thanks, but I was hoping for a solution that did not involve changing the
jar (I mistakenly refered to it as a dll in the orginal post) to link to
org.eclipse code. Note that in 2.1, that was not necessary. While this
particular jar is ours, it is used by applications outside Eclipse and we
would rather not have to package Eclipse with it in those situations.


"Rafael Chaves" <chaves@nospam.inf.ufsc.br.ok> wrote in message
news:ce5s1d$rb$1@eclipse.org...
> You can ensure the URL you handle to Xerces is a Java native one by
> calling:
>
> URL nativeURL = org.eclipse.core.runtime.Platform.resolve(pluginURL);
>
> Rich Hume wrote:
>
> > I am moving code from an existing 2.1 plugin into a 3.0 RCP. Everything
> > worked fine under 2.1.
>
> > I am now seeing a call to getClass().getResource("file.xsd") in a
dependant
> > DLL return a URL like bundleresource://2/file.xsd. The Xerces parser
does
> > not like this at all, it gives a SAXParseException:
>
> > bundleresource://2/page-store-labeled.xsd' is not a valid 'anyURI' value
>
> > Anyone have any advice?
> > Thanks!
> > Rich
>
>
Re: bundleresource:// URL problem in library plugin [message #264129 is a reply to message #264066] Tue, 27 July 2004 17:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: chaves.nospam.inf.ufsc.br.ok

Not of much help, but here is the corresponding PR:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=65673
Re: bundleresource:// URL problem in library plugin [message #1752194 is a reply to message #264066] Thu, 19 January 2017 10:58 Go to previous message
Eclipse UserFriend
This issue can be avoided by simply installing eclipse in a path without spaces.
Previous Topic:New java project does not get created correctly on network share
Next Topic:Expand Section widget in Eclipse Forms
Goto Forum:
  


Current Time: Sun Mar 16 21:54:46 EDT 2025

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

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

Back to the top