The eworkflow custom workflow system and process definition file adopt the XML format. At the beginning of the design, the DTD file is used to constrain the content of the XML document.
During development, resin3 is used for release, and the validation of the DTD format is not very strict.
Later in the test, I published it with tomcat4 and found that the validation of the DTD file was stricter. Therefore, the DTD file in the XML process definition file was removed.
However, the background JavaCodeThe DTD verification is still performed. Because the DTD file is not read, the verification is successful!
A user has recently released it in tomcat6 and finds that the background verification of the DTD is still unsuccessful! Various release tools are trueTooTooTooDifferent!
Therefore, the latest modification removes the DTD validation in the background class and uses the code for verification to check whether the node definitions in the XML file are standardized.
Download the latest version:/files/webreport/eworkflow.rar (The latest demo version is available. This is deleted)
Qq exchange: 6460267 (workflow)
links:
one of the Web workflow management system development concepts
Web workflow management system development 2 workflow engine
Web workflow management system development 3 visualization process designer
Web workflow management System Development-4 integrated workflows and Custom forms
Web workflow management system development-5 open-source osworkflow-user system transformation
six form permissions for Web workflow management system development and process permission Control
7. Latest DTD format verification and modification in Web workflow management system development
8. Open-source osworkflow Task Management in Web workflow management system development