Making good progress. Have now got the parser fully separated into a lexer/grammar parser that creates AST output, and then a tree grammar parser that will walk a tree and fire actions to turn it into a runtime bean instance.
So right now JFig processes an input applicationContext.jfig file and establishes a map of bean definitions where each bean AST can be dereferenced by name and then an instance returned in a bean factory manner. There's now an API for loading config and then using the resulting object as an "application context" bean factory via making getBean() calls. Instead of declaring java.util.Properties, will be able to use PROPERTIES as a specially recognized name. This is handy for using properties within the applicationContext.xml for initializing other beans. Also, java.util.ArrayList is specially recognized as LIST. So can declare and initialize with array declaration syntax [x, y, z, [a, b, c] ], etc. Strings that are like so: "classpath:sqlmap-config.xml" return a Spring Framework resource instance instead of a string object. At the point where is right now, JFig can act as a mini replacement of Spring. The next step, though, will begin to have the AST walker use Spring APIs to do bean definition and bean registration into an actual Spring bean factory or application context. JFig will ultimately have three variations: 1) Standalone Java-targeting mini bean factory 2) Alternative Spring Framework metadata config parser 3) Standalone Flex ActionScript mini bean factory It would also be possible to use ANTLR to target .NET, but I have no need for pursing that myself at this time. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
