Eclipse Community Forums: ServerTools (WTP)

Home » Language IDEs » ServerTools (WTP) » XML Catalogs

Wed, 22 June 2005 05:13

Eclipse User

Originally posted by: constantine.plotnikov.gmail.com

1. I'm intersted why XML Catalog extension point syntax is not aligned
with OASIS XML Catalog syntax
( http://www.oasis-open.org/committees/download.php/12075/xml- catalogs.html)
for supported elements. Possibly just embedding "catalog" element
without namespace would be most strightforward.

2. I would also prefer if there would be an option for catalog extension
point would refer to catalog file rather than embed it. In scenarios
when some library is distributed as both plugin and standalone library,
it would be more convinient. On other hand embedding it into plugins can
be more simple when there is only one mapping entry.

3. I'm intersted why Apache XML Catalog implementation from
http://xml.apache.org/commons/components/resolver/index.html was not
used? Was there some licensing problem? Or it was too difficult to
extend with events?

4. Builder that updates workplace visible catalog information from a
catalog file from some project might be an interesting extension. It
would simplify creation of projects that contain reusable xml files. For
example one project might contain docbook schemas that are refered by
catalog and files in other project refer to these schemas by public id.

Constantine

Re: XML Catalogs [message #113167 is a reply to message #113121]

Wed, 22 June 2005 15:25

Eclipse User

Originally posted by: ebelisar.ca.ibm.com

Constantine Plotnikov wrote:

> 1. I'm intersted why XML Catalog extension point syntax is not aligned
> with OASIS XML Catalog syntax
> ( http://www.oasis-open.org/committees/download.php/12075/xml- catalogs.html)
> for supported elements. Possibly just embedding "catalog" element
> without namespace would be most strightforward.

Are you asking why "catalogContribution" element is not named "catalog"
element? If that is the question, then
- we wanted to target users who just want to add entries to the catalog by
following the extension point definition without understanding the whole
OASIS spec.
- we wanted to limit what entries we support

> 2. I would also prefer if there would be an option for catalog extension
> point would refer to catalog file rather than embed it. In scenarios
> when some library is distributed as both plugin and standalone library,
> it would be more convinient. On other hand embedding it into plugins can
> be more simple when there is only one mapping entry.

- you could specify nextCatalog entry with your catalog file location in
the extension point. That catalog will be added to the system catalog.

> 3. I'm intersted why Apache XML Catalog implementation from
> http://xml.apache.org/commons/components/resolver/index.html was not
> used? Was there some licensing problem? Or it was too difficult to
> extend with events?

- yes, it's difficult to extend. Common catalog resolver implementation
does not have write capability, as well as events support, so we would
need to have either two in-memory representations of the catalog with the
problem of synchronizing them or just use our own implementation of the
resolution based on our model. Since files are saved in the common format
anyway, other tools could use common resolver if they want to.

> 4. Builder that updates workplace visible catalog information from a
> catalog file from some project might be an interesting extension. It
> would simplify creation of projects that contain reusable xml files. For
> example one project might contain docbook schemas that are refered by
> catalog and files in other project refer to these schemas by public id.

- you could submit a bugzilla enhancement request for this idea

Thanks,

Ella

Re: XML Catalogs [message #113259 is a reply to message #113167]

Thu, 23 June 2005 07:37

Eclipse User

Originally posted by: constantine.plotnikov.gmail.com

Ella Belisario wrote:
> Constantine Plotnikov wrote:
>
>> 1. I'm intersted why XML Catalog extension point syntax is not aligned
>> with OASIS XML Catalog syntax
>> ( http://www.oasis-open.org/committees/download.php/12075/xml- catalogs.html)
>> for supported elements. Possibly just embedding "catalog" element
>> without namespace would be most strightforward.
>
>
> Are you asking why "catalogContribution" element is not named "catalog"
> element? If that is the question, then
> - we wanted to target users who just want to add entries to the catalog
> by following the extension point definition without understanding the
> whole OASIS spec. - we wanted to limit what entries we support

I was asking why extension point contents is not a strict subset of
elements specified by XML Catalog 1.1 specification? Because different
syntax is used, those who know the catalog specification has to learn
both syntaxes. Also knowing extention point syntax would not help those
who do not yet know the specification to learn the complete
specification. It is also more difficult to copy/paste elements between
catalog and extention point.

.... 2 and 3 were cut ...

>> 4. Builder that updates workplace visible catalog information from a
>> catalog file from some project might be an interesting extension. It
>> would simplify creation of projects that contain reusable xml files.
>> For example one project might contain docbook schemas that are refered
>> by catalog and files in other project refer to these schemas by public
>> id.
>
>
> - you could submit a bugzilla enhancement request for this idea
>
Done. https://bugs.eclipse.org/bugs/show_bug.cgi?id=101422

5. I also have a new question. It might make sense to push XML Catalog
plugin into eclipse core in future versions. There is number of other
plugings that might benefit from it. For example EMF has own entity
resolver interface. The functionality is very basic and other plugins
that have reusable resources referenced by URI might find such
functionality useful.

Constantine

Re: XML Catalogs [message #113335 is a reply to message #113259]

Thu, 23 June 2005 10:51

Eclipse User

Originally posted by: ebelisar.ca.ibm.com

Constantine,

> I was asking why extension point contents is not a strict subset of
> elements specified by XML Catalog 1.1 specification? Because different
> syntax is used, those who know the catalog specification has to learn
> both syntaxes. Also knowing extention point syntax would not help those
> who do not yet know the specification to learn the complete
> specification. It is also more difficult to copy/paste elements between
> catalog and extention point.

- Currently public, system, uri and nextCatalog elements are supported by
the extension point. This is a subset of the elements defined in the spec
and they have the same syntax as in the spec. What is the difference that
you are pointing to?

> 5. I also have a new question. It might make sense to push XML Catalog
> plugin into eclipse core in future versions. There is number of other
> plugings that might benefit from it. For example EMF has own entity
> resolver interface. The functionality is very basic and other plugins
> that have reusable resources referenced by URI might find such
> functionality useful.

Best regards,

Ella

Re: XML Catalogs [message #113398 is a reply to message #113335]

Thu, 23 June 2005 16:06

Eclipse User

Originally posted by: constantine.plotnikov.gmail.com

Ella Belisario wrote:
> Constantine,
>
>> I was asking why extension point contents is not a strict subset of
>> elements specified by XML Catalog 1.1 specification? Because different
>> syntax is used, those who know the catalog specification has to learn
>> both syntaxes. Also knowing extention point syntax would not help
>> those who do not yet know the specification to learn the complete
>> specification. It is also more difficult to copy/paste elements between
>> catalog and extention point.
>
>
> - Currently public, system, uri and nextCatalog elements are supported
> by the extension point. This is a subset of the elements defined in the
> spec and they have the same syntax as in the spec. What is the
> difference that you are pointing to?
>
>

I have looked at fresh sources and have noticed that XML catalog support
changed in great way since last time I have looked. So my comment is no
more acutal and we were talking about different things. In M4 and in two
week old checkout there is, for example, the following fragment in
org.eclipse.wst.xsd.ui_1.0.0:

<extension point="org.eclipse.wst.xml.uriresolver.catalogContributor">
<catalogContributor catalogId="default">
<mappingInfo key="http://www.w3.org/2001/XMLSchema"
uri=" platform:/resource/org.eclipse.xsd/cache/www.w3.org/2001/XML Schema.xsd "/>
</catalogContributor>
</extension>

From implementation is looked as an attempt to merge all three elements
in the one. That caused my comment.

Constantine

Re: XML Catalogs [message #113511 is a reply to message #113259]

Fri, 24 June 2005 02:12

Eclipse User

> I was asking why extension point contents is not a strict subset of
> elements specified by XML Catalog 1.1 specification? Because different
> syntax is used, those who know the catalog specification has to learn
> both syntaxes. Also knowing extention point syntax would not help those
> who do not yet know the specification to learn the complete
> specification. It is also more difficult to copy/paste elements between
> catalog and extention point.

Contantine, you may not have seen the newest changes Ella has made. The
catalog extension point now 'is' a strict subset of elements specified by
XML Catalog 1.1 We just completed this work recently ... perhaps we read
your mind ;-)

Here's the document Ella wrote to describe
http://www.eclipse.org/webtools/wst/components/xml/M5/new_an d_noteworthy/XMLCatalog-m5.html

Re: XML Catalogs [message #113622 is a reply to message #113511]

Fri, 24 June 2005 09:17

Eclipse User

Originally posted by: constantine.plotnikov.gmail.com

Craig Salter wrote:
> Contantine, you may not have seen the newest changes Ella has made. The
> catalog extension point now 'is' a strict subset of elements specified
> by XML Catalog 1.1 We just completed this work recently ... perhaps we
> read your mind ;-)
>
> Here's the document Ella wrote to describe
> http://www.eclipse.org/webtools/wst/components/xml/M5/new_an d_noteworthy/XMLCatalog-m5.html
>
Yes. I have noticed it in the sources that I have checked out after
Ella's reply. I like the changes.

Constantine

Re: XML Catalogs [message #114735 is a reply to message #113259]

Thu, 30 June 2005 05:46

Eclipse User

Originally posted by: thhal.mailblocks.com

Constantine Plotnikov wrote:
> 5. I also have a new question. It might make sense to push XML Catalog
> plugin into eclipse core in future versions. There is number of other
> plugings that might benefit from it. For example EMF has own entity
> resolver interface. The functionality is very basic and other plugins
> that have reusable resources referenced by URI might find such
> functionality useful.
>
I second this. I added a Platform runtime feature request Bug# 102283.

Regards,
Thomas Hallgren

Previous Topic:	Why is no xml editor available?
Next Topic:	Errors using JSTL

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Apr 24 10:39:20 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter