Download JAR files tagged by mode with all dependencies

This module of Akka is marked as experimental, which means that it is in early access mode, which also means that it is not covered by commercial support. An experimental module doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. An experimental module may be dropped in major releases without prior deprecation.

This module of Akka is marked as experimental, which means that it is in early access mode, which also means that it is not covered by commercial support. An experimental module doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. An experimental module may be dropped in major releases without prior deprecation.

This module of Akka is marked as experimental, which means that it is in early access mode, which also means that it is not covered by commercial support. An experimental module doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. An experimental module may be dropped in major releases without prior deprecation.

Smart Commit JDBC Driver enables 'smartcommit' mode for all JDBC drivers. In Smart Commit mode a JDBC connection will execute all queries in autocommit mode until it encounters a write operations. From the first write operation until the following commit or rollback, the connection will operate in transactional mode. It will then switch back to autocommit and remain in autocommit until it once again encounters a write operation. Using a JDBC connection in Smart Commit mode will reduce the number of read locks needed. Operating a JDBC connection in Smart Commit mode effectively reduces the isolation level of a transaction to READ_COMMITTED for all queries that are executed *BEFORE* a write operation in a transaction. All queries that are executed *AFTER* a write operation in a transaction, will be executed using the configured isolation level of the JDBC connection.

It helps to quickly make settings for class and its fields of with properties XML. Instead of create a lot of files to describe every class and its fields it use describing by type, by name. E.g. setting "java.lang.Integer"-"INTEGER NOT NULL" will be assigned fo every field of this type. Of course it can be overriden by settings for field name and so on. It is used by beige-web to describe how to render an entity and convert from HTML value. It is used by beige-orm to describe how to map an entity to a DBMS. It make simple settings - Map<String, String>, e.g. "title"-"Beige ORM 1.1", class settings Map<String, Map<String, String>>, e.g. "org.mode.Customer"-["defaultOrder"-"ITSNAME", "wdgFilterOrder"-"filterOrderStd"], fields settings Map<String, Map<String, Map<String, String>>>, e.g. "org.mode.Customer"-["itsId"["wdgNew"-"null", "wdgFilter"-"filterNumber"]]

This powerful reporting library aims to simplify producing reports using iText. The most demanding and coding intensive tasks when producing reports with iText are how to get from data to report elements, how to style those blocks and how to evaluate (debug) the resulting report layout. Exactly those three tasks are simplified by this library: xml configuration and/or annotations to transform existing Java data objects into report block, provide styling information (css like, syntax independent) seperate from code, a firebug like debug mode to help evaluate your report.

This powerful reporting library aims to simplify producing reports using iText. The most demanding and coding intensive tasks when producing reports with iText are how to get from data to report elements, how to style those blocks and how to evaluate (debug) the resulting report layout. Exactly those three tasks are simplified by this library: xml configuration and/or annotations to transform existing Java data objects into report block, provide styling information (css like, syntax independent) seperate from code, a firebug like debug mode to help evaluate your report.

The HTTP server module (ks-server-http) implements the Web API of the KnowledgeStore, which includes the two CRUD and SPARQL endpoints. The CRUD Endpoint supports the retrieval and manipulation of semi-structured data about resource, mention, entity and axiom records (encoded in RDF, possibly using JSONLD), and the upload / download of resource representation. The SPARQL Endpoint supports SPARQL SELECT, CONSTRUCT, DESCRIBE and ASK queries according to the W3C SPARQL protocol. The two endpoints are implemented on top of a component implementing the KnowledgeStore Java API (the Store interface), which can be either the the KnowledgeStore frontend (ks-frontend) or the Java Client. The implementation of the module is based on the Jetty Web sever (run in embedded mode) and the Jersey JAX-RS implementation. Reference documentation of the Web API is automatically generated using the Enunciate tool.