XmlBlaster requirements
=======================

Open

  http://www.xmlBlaster.org/xmlBlaster/doc/requirements/requirement.html

or locally

  file:///<XMLBLASTER_HOME/doc/requirements/requirement.html

to read the requirements.



Generate requirement HTML pages:
================================

cd xmlBlaster
build.sh requirements

That's it!



OLD REMAKRS:
============


The requirement document layout is validated with requirement.dtd

Each requirement is described in an own xml file

Requirements have no numbers but a unique describing name,
the filename is the same as the <requirement id=""> ID.

Every requirement needs a <testcase> tag, which refers to the testsuite
with one to many full automatic test cases.

Every bug is noted here and checked with a testsuite case.

The example tag allows to use the "<", all other tags need to write &lt; instead
(The example tag uses CDATA section, <pre> encapsulation and no
 'disable-output-escaping' in XLS)

You can query a closed requirement as follows:
   java DomQueryTest  engine.get.no.xml  "requirement/fix[@status='CLOSED']/.."

The html.xsl files needs the all.xml file to go though all xml requirements
and build a HTML table.

CollectXml.java is a little helper which generates all.xml
containing all xml requirements.
all.html is used by the XSL stylesheet to process all xml files into
one html file

Don't forget to do a 'make javadoc' in testcase/org/xmlBlaster to
generate html files from java files with syntax highlighting
(make javadoc in the root directory does this as well)

Note that both '-Dorg.xml.sax.parser=' or '-Dcom.jclark.xsl.sax.parser='
may be used to specify the xml parser.


Generate HTML output with Sun XML parser:
=========================================
Table with all requirements:
   java -Dorg.xml.sax.parser=com.jclark.xsl.dom.SunXMLProcessorImpl com.jclark.xsl.sax.Driver all.xml html.xsl requirement.html
  or:
   java -Dorg.xml.sax.parser=com.sun.xml.parser.Parser com.jclark.xsl.sax.Driver all.xml html.xsl requirement.html

Detail info of one requirement:
   java -Dcom.jclark.xsl.sax.parser=com.jclark.xsl.dom.SunXMLProcessorImpl com.jclark.xsl.sax.Driver engine.qos.publish.destination.PtX.xml detail.xsl engine.qos.publish.destination.PtX.html
  or:
   java -Dcom.jclark.xsl.sax.parser=com.sun.xml.parser.Parser com.jclark.xsl.sax.Driver engine.qos.publish.destination.PtX.xml detail.xsl engine.qos.publish.destination.PtX.html
  or:
   java -Dcom.jclark.xsl.sax.parser=com.sun.xml.parser.ValidatingParser com.jclark.xsl.sax.Driver engine.qos.publish.destination.PtX.xml detail.xsl engine.qos.publish.destination.PtX.html


Generate HTML output with James Clarks XML parser XP:
=====================================================
   export CLASSPATH=/www/xp/xp.jar:$CLASSPATH
   java -Dcom.jclark.xsl.sax.parser=com.jclark.xml.sax.CommentDriver com.jclark.xsl.sax.Driver all.xml html.xsl requirement.html


Validating with Sun jaxp parser:
================================
   java -Djavax.xml.parsers.validation=true main engine.transaction.xml


Validating with IBM parser:
===========================
export CLASSPATH=/www/xml4j/xml4j.jar:/www/xml4j/xml4jSamples.jar:$CLASSPATH
java dom.DOMCount -p dom.wrappers.DOMParser engine.get.no.xml
java dom.DOMWriter -p dom.wrappers.DOMParser engine.get.no.xml



xmlBlaster@marcelruff.info




---- snippet how to pass parameters from command line ----
If I try this from the command-line with Oracle XSLT,
passing a value for the parameter, I get:

$ oraxsl -p key='9988' data.xml test.xsl

http://localhost:8000/servlet/servletName?objectKey=9988
http://localhost:8000/servlet/servletName?objectKey=9988


---- XSL-FO engine to generate PDF output ----------------
http://www.unicorn-enterprises.com/download_ufo.html
