Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » WST XML editor schema finding using name of the schema
WST XML editor schema finding using name of the schema [message #191902] Wed, 02 May 2007 06:04 Go to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Hi,
is there anyway to configure WST XML editor in a way that all the XML files
in an eclipse prject locate to the schema files at the project root?? The
project may have subfolders to hold XMl files. What I want is to just
mention the name of the schema file and don't want to mention the project
relative path. Your comment in this regard will be helpfull.

Thanks,
Kashif
Re: WST XML editor schema finding using name of the schema [message #191918 is a reply to message #191902] Wed, 02 May 2007 11:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

Kashif,

I don't know the details, but I'm quite sure WTP supports an XML catalog
that allows you to specify the location of the schema for each target
namespace. So look for a way to configure the catalog.


kashif wrote:
> Hi,
> is there anyway to configure WST XML editor in a way that all the XML files
> in an eclipse prject locate to the schema files at the project root?? The
> project may have subfolders to hold XMl files. What I want is to just
> mention the name of the schema file and don't want to mention the project
> relative path. Your comment in this regard will be helpfull.
>
> Thanks,
> Kashif
>
>
>
Re: WST XML editor schema finding using name of the schema [message #191927 is a reply to message #191918] Wed, 02 May 2007 12:00 Go to previous messageGo to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Hi Ed Merks,

Let me explain my problem....

My project structure looks like this

Project
a.. TemplateFolder
a.. Template1.xml
b.. Template2.xml
a.. MenuFolder
a.. Menu1.xml
b.. Menu2.xml
a.. Project.xml
b.. Tokens.xml
c.. Settings.xml
d.. SchemaFolder
a.. Schema for Template XML files
b.. Schema for Menu XML files
c.. Schema for Project XML files
d.. Schema for Tokens XMl files
e.. .....
f.. .....

What I really wanted to do is to just have a subfolder at the project level
say "schema". This is the folder which will have the schema files for all
the different types of XML files (template, menu, project, tokens and
settings). I don't want to put absolute the location of the schema file. If
I mention the absolute location of the schema file in the XML file then all
the projects does not preserve the shareable nature. It means if in my
project the location of the schema file is

F:\Infelxion_handheld\schema\temp\uiTemplate.xsd

This same location will not be valid for other user at his system. What I
can do is for the user I can place all my schema files in the in the project
root and might be XML editor allow me some sort of configuration mechanism
to resolve these schema files placed under the project root. If it does have
already built in mechanism that will be great which I don't know.


I got know that it can resolve the schema file location if I use

<uiMenu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="../uiMenu.xsd">

uiMenu is the root element in my XMl file. This XML file is placed under the
Menu folder in the Project. But this is too an issue as user is allowed to
move file from one directory to another and then we have to track the
copying operation as well which seems not to be realistic.

I would really appreciate your valuable comments to solve the above problem.

Thanks,
Kashif

"Ed Merks" <merks@ca.ibm.com> wrote in message
news:f19rs6$pib$4@build.eclipse.org...
> Kashif,
>
> I don't know the details, but I'm quite sure WTP supports an XML catalog
> that allows you to specify the location of the schema for each target
> namespace. So look for a way to configure the catalog.
>
>
> kashif wrote:
>> Hi,
>> is there anyway to configure WST XML editor in a way that all the XML
>> files in an eclipse prject locate to the schema files at the project
>> root?? The project may have subfolders to hold XMl files. What I want is
>> to just mention the name of the schema file and don't want to mention the
>> project relative path. Your comment in this regard will be helpfull.
>>
>> Thanks,
>> Kashif
>>
>>
Re: WST XML editor schema finding using name of the schema [message #191930 is a reply to message #191918] Wed, 02 May 2007 12:14 Go to previous messageGo to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Hi Ed Merks,

I just created a namespace entry thorugh catlog


Location: Spiderman Theme/uiMenu.xsd
URI: platform:/resource/Spiderman Theme/uiMenu.xsd
Key Type: Namespace Name
Key: Test1

My XMl file the looks like this

<uiMenu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/XMLSchema-instance Test">

I found the following warning message "No grammer constraint detected for
the Document"

May be I am missing something which needs to be address. When I use schema
location option it says there needs to be full path to the location is
required which does not fit wiht the requirement which I mentioned in the
Last email. Any thoughts at this??

Thanks,

Kashif










"Ed Merks" <merks@ca.ibm.com> wrote in message
news:f19rs6$pib$4@build.eclipse.org...
> Kashif,
>
> I don't know the details, but I'm quite sure WTP supports an XML catalog
> that allows you to specify the location of the schema for each target
> namespace. So look for a way to configure the catalog.
>
>
> kashif wrote:
>> Hi,
>> is there anyway to configure WST XML editor in a way that all the XML
>> files in an eclipse prject locate to the schema files at the project
>> root?? The project may have subfolders to hold XMl files. What I want is
>> to just mention the name of the schema file and don't want to mention the
>> project relative path. Your comment in this regard will be helpfull.
>>
>> Thanks,
>> Kashif
>>
>>
Re: WST XML editor schema finding using name of the schema [message #191940 is a reply to message #191930] Wed, 02 May 2007 12:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

This is a multi-part message in MIME format.
--------------080807010501050207020208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Kashif,

I'm really not familiar with how WTP manages the catalog but if relative
paths don't make you happy, and paths of the form
platform:/resource/project/My.xsd don't make you happy (maybe you don't
know about those?), then your last alternative appears to be the
catalog. In general a relative path like "Test" will/should be resolved
against the containing document's URI. I.e., if the example below were
in resource with URI platform:/resource/project/my.xml then the schema's
location should resolve to platform:/resource/project/Test and that
should be what's looked up in the XML catalog.


kashif wrote:
> Hi Ed Merks,
>
> I just created a namespace entry thorugh catlog
>
>
> Location: Spiderman Theme/uiMenu.xsd
> URI: platform:/resource/Spiderman Theme/uiMenu.xsd
> Key Type: Namespace Name
> Key: Test1
>
> My XMl file the looks like this
>
> <uiMenu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.w3.org/2001/XMLSchema-instance Test">
>
> I found the following warning message "No grammer constraint detected for
> the Document"
>
> May be I am missing something which needs to be address. When I use schema
> location option it says there needs to be full path to the location is
> required which does not fit wiht the requirement which I mentioned in the
> Last email. Any thoughts at this??
>
> Thanks,
>
> Kashif
>
>
>
>
>
>
>
>
>
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:f19rs6$pib$4@build.eclipse.org...
>
>> Kashif,
>>
>> I don't know the details, but I'm quite sure WTP supports an XML catalog
>> that allows you to specify the location of the schema for each target
>> namespace. So look for a way to configure the catalog.
>>
>>
>> kashif wrote:
>>
>>> Hi,
>>> is there anyway to configure WST XML editor in a way that all the XML
>>> files in an eclipse prject locate to the schema files at the project
>>> root?? The project may have subfolders to hold XMl files. What I want is
>>> to just mention the name of the schema file and don't want to mention the
>>> project relative path. Your comment in this regard will be helpfull.
>>>
>>> Thanks,
>>> Kashif
>>>
>>>
>>>
>
>
>


--------------080807010501050207020208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Kashif,<br>
<br>
I'm really not familiar with how WTP manages the catalog but if
relative paths don't make you happy, and paths of the form
platform:/resource/project/My.xsd don't make you happy (maybe you don't
know about those?), then your last alternative appears to be the
catalog.&nbsp; In general a relative path like "Test" will/should be
resolved against the containing document's URI.&nbsp; I.e., if the example
below were in resource with URI platform:/resource/project/my.xml then
the schema's location should resolve to platform:/resource/project/Test
and that should be what's looked up in the XML catalog.<br>
<br>
<br>
kashif wrote:
<blockquote cite="midf19vc2$2eb$1@build.eclipse.org" type="cite">
<pre wrap="">Hi Ed Merks,

I just created a namespace entry thorugh catlog


Location: Spiderman Theme/uiMenu.xsd
URI: platform:/resource/Spiderman Theme/uiMenu.xsd
Key Type: Namespace Name
Key: Test1

My XMl file the looks like this

&lt;uiMenu xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instanceTest">"http://www.w3.org/2001/XMLSchema-instance Test"</a>&gt;

I found the following warning message "No grammer constraint detected for
the Document"

May be I am missing something which needs to be address. When I use schema
location option it says there needs to be full path to the location is
required which does not fit wiht the requirement which I mentioned in the
Last email. Any thoughts at this??

Thanks,

Kashif










"Ed Merks" <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com">&lt;merks@ca.ibm.com&gt;</a> wrote in message
<a class="moz-txt-link-freetext" href="news:f19rs6$pib$4@build.eclipse.org">news:f19rs6$pib$4@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Kashif,

I don't know the details, but I'm quite sure WTP supports an XML catalog
that allows you to specify the location of the schema for each target
namespace. So look for a way to configure the catalog.


kashif wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
is there anyway to configure WST XML editor in a way that all the XML
files in an eclipse prject locate to the schema files at the project
root?? The project may have subfolders to hold XMl files. What I want is
to just mention the name of the schema file and don't want to mention the
project relative path. Your comment in this regard will be helpfull.

Thanks,
Kashif


</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->

</pre>
</blockquote>
<br>
</body>
</html>

--------------080807010501050207020208--
Re: WST XML editor schema finding using name of the schema [message #191949 is a reply to message #191940] Wed, 02 May 2007 17:02 Go to previous messageGo to next message
Craig Salter is currently offline Craig SalterFriend
Messages: 169
Registered: July 2009
Senior Member
Please note that the XML Catalog only supports keys that are 'qualified'
locations.

So creating an entry like this...

'http://www.example.org/myschema.xsd' --> 'D:/foo/myschema/xsd'

.. is supported but creating an entry lis this...

'myschema.xsd' --> 'D:/foo/myschema/xsd'

.. is not supported.

For more info see this feature request...

https://bugs.eclipse.org/bugs/show_bug.cgi?id=104001

BTW, you can likely achieve exactly what you want by providing a
URIResolver extension. That means having to write a bit of plugin code.
But it should be very do-able. Table a look at wst.common.uriresolver
Re: WST XML editor schema finding using name of the schema [message #191972 is a reply to message #191949] Thu, 03 May 2007 05:43 Go to previous messageGo to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Hi Criag,

This seems to be a cool idea. I try to implement URIResolver interface but a
null pointer exception occurs while getting the resolver. May be I am
missing something here??

java.lang.NullPointerException

at
org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionDescriptor.getResolver(URIResolverExtensionDescriptor.ja va:81)

at
org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionRegistry.getMatchingURIResolvers(URIResolverExtensionReg istry.java:153)

at
org.eclipse.wst.common.uriresolver.internal.ExtensibleURIRes olver.resolvePhysicalLocation(ExtensibleURIResolver.java:105 )

at
org.eclipse.wst.xml.core.internal.validation.ValidatorHelper $MyContentHandler.startElement(ValidatorHelper.java:257)

at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unk nown Source)

at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unkn own Source)

at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanSt artElement(Unknown
Source)

at
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatc her.scanRootElementHook(Unknown
Source)

at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$Fragme ntContentDispatcher.dispatch(Unknown
Source)

at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDo cument(Unknown
Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at
org.eclipse.wst.xml.core.internal.validation.ValidatorHelper .computeValidationInformation(ValidatorHelper.java:144)

at
org.eclipse.wst.xml.core.internal.validation.XMLValidator.va lidate(XMLValidator.java:264)

at
org.eclipse.wst.xml.core.internal.validation.eclipse.Validat or.validate(Validator.java:70)

at
org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validate(AbstractNestedValidator.java:241)

at
org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validateInJob(AbstractNestedValidator.java:88)

at
org.eclipse.wst.xml.ui.internal.validation.DelegatingSourceV alidator.validate(DelegatingSourceValidator.java:211)

at
org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.validate(ReconcileStepForValidator.java:27 7)

at
org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.reconcileModel(ReconcileStepForValidator.j ava:243)

at
org.eclipse.jface.text.reconciler.AbstractReconcileStep.reco ncile(AbstractReconcileStep.java:96)

at
org.eclipse.wst.sse.ui.internal.reconcile.validator.Validato rStrategy.reconcile(ValidatorStrategy.java:204)

at
org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProc essor.process(DocumentRegionProcessor.java:183)

at
org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionPr ocessor.process(StructuredRegionProcessor.java:302)

at
org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcess or.run(DirtyRegionProcessor.java:636)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)



Thanks,

Kashif

"craig" <csalter@ca.ibm.com> wrote in message
news:3665b0905a32b826f4060987d6c3a0a5$1@www.eclipse.org...
> Please note that the XML Catalog only supports keys that are 'qualified'
> locations.
> So creating an entry like this...
>
> 'http://www.example.org/myschema.xsd' --> 'D:/foo/myschema/xsd'
>
> . is supported but creating an entry lis this...
>
> 'myschema.xsd' --> 'D:/foo/myschema/xsd'
>
> . is not supported.
>
> For more info see this feature request...
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=104001
>
> BTW, you can likely achieve exactly what you want by providing a
> URIResolver extension. That means having to write a bit of plugin code.
> But it should be very do-able. Table a look at wst.common.uriresolver
>
Re: WST XML editor schema finding using name of the schema [message #191983 is a reply to message #191972] Thu, 03 May 2007 09:58 Go to previous messageGo to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Hi Criag,
Please ignore my Last URIResolver exception problem. I just removed the id
and name and it works fine. Seems it might be a bug. Anyway it works without
id and name for resolver

But now I am curious to know if it works or not as I just return the file
system path for the specific schema file but it does not work. It looks like
that cutomize resolver has no significance impact over the help tooltip,
content assist and error messages. They showed up if I just return wrong
path.

Looks like there is something else which I need to implement??

Thanks,
Kashif

"kashif" <kashif_shahzad@mentor.com> wrote in message
news:f1bspb$7uf$1@build.eclipse.org...
> Hi Criag,
>
> This seems to be a cool idea. I try to implement URIResolver interface but
> a null pointer exception occurs while getting the resolver. May be I am
> missing something here??
>
> java.lang.NullPointerException
>
> at
> org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionDescriptor.getResolver(URIResolverExtensionDescriptor.ja va:81)
>
> at
> org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionRegistry.getMatchingURIResolvers(URIResolverExtensionReg istry.java:153)
>
> at
> org.eclipse.wst.common.uriresolver.internal.ExtensibleURIRes olver.resolvePhysicalLocation(ExtensibleURIResolver.java:105 )
>
> at
> org.eclipse.wst.xml.core.internal.validation.ValidatorHelper $MyContentHandler.startElement(ValidatorHelper.java:257)
>
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unk nown
> Source)
>
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unkn own Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanSt artElement(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatc her.scanRootElementHook(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$Fragme ntContentDispatcher.dispatch(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDo cument(Unknown
> Source)
>
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>
> at
> org.eclipse.wst.xml.core.internal.validation.ValidatorHelper .computeValidationInformation(ValidatorHelper.java:144)
>
> at
> org.eclipse.wst.xml.core.internal.validation.XMLValidator.va lidate(XMLValidator.java:264)
>
> at
> org.eclipse.wst.xml.core.internal.validation.eclipse.Validat or.validate(Validator.java:70)
>
> at
> org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validate(AbstractNestedValidator.java:241)
>
> at
> org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validateInJob(AbstractNestedValidator.java:88)
>
> at
> org.eclipse.wst.xml.ui.internal.validation.DelegatingSourceV alidator.validate(DelegatingSourceValidator.java:211)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.validate(ReconcileStepForValidator.java:27 7)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.reconcileModel(ReconcileStepForValidator.j ava:243)
>
> at
> org.eclipse.jface.text.reconciler.AbstractReconcileStep.reco ncile(AbstractReconcileStep.java:96)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.validator.Validato rStrategy.reconcile(ValidatorStrategy.java:204)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProc essor.process(DocumentRegionProcessor.java:183)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionPr ocessor.process(StructuredRegionProcessor.java:302)
>
> at
> org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcess or.run(DirtyRegionProcessor.java:636)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
>
>
> Thanks,
>
> Kashif
>
> "craig" <csalter@ca.ibm.com> wrote in message
> news:3665b0905a32b826f4060987d6c3a0a5$1@www.eclipse.org...
>> Please note that the XML Catalog only supports keys that are 'qualified'
>> locations.
>> So creating an entry like this...
>>
>> 'http://www.example.org/myschema.xsd' --> 'D:/foo/myschema/xsd'
>>
>> . is supported but creating an entry lis this...
>>
>> 'myschema.xsd' --> 'D:/foo/myschema/xsd'
>>
>> . is not supported.
>>
>> For more info see this feature request...
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=104001
>>
>> BTW, you can likely achieve exactly what you want by providing a
>> URIResolver extension. That means having to write a bit of plugin code.
>> But it should be very do-able. Table a look at wst.common.uriresolver
>>
>
>
Re: WST XML editor schema finding using name of the schema [message #191992 is a reply to message #191983] Thu, 03 May 2007 12:52 Go to previous messageGo to next message
kashif is currently offline kashifFriend
Messages: 16
Registered: July 2009
Junior Member
Thanks All.

I am fixed my problem and it's up now

Thanks,
Kashif


"kashif" <kashif_shahzad@mentor.com> wrote in message
news:f1cbot$j68$1@build.eclipse.org...
> Hi Criag,
> Please ignore my Last URIResolver exception problem. I just removed the id
> and name and it works fine. Seems it might be a bug. Anyway it works
> without id and name for resolver
>
> But now I am curious to know if it works or not as I just return the file
> system path for the specific schema file but it does not work. It looks
> like that cutomize resolver has no significance impact over the help
> tooltip, content assist and error messages. They showed up if I just
> return wrong path.
>
> Looks like there is something else which I need to implement??
>
> Thanks,
> Kashif
>
> "kashif" <kashif_shahzad@mentor.com> wrote in message
> news:f1bspb$7uf$1@build.eclipse.org...
>> Hi Criag,
>>
>> This seems to be a cool idea. I try to implement URIResolver interface
>> but a null pointer exception occurs while getting the resolver. May be I
>> am missing something here??
>>
>> java.lang.NullPointerException
>>
>> at
>> org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionDescriptor.getResolver(URIResolverExtensionDescriptor.ja va:81)
>>
>> at
>> org.eclipse.wst.common.uriresolver.internal.URIResolverExten sionRegistry.getMatchingURIResolvers(URIResolverExtensionReg istry.java:153)
>>
>> at
>> org.eclipse.wst.common.uriresolver.internal.ExtensibleURIRes olver.resolvePhysicalLocation(ExtensibleURIResolver.java:105 )
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.ValidatorHelper $MyContentHandler.startElement(ValidatorHelper.java:257)
>>
>> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unk nown
>> Source)
>>
>> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unkn own
>> Source)
>>
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanSt artElement(Unknown
>> Source)
>>
>> at
>> org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatc her.scanRootElementHook(Unknown
>> Source)
>>
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$Fragme ntContentDispatcher.dispatch(Unknown
>> Source)
>>
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDo cument(Unknown
>> Source)
>>
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>
>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>
>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.ValidatorHelper .computeValidationInformation(ValidatorHelper.java:144)
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.XMLValidator.va lidate(XMLValidator.java:264)
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.eclipse.Validat or.validate(Validator.java:70)
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validate(AbstractNestedValidator.java:241)
>>
>> at
>> org.eclipse.wst.xml.core.internal.validation.core.AbstractNe stedValidator.validateInJob(AbstractNestedValidator.java:88)
>>
>> at
>> org.eclipse.wst.xml.ui.internal.validation.DelegatingSourceV alidator.validate(DelegatingSourceValidator.java:211)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.validate(ReconcileStepForValidator.java:27 7)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.validator.Reconcil eStepForValidator.reconcileModel(ReconcileStepForValidator.j ava:243)
>>
>> at
>> org.eclipse.jface.text.reconciler.AbstractReconcileStep.reco ncile(AbstractReconcileStep.java:96)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.validator.Validato rStrategy.reconcile(ValidatorStrategy.java:204)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProc essor.process(DocumentRegionProcessor.java:183)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionPr ocessor.process(StructuredRegionProcessor.java:302)
>>
>> at
>> org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcess or.run(DirtyRegionProcessor.java:636)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>>
>>
>>
>> Thanks,
>>
>> Kashif
>>
>> "craig" <csalter@ca.ibm.com> wrote in message
>> news:3665b0905a32b826f4060987d6c3a0a5$1@www.eclipse.org...
>>> Please note that the XML Catalog only supports keys that are 'qualified'
>>> locations.
>>> So creating an entry like this...
>>>
>>> 'http://www.example.org/myschema.xsd' --> 'D:/foo/myschema/xsd'
>>>
>>> . is supported but creating an entry lis this...
>>>
>>> 'myschema.xsd' --> 'D:/foo/myschema/xsd'
>>>
>>> . is not supported.
>>>
>>> For more info see this feature request...
>>>
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=104001
>>>
>>> BTW, you can likely achieve exactly what you want by providing a
>>> URIResolver extension. That means having to write a bit of plugin code.
>>> But it should be very do-able. Table a look at wst.common.uriresolver
>>>
>>
>>
>
>
Re: WST XML editor schema finding using name of the schema [message #192027 is a reply to message #191992] Thu, 03 May 2007 16:47 Go to previous message
Craig Salter is currently offline Craig SalterFriend
Messages: 169
Registered: July 2009
Senior Member
Kashif,

Glad to hear you managed to get things working. If you have time to
contribute a short tutorial on the Eclipse WIKI [1] to describe the steps
you needed to take to achieve this I'm sure community would appreciate it.


[1] http://wiki.eclipse.org/index.php/Web_Tools_Project

kashif wrote:

> Thanks All.

> I am fixed my problem and it's up now

> Thanks,
> Kashif
Previous Topic:Doubt about the kind of web project to start
Next Topic:XMl attribute value validation
Goto Forum:
  


Current Time: Fri Nov 28 15:04:04 GMT 2014

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

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