Yes. That's much clearer. Thanks. I think it's fine to have the W3C catalog in our tests package.
Lawrence "Graham Turrell (gmail)" <[EMAIL PROTECTED]> 04/17/2007 06:13 AM Please respond to [email protected] To [email protected] cc Subject Re: No need for imported doc entries in catalog file? Hi Lawrence, Bit of explaination needed. There are actually two catalog files in the full distro: schema.catalog is the system catalog containing references to WSDL2 and related schema and is therefore generally applicable. The other catalog (the subject of the earlier part of this thread) is specific to the W3c test suite, but this appears only in the {trunk}/test directory of the woden tree (and the "test" jar in the distro), not in the {trunk}/src tree.This is just an example of a "user catalog" that can be specified in addition to the "hard-wired" system catalog. In this case the w3c user catalog is available for running the w3c test-suite offline/locally. The two catalogs types are covered in the woden user guide [1]. I'd certainly accept any suggestions for clarifying thwe mechanism description... In summary, the (test-suite independent) system catalog appears in the main woden jar file, and the test-suite specific user catalog is in the woden test jar (along with the test-suite specific JUnit classes). Hope that clarifies? Regards, Graham. [1] http://incubator.apache.org/woden/userguide.html : "3 ? Automatic schema resolution - schema.catalog" On 4/16/07, Lawrence Mandel <[EMAIL PROTECTED] > wrote: Graham, Have I understood correctly that we have W3C specific schemas listed in our Woden catalog? If this is the case I think they should be removed. We need to ensure Woden can function without any knowledge of the application or domain in which it is functioning. Also, I don't think these entries will be useful for any of our clients as they all refer to test documents. Lawrence "Graham Turrell (gmail)" <[EMAIL PROTECTED] > 04/12/2007 01:39 PM Please respond to [email protected] To [email protected] cc Subject Re: No need for imported doc entries in catalog file? Hi John, I've tried recreating your problem, using the catalog file with those entries removed, and I still see the failing tests that prompted those entries to be added. I've run the Junit tests using the eclipse sandbox and the ant-generated woden jars, both network-connected and network isolated (the former still gives all green as one would expect). I've pulled down a brand new super-fresh 7a-RC1 image to eclipse, rebuilt the jars and done the same there. With the user catalog in 7a-RC1, I see the same failures because you reverted the catalog to prior my changes. Please double-check your test results and if you see see all green in JUnit I'll take another look. Otherwise please sync the trunk W3CTests.catalog into 7a in svn. Cheers, Graham On 4/12/07, John Kaputin < [EMAIL PROTECTED]> wrote: Graham, I tested Woden M7a against the jar files only and disconnected from the network and it ran fine using the W3Ctest.catalog file without the following XSD entries. These entries are present in this file in Woden trunk, but if my testing is correct they are redundant. I don't recall the exact test scenario that prompted us to add these entries initially, but I assume your recent WODEN-154 fix resolved the problem. Could you do the same test yourself against Woden trunk, with these entries removed from the catalog file, running against the jars only and disconnected. If that works, it means the resolver and catalog work the way we originally intended, which was to enter only the base document's entry and let imported documents resolve against that without the need to include catalog entries for all imported docs. http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/CreditCardFaults-1G/resSvc.xsd=documents/good/CreditCardFaults-1G/resSvc.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/Import-1G/name.xsd=documents/good/Import-1G/name.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/Import-2G/name.xsd=documents/good/Import-2G/name.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/ServiceReference-1G/reservationList.xsd=documents/good/ServiceReference-1G/reservationList.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/ServiceReference-1G/reservationDetails.xsd=documents/good/ServiceReference-1G/reservationDetails.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/TicketAgent-1G/TicketAgent.xsd=documents/good/TicketAgent-1G/TicketAgent.xsd http\://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/XsImport-3G/reservationDetails.wsdl=documents/good/XsImport-3G/reservationDetails.wsdl John Kaputin Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kind Regards, Graham --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kind Regards, Graham --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
