Download JAR files tagged by could with all dependencies

This module was created to fix issue DIRSHARED-91 where the embedded Felix instance inside the default LdapCodecService implementation was making it very problematic to deploy the ldap-codec inside an RCP (OSGi) environment and hence Apache Directory Studio could not use it. This module is most likely temporary and will disappear once we are fully OSGi enabled. This module is a plain old jar, not a bundle to avoid accidental reuse as an OSGi module because it contains the version of the LdapCodecService that embeds Felix to make controls and extended ops pluggable in the codec.

The rooster crows immediately before sunrise, the rooster causes the sun to rise. Using GraphX to detect possible causes and effects between time related events. We observe a true causation signal by generating random correlations over same events at different time and back propagate these scores to their most connected events. Finally, we extract the most probable causes and effects together with a score of aggressiveness (how likely an event could explain downstream effects) and sensitivity (how likely an event results from an upstream cause).

Janus is an open-source multi-agent platform fully implemented in Java 1.8. Janus enables developers to quickly create web, enterprise and desktop multiagent-based applications. It provides a comprehensive set of features to develop, run, display and monitor multiagent-based applications. Janus-based applications can be distributed across a network. Janus could be used as an agent-oriented platform, an organizational platform, and/or an holonic platform. It also natively manages the concept of recursive agents and holons. Janus is jointly developed by the multiagent team of the University of Burgondy Franche Comté, and the Grupo de Investigación en Tecnologías Informáticas Avanzadas de Tucumán. This is the new version of Janus fully reimplemented to support the SARL Agent-Oriented Programming Language (http://www.sarl.io).

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.

Spring JdbcTemplate did very convient and useful, but it also has some disadvantages or in another word “inconvenient”. For example, you can’t just pass an object and tell JdbcTemplate to turn it into a sql and save to database just like hibernate does. Alright, you may say “JdbcTemplate doesn’t need you to write hbm.xml , so it’s understandable”. But is it true that this thing is impossible to achieve? And also you know JdbcTemplate can auto turn the result of a query to a list of persistent object a.k.a PO, but when you want to do this you will meet a problem: “How to ?”.Because you can’t find any function of JdbcTemplate to pass a sql and a PO class as we expected. After you google for it, you’ve been told you can create a BeanPropertyRowMapper to deal with this. But isn’t it could be more easier? Based on those questions I create JdbcTemplateTool which can provide these features.

Keystone project is a bootstrap that loads your application and its dependencies from a single archive. With his maven plugin and few line of configuration, your application will be available with all his dependencies in a single archive. The four main ideas which make the difference with other solution are: 1. all dependencies are not exploded in final archive, 'jar' file stay without any modification, so manifest also... 2. use our maven plugin to package all that you need (and we'll loading dependencies automatically for you) 3. you could load native library 4. you could restart your application Why named Keystone? 1. Stone wedge-shaped arch which maintains a vault [Architecture]. 2. A central element on which everything depends.