cocoon

 the classic workflow for developing and debugging code is edit,compile and test. an instance of the java.lang.thread class is associated with each thread running in the java vm.  these thread objects serve as the interface for interacting with the underlying operating system thread. through the methods in this class, threads can be started, stopped ,interrupted ,named,prioritized and queries regarding their current state. the volatile keywords is used as a modifier on member variable to force individual threads to reread the varibale's value from shared memory every time the variable is accessed. exception can be thrown just about anywhere in a java program. methods must declare all of the exceptions they might throw except for runtimeexception and its subclasses. a runtimeexception can occur on just about everyline of code. when an exception occurs and is not immediately caught , it propagates up the call stack until it either is caught by one of the invoking methods,or remains uncaught. cocoon was originally a very simple java servlet with approximately 100 lines of code and the format for the documents was xml.  it used the ibmxml4j parser for parsing of xml documents and the lotusxsl parser for transforming the xml file using an xsl stylesheet. generators take a requested uri and produce sax events. transformers consume sax events and produce other sax events. serializer consume sax events and produce a response. the cocoon sitemap is the configuration document that defines the piplines and  components available for use by web applications. the sitemap is an xml file and complies with all xml syntax and notations.