Search Results for "input-leap"

neoHort: Java PDF&XLSX runtime builder. Based: iText 2.1.7, OpenPdf, JExcelAPI, POI libraries. Xml-based input source with integrated WebJava environment objects. Includes dynamical tag's structures. Demo https://neohort.herokuapp.com/ https://neohort4ape.appspot.com GitHub https://github.com/surban1974/neohort neoHort5 migrated to https://sourceforge.net/p/neohort5 Maven https://github.com/surban1974/neohort/blob/master/README.md

neoHort5:Java PDF&XLS runtime builder-based iText(v.5.*)&JExcelAPI library.Xml-based input source with integrated WebJava environment objects (beans e.c.)Include dynamical tag's structures: cycle,condition,e.c. Support iText 5.* Demo https://neohort4ape.appspot.com GitHub https://github.com/surban1974/neohort Maven <repositories> <repository> <id>neohort-mvn-repo</id> <url>https://github.com/surban1974/neohort/raw/mvn-repo/</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> </repository> </repositories> <dependency> <groupId>com.github.surban1974.neohort</groupId> <artifactId>neoHort5</artifactId> <version>5.2.8</version> </dependency> <dependency> <groupId>com.github.surban1974.neohort</groupId> <artifactId>neoHort5-poi-xlsx</artifactId> <version>5.2.8</version> </dependency>

...The provision of a JEDI document is based on a synchronous processing performed by the JEDI core engine triggered by an end-user request (through HTTP request or RMI call). The content of a JEDI document (i.e. the input of the JEDI service), must be an XML stream regardless of the source. Such data is subsequently processed through one or more XSL transformations in order to provide the user with the document in the required format.