Download JAR files tagged by transactional with all dependencies

Yiling Yang, Xudong Guan, Jinyuan You: CLOPE: a fast and effective clustering algorithm for transactional data. In: Proceedings of the eighth ACM SIGKDD international conference on Knowledge discovery and data mining, 682-687, 2002.

The Imixs Workflow engine is a full featured Workflow Management System (WFMS) based on the Java EE specification. The project extends the Imixs Workflow Core API project to fulfill the requirements to a scalable, transactional, robust and simple deployable JEE Workflow System. The Project provides different service components (EJBs) to be used in any kind of Java EE based business application.

The Imixs JEE Workflow is a full featured Workflow Management System (WFMS) based on the JEE5 specification. The project extends the Imixs Workflow API project to fulfill the requirements to a scalable, transactional, robust and simple deployable JEE Workflow System. The Project provides different service components (EJBs) to be used in any kind of business application. All components of the project are build using Maven 2 to simplify the development process and usage of the components in a Java project.

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.

The Virtuoso server module (ks-server-virtuoso) provides an implementation of the Triple Store server-side component (API in ks-triplestore) on top of the OpenLink Virtuoso triple store, a scalable native code triple store that is accessed as an external service. The Virtuoso Sesame driver, which builds on the Virtuoso JDBC driver, is used to remotely access the Virtuoso server for writing data and performing SPARQL queries. For performance reasons, data modification is performed in a non-transactional way, with the module managing possible failures in a way that trigger the external repopulation of the Virtuoso triple store starting from the master copy of data stored in the Data Store component.

This is a demo program that illustrates some of the capabilities of Madura working with Vaadin. Specifically it shows the use of the JPAontainer. The JPAContainer shown here is extended from the one you can find in Vaadin Addons to support Spring's @Transactional notation. It is also using Madura Objects, but that is an interesting incidental because you could use Madura Objects with both. So the objective here is to show a complete working demo of how to configure everything to show a table of data fetched from a database using JPA, including popup edit forms.

An instance filter that collapses instances with a common grouping ID value into a single instance. Useful for converting transactional data into a format that Weka's association rule learners can handle. IMPORTANT: assumes that the incoming batch of instances has been sorted on the grouping attribute. The values of nominal attributes are converted to indicator attributes. These can be either binary (with f and t values) or unary with missing values used to indicate absence. The later is Weka's old market basket format, which is useful for Apriori. Numeric attributes can be aggregated within groups by computing the average, sum, minimum or maximum.

Scala classes to allow more elegant use of Multiverse from Scala. Atm the functionality is quite limited since not a lot of effort was put in the Scala integration. For the 0.6 release Multiverse should be able to work with in Scala written transactional objects configured with the Multiverse annotations. So that would reduce the need for this library, although in Scala they want to have special Scala 'interfaces' that provide some syntactic sugar to use java collections in Scala. So this module would be the good location for that. If anyone would like to help improving the Multiverse/Scala integration, please don't hesitate to join.

[] (https://drone.io/bitbucket.org/tidalwave/thesefoolishthings-superpom-src/latest) A feature-rich SuperPOM for building Java projects. It features: * explicit version configuration for a number of plugins; * easy configurability by means of pre-defined properties to avoid cut & copy of plugin sections. A number of profiles, that can be easily activated, are available for: * Spring-AOP configuration; * different kinds of Continuous Integration tasks, including a full run of QA tools such as JaCoCo, FindBugs, PMD, etc... * deploying WARs and locally running them with Tomcat or Jetty; * creating a Mac OS X bundle for JavaFX applications; * creating .deb packages for both application and services; * a customized release cycle, including all requirements for the Maven Central such as signing, with a 'transactional' behaviour (all artifacts, both the DSCM and the Maven artifacts are prepared on the local disk, so they can be uploaded in a second moment); Remember to customise it ------------------------ If you use it, please remember to change the ```description```,```url```, ```organization```, ```developers```, ```license```, etc... to override those related to the development of this POM.