[CJ-dev] commonjava-projects/commonjava-opl logging.properties,NONE,1.1 project.properties,1.4,1.5 .
Brought to you by:
johnqueso
Menu
▾
▴
[CJ-dev] commonjava-projects/commonjava-opl logging.properties,NONE,1.1 project.properties,1.4,1.5 .classpath,1.7,1.8 project.xml,1.12,1.13 .project,1.1,1.2
|
From: <joh...@co...> - 2004-02-18 06:21:30
|
Update of /cvsroot/commonjava/commonjava-projects/commonjava-opl In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26618 Modified Files: project.properties .classpath project.xml .project Added Files: logging.properties Log Message: updated documentation in project.xml files, and added functionality to: Console: - provide convenient way to prompt the user for more information Config: - Provide snap-in container stacking, or scoping - Provide a JBoss service implementation of a snap-in container Probably other things, but I don't honestly remember everything... --- NEW FILE: logging.properties --- ############################################################ # Default Logging Configuration File # # You can use a different file by specifying a filename # with the java.util.logging.config.file system property. # For example java -Djava.util.logging.config.file=myfile ############################################################ ############################################################ # Global properties ############################################################ # "handlers" specifies a comma separated list of log Handler # classes. These handlers will be installed during VM startup. # Note that these classes must be on the system classpath. # By default we only configure a ConsoleHandler, which will only # show messages at the INFO and above levels. handlers= java.util.logging.ConsoleHandler # To also add the FileHandler, use the following line instead. #handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler # Default global logging level. # This specifies which kinds of events are logged across # all loggers. For any given facility this global level # can be overriden by a facility specific level # Note that the ConsoleHandler also has a separate level # setting to limit messages printed to the console. .level= INFO ############################################################ # Handler specific properties. # Describes specific configuration info for Handlers. ############################################################ # default file output is in user's home directory. java.util.logging.FileHandler.pattern = %h/java%u.log java.util.logging.FileHandler.limit = 50000 java.util.logging.FileHandler.count = 1 java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter # Limit the message that are printed on the console to INFO and above. java.util.logging.ConsoleHandler.level = FINEST java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter ############################################################ # Facility specific properties. # Provides extra control for each logger. ############################################################ # For example, set the com.xyz.foo logger to only log SEVERE # messages: org.commonjava.opl.level=FINEST Index: project.properties =================================================================== RCS file: /cvsroot/commonjava/commonjava-projects/commonjava-opl/project.properties,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- project.properties 9 Jan 2004 05:07:43 -0000 1.4 +++ project.properties 18 Feb 2004 06:12:10 -0000 1.5 @@ -12,6 +12,6 @@ maven.compile.source=1.4 maven.compile.target=1.4 -maven.junit.fork=true +#maven.junit.fork=true maven.junit.usefile=${basedir}/junit.out Index: .classpath =================================================================== RCS file: /cvsroot/commonjava/commonjava-projects/commonjava-opl/.classpath,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- .classpath 9 Jan 2004 05:07:43 -0000 1.7 +++ .classpath 18 Feb 2004 06:12:10 -0000 1.8 @@ -4,10 +4,10 @@ <classpathentry kind="src" output="target/test-classes" path="src/test"/> <classpathentry kind="var" path="MAVEN_REPO/junit/jars/junit-3.8.1.jar"/> <classpathentry kind="var" path="JRE_LIB" sourcepath="JRE_SRC"/> - <classpathentry kind="var" path="MAVEN_REPO/commonjava/jars/commonjava-lang-2.0.jar"/> - <classpathentry kind="var" path="MAVEN_REPO/commonjava/jars/commonjava-io-2.0.jar"/> - <classpathentry kind="var" path="MAVEN_REPO/commonjava/jars/commonjava-reflection-2.0.jar"/> <classpathentry kind="var" path="MAVEN_REPO/commons-logging/jars/commons-logging-1.0.2.jar"/> - <classpathentry kind="var" path="MAVEN_REPO/commonjava/jars/commonjava-util-2.0-2.jar"/> + <classpathentry kind="src" path="/commonjava-io"/> + <classpathentry kind="src" path="/commonjava-lang"/> + <classpathentry kind="src" path="/commonjava-reflection"/> + <classpathentry kind="src" path="/commonjava-util"/> <classpathentry kind="output" path="target/classes"/> </classpath> Index: project.xml =================================================================== RCS file: /cvsroot/commonjava/commonjava-projects/commonjava-opl/project.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -d -r1.12 -r1.13 --- project.xml 9 Jan 2004 05:07:43 -0000 1.12 +++ project.xml 18 Feb 2004 06:12:10 -0000 1.13 @@ -3,9 +3,9 @@ <project> <pomVersion>3</pomVersion> <id>commonjava-opl</id> - <name>CommonJava Object Parsing Library</name> + <name>OPL: Object Parsing Library</name> <groupId>commonjava</groupId> - <currentVersion>2.1-4</currentVersion> + <currentVersion>2.1-5</currentVersion> <organization> <name>CommonJava Open Component Project</name> <url>http://www.commonjava.org</url> @@ -13,6 +13,40 @@ <inceptionYear>2002</inceptionYear> <package>org.commonjava.opl</package> + <description> + In a drastically simple nutshell, OPL is an XML parser. It supports the notion of parser-per-element + XML parsing, facilitating the construction of complex configurations and other types of objects from + the parsed XML. OPL supports dynamic attribute resolution and packaged parser library definitions, + both in the form of ParserLibrary implementation classes and in the form of XML definitions. In the + latter case, OPL uses a specially-defined meta ParserLibrary and builds the actual parser library + straight from the XML. The following is the algorithm: + <ol> + <li>Encounter new namespace.</li> + <li>If the namespace is not of the form "opl:libname", see if a NamespaceResolver has been + specified. If it has, resolve the namespace. This should render an "opl:libname" namespace.</li> + <li>Check the OPLContext for a mapped library keyed by the namespace.</li> + <li>If no mapped library is found, look for the classpath resource "META-INF/parsers/libname.opl"</li> + <li>If the resource exists, parse the ParserLibrary from the XML in that file.</li> + <li>Use the parser library to lookup/instantiate the appropriate NodeParser implementation for + the element name in question.</li> + <li>Construct an ElementInfo from the current element definition</li> + <li>Call NodeParser's doBeforeChildren() method</li> + <li>Parse sub-elements using this same algorithm</li> + <li>Collect the accumulated element body text if any</li> + <li>Call NodeParser's doAfterChildren() method</li> + </ol> + + In this way, we can start parsing the object before the children are visited, and finish afterward. + All NodeParsers have the ability to retrieve attribute values from the passed in ElementInfo object, + and can lookup their parent parser via the getParent() or findAncestorWithClass() methods. Finally, + if a NodeParser implementation also implements OPLModelRoot, this is meant to be the root node of + the XML document, and contains the additional method getParsedObject(), which will return the result + of the parsing effort. + + SAX and DOM are both supported via specific OPLDriver implementations; other XML parsers can also + be supported by re-implementing this interface with specific code to use the other parser technology. + </description> + <dependencies> <dependency> <groupId>commonjava</groupId> Index: .project =================================================================== RCS file: /cvsroot/commonjava/commonjava-projects/commonjava-opl/.project,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- .project 18 Sep 2003 04:57:09 -0000 1.1 +++ .project 18 Feb 2004 06:12:10 -0000 1.2 @@ -1,19 +1,22 @@ <?xml version="1.0" encoding="UTF-8"?> - <projectDescription> - <name>commonjava-opl</name> - <comment> + <name>commonjava-opl</name> + <comment> </comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.jdt.core.javabuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.jdt.core.javanature</nature> - </natures> -</projectDescription> \ No newline at end of file + <projects> + <project>commonjava-io</project> + <project>commonjava-lang</project> + <project>commonjava-reflection</project> + <project>commonjava-util</project> + </projects> + <buildSpec> + <buildCommand> + <name>org.eclipse.jdt.core.javabuilder</name> + <arguments> + </arguments> + </buildCommand> + </buildSpec> + <natures> + <nature>org.eclipse.jdt.core.javanature</nature> + </natures> +</projectDescription> |
