[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] JEE Related Schemas (finally) distributed in WTP
|
As promised I eyeballed the 'org.eclipse.jst.standard.schemas' plugin's xml
catalog extension points. Functionally everything should work fine and
although I did spot a minor issue (that I've described below) I suggest
leaving the plugin.xml just as it is until we get some time to consider
this minor issue further. Keep in mind this issue is really quite minor
and won't effect all the goodness that the community will enjoy (no more
schema license popups) once these schemas make their way into the builds.
The minor wrinkle I'm referring to is related to the 'location' or
'namespace' nature of a catalog entry. This distinction exists partially
for historical reasons (since the original catalog was not designed to
conform to the XML Catalog spec) and partially communicate to end users the
intended usage of the entry. I've opened bug 18420 to track this issue.
The skinny of the matter is that the newly added catalog entries for the
JEE schemas will show up in the XML Catalog as 'namespace' entries when in
fact they're really intended to be used to map to 'schemaLocations'. This
won't effect the way schemas are resolved, but it may mislead users who
read the details of these entries and attempt to reuse them as advertised.
Here's a bit more detail...
Currently in our XML Catalog implementation we use <system> elements to
describe entries that map to schemaLocations. So an element like this... .
<system
name="http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
uri="dtdsAndSchemas/application_1_4.xsd" />
.. would be applied in cases where the xml file was written like this...
<root xmlns="http://foo"; xsi:schemaLocation="http://foo
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
We use <uri> elements to describe entries that map to namespaces. So an
element like this...
<uri
name="http://java.sun.com/xml/ns/javaee/application_4.xsd";
uri="dtdsAndSchemas/application_4.xsd" />
... would be applied in cases where the xml file was written like this...
<root xmlns="
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
So we could 'fix' this issue by changing our <uri> elements to <system>
elements... but technically [1] we should be using <uri> for everything
other than DOCTYPE declarations (i.e. references to DTDs).
thanks
Craig
[1] http://www-128.ibm.com/developerworks/xml/library/x-mxd3.html
Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM
Phone: (905) 413-3918 TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx Notes: Craig Salter/Toronto/IBM@IBMCA
Craig
Salter/Toronto/IB
M@IBMCA To
Sent by: "General discussion of project-wide
wtp-dev-bounces@e or architectural issues."
clipse.org <wtp-dev@xxxxxxxxxxx>
cc
29/04/2007 11:34 Subject
PM Re: [wtp-dev] JEE Related Schemas
(finally) distributed in WTP
Please respond to
"General
discussion of
project-wide or
architectural
issues."
That's great news! BTW, so long as the xmlcatalog extensions live in the
same plugin as the schemas you shouldn't need to put 'platform:' in the
URI. We only need to do that in cases where we're the extension and the
xsd's live in different plugins. I'll grab the latest stuff tomorrow and
double check that things are config'd properly.
thanks
Craig
Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM
Phone: (905) 413-3918 TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx Notes: Craig Salter/Toronto/IBM@IBMCA
David M Williams
<david_williams@u
s.ibm.com> To
Sent by: wtp-dev@xxxxxxxxxxx
wtp-dev-bounces@e cc
clipse.org
Subject
[wtp-dev] JEE Related Schemas
29/04/2007 09:49 (finally) distributed in WTP
PM
Please respond to
"General
discussion of
project-wide or
architectural
issues."
It may not be the oldest IPZilla (but the three older one's have all been
closed as invalid :)
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4
Beginning this week, the JEE related schemas and dtds will be in WTP
builds.
The most obvious difference will be that the "accept license to cache"
dialog should
no longer pop up.
I'm sending this note to this general wtp-dev list since we are adding this
plugin very late in
the RC0 cycle so would appreciate if everyone could confirm it works
correctly and
contains everything expected.
I named the plugin
org.eclipse.jst.standard.schemas
And put the plugin into cvs at
jst/components/j2ee/plugins/org.eclipse.jst.standard.schemas
It is built as part of the jst web core feature
org.eclipse.jst.web_core.feature
I do leave the plugin "jarred" and all seems to work correct ...
for the tiny bit of testing I've done. But, I'm not sure, we may
have to put "platform:" in some of the URIs.
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
