[ http://issues.apache.org/jira/browse/WODEN-70?page=comments#action_12454379 ] John Kaputin commented on WODEN-70: -----------------------------------
This issue is about being able to prove via the Woden Junit test suite that the URI resolver works when disconnected from the network. The idea is to establish a disconnected state during the normal execution of the entire test suite, rather than having to manually disconnected from the network and run the test suite a second time. While this does seem like an important feature of the test framework, I don't think it's essential for M7 so I suggest we do not flag this for the M7 release. There's already a lot of other essential JIRAs flagged for M7. Note, this JIRA is not just about running the Woden test suite network disconnected. That can be done already, providing you manually create the XML Catolog and place the common schemas and DTDs in the right place and define the appropriate JVM system properties. Other JIRA's have been opened about making that type of configuration more transparent or automatic. > Running Woden test suite in network isolation mode > -------------------------------------------------- > > Key: WODEN-70 > URL: http://issues.apache.org/jira/browse/WODEN-70 > Project: Woden > Issue Type: Test > Components: Validation > Reporter: Graham Turrell > > An excellent validation of the a URI resolver is to run the entire test suite > disconnected from the network. All external WSDL and XML Schema files > referenced by the test suite much appear (directly or indirectly) in the > Catalog used by the resolver under test, and local copies of those files must > exist prior to test execution. With the current test suite, this applies to > the W3C tests only. > Ideally there should be an ant task to automatically extract those files from > the W3C external URLs, and build the catalog file. In the meantime they may > be hard-wired into the Woden test suite (as the W3C tests currently are). > Also, decide upon and implement the means of running the tests in this mode. > The Resolver and catalog are referenced at run-time via system properties. A > JUnit test-suite could be created for each implemented Resolver to set > properties accordingly, and call AllWodenTests.suite() in a simulated offline > mode (eg. by "tampering" with http system properties). > Should the complete test-suite *always* be run multiple times (connected, and > disconnected) for each supported Woden URI Resolver); or limit the offline > tests to W3C tests only (by default at least)? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
