Graham,

The schemas and DTDs should be in a Java package directory so the usual 
Java class loader can find them and return them as input streams.

e.g.

InputStream is = this.getClass().getResourceAsStream( "wsdl20.xsd" );

You should pick an existing package. Maybe the one that holds the URI 
resolver.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]



Graham Turrell <[EMAIL PROTECTED]> 
12/11/2006 01:54 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
location for standard schema in woden.jar







List,

I've not had any feedback to my recent comments on Woden-85 [1], so I
assume there is nothing contentious therein.

For building woden.jar, I plan to change build.xml to copy the xml and
wsdl2 schema files from the unzipped w3c test-suite.zip into
xmlcatalog/wsdl and xmlcatalog/wsdl respectively (which happens to mirror
the structure in downloads/w3c in the w3c test-suite).
This also simplifies configuration the developers' enviroment (eg eclipse
projects) too, as the schema downloaded from test-suite.zip into the
workspace can be used directly when running the test suites.
The hard-coded catalog file "system.catalog" (containing URI resolution
info for these local schema files) will appear in trunk/java in svn
(alongside build.xml, license files etc) and will be copied into the "/"
directory of woden.jar at build time.

There is a slight alternative to these locations, which is to place the
schema and catalog in woden.jar /META-INF. The only proviso is that in svn
the system catalog would need to appear 
trunk/java/META-INF/system.catalog.
If this is prefered to the first alternative and there is no objection to 
a
META-INF directory in svn, then I'll do it that way.

Please let me know asap if you have a view on this either way.

Finally, which is preferred? - copying the schema to woden.jar from w3c
test-suite.zip, or directly from their published web locations? I'm in
favour of the former, since a built woden.jar should result from a build
tested with test-suite.zip's current contents.

Again, any views asap please. Thanks.

[1] http://issues.apache.org/jira/browse/WODEN-85

Kind Regards,

Graham.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to