Search Results for "which"

...The low-level components, XMLWriter and XMLReader, can be used directly, for a higher control compared to the EasyML Facade. Security policies can also be defined, specifying black- or whitelists of types which are allowed at deserialization time. EasyML on GitHub: http://github.com/cordisvictor/easyml-lib

This project is now abandoned in favour of MorganaXProc-III which implements XProc 3.0: https://sourceforge.net/projects/morganaxproc-iiise/ MorganaXProc is a full implementation of XProc: An XML Pipeline Language (W3C Recommendation 11 May 2010) written in Java, supporting all required and optional steps, the steps proposed on EXProc.org and also the document templating steps "p:in-scope-names" and "p:template".

...Later, the XML data may easily be processed by standard tools such as XSLT to produce HTML, PDF, dot graphs etc. Technically, this is done by wrapping the class and interfaces of the com.sun.javadoc packages into JAXB annotated classes, which allows for an easy serialization.

FFEntityFramework is an Object-Relational Mapping Framework (O-R Mapping / Object Persistence) for .NET with built-in features like Xml-Serialization, Model-View-Controller-Framework or UndoManagement ... All these Components use the same Meta-Base which can be definied via Attributes (Annotations) on your Business-Classes. Nevertheless differences between Xml- and Db-Serialization can be made via an enum MetaUsage (Database, Xml, Internal …). For Example you can define a Key-Column which is only used for Db-Serialization and excluded for Xml-Serialization. The same can be done with References, Delegations &c. ...