XFP eXtensible Filtering Pipelines Changeshttp://xfp.sourceforge.net/changes.htmlXFP eXtensible Filtering Pipelines Changesen-usEngine addhttp://xfp.sourceforge.net/changes.htmlEngine add by FT : XFP now uses the Quartz Scheduler, instead of java.util.Timer. This means that you can take advantage of Cron-style scheduling, configurable number of threads and many other Quartz features. Engine/Framework updatehttp://xfp.sourceforge.net/changes.htmlEngine/Framework update by FT : Remove notification and error handling from Framework classes. Engine addhttp://xfp.sourceforge.net/changes.htmlEngine add by FT : Introduction of the "Task" concept, Task = Pipeline + Scheduling + Logging. Information on scheduling and logging is now defined in separate files (scheduling.xml and log4j.xml) for each task. Framework updatehttp://xfp.sourceforge.net/changes.htmlFramework update by FT : DOM Level 3 XPath API now used instead of Xalan XPathAPI. Engine updatehttp://xfp.sourceforge.net/changes.htmlEngine update by FT : Schemas and DTDs updated and moved inside the JAR. Use of namespaces. Project updatehttp://xfp.sourceforge.net/changes.htmlProject update by FT : Global refactoring: the org.sourceforge.xfp package has been renamed to org.xfp. The classes forming the XFP Engine (i.e the server) have been moved to the org.xfp.engine package. The XFP Project is now divided in 3 parts: Framework (org.xfp.*), Engine (org.xfp.engine.*), Filters (org.xfp.filters.*). Project updatehttp://xfp.sourceforge.net/changes.htmlProject update by FT : XFP has been relicensed under the Apache License, Version 2.0