Osworkflow is a lightweight workflow engine, Code The structure is very simple and clear, as follows: 1) COM. opensymphony. workflow workflow code interface 2) COM. opensymphony. workflow. of course, config refers to the configuration, mainly for osworkflow. XML Parsing
That is, parse the following content:
<Osworkflow>
<Persistence class = "com. opensymphony. workflow. SPI. Memory. memoryworkflowstore"/> <factory class = "com. opensymphony. workflow. loader. xmlworkflowfactory">
<Property key = "resource" value = "workflows. xml"/>
</Factory>
</Osworkflow> 3) COM. opensymphony. workflow. loader refers to the loading. Here it refers to the reading of the process definition, that is, Parsing
The process defined in the workflows. xml file in <property key = "resource" value = "workflows. xml"/> 4) COM. opensymphony. workflow. Query
Used to process expressions 5) COM. opensymphony. workflow. SPI refers to server provider Identification
That is, in osworkflow. XML
<Persistence class = "com. opensymphony. workflow. SPI. Memory. memoryworkflowstore"/>
Look at the subdirectories in this package and you will know: EJB/hibernate/jdbc/memory .... 6) COM. opensymphony. workflow. timer knows the word timer when learning Java.
Schedule7) COM. opensymphony. workflow. util
Util is very useful here, including support for a variety of features: bean shell/condition/caller/JMS/mail/
Listener/status and so on...
