Download JAR files tagged by when with all dependencies

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 small subproject regroup most of the stuff needed to build pmd. As some java code has been produced to reduce the use of scripts when generating the website, the build also requires a small jar, which is generated by this pom. IMPORTANT NOTE: the pmd-build.jar does not need to be recompile if you modify any ant or xslt files. You can alter the files that are in the xslt directory and directly uses the appropriate ant or java task. pmd-build should be recompiled and package (and its version incrememented) only if you modify the java code.

Evaluates the worth of a subset of attributes by the level of consistency in the class values when the training instances are projected onto the subset of attributes. The consistency of any subset can never be lower than that of the full set of attributes, hence the usual practice is to use this subset evaluator in conjunction with a Random or Exhaustive search which looks for the smallest subset with consistency equal to that of the full set of attributes. See: H. Liu, R. Setiono: A probabilistic approach to feature selection - A filter solution. In: 13th International Conference on Machine Learning, 319-327, 1996.

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.

Provides basic support of servlet filter. Boilerplate code etc. It provides a boilerplate implementation of the Filter interface. The GenericFilter provides a getter and setter for the FilterConfig object and ensures that this is set when init is called. The init method also calls the configureFilter method after the FilterConfig object is set and can be used by subclasses to process the filter config during initiation. It also provides an empty implementation of the destory method. The only method that requires implementation is the doFilter method. The GenericHTTPFilter extends the GenericFilter class, it provides a doFilter method that attempts to cast the ServletRequest and ServletResponse objects to HttpServletRequest and HttpServletResponse objects. If these objects can be cast successfuly then it calls the doHTTPFilter method and passes the cast objects references. If the objects cannot be cast a ServletException is thrown. The doHTTPFilter method is abstract and must be implemented by subclasses.

Asynchronous publish-subscribe communication library. Features: 1. Listeners are stored using WeakReferences to prevent memory leaks when they are not unsubscribed. 2. Uses fork-join framework for concurrent event delivery. 3. Publish methods returns collection of Futures that represent event notifications. 4. Supports ordered publishing: guaranteed to notify of the events in order they were published. 5. Provides EventSource and EventService interfaces for better integration with IOC containers and alternative implementations.

An low latency, lock free, primitive bounded blocking queue backed by an int[]. This class mimics the interface of {@linkplain java.util.concurrent.BlockingQueue BlockingQueue}, however works with primitive ints rather than objects, so is unable to actually implement the BlockingQueue. This class takes advantage of the Unsafe.putOrderedObject, which allows us to create non-blocking code with guaranteed writes. These writes will not be re-orderd by instruction reordering. Under the covers it uses the faster store-store barrier, rather than the the slower store-load barrier, which is used when doing a volatile write. One of the trade off with this improved performance is we are limited to a single producer, single consumer.

Jadex XML is an XML data binding framework for Java and also for other representations. The main idea of Jadex XML is that neither the XML-Schema on the one side nor the Java classes on the other side should define the binding. Instead, a separate mapping between both is used as a mediation. This allows designing the XML representation independent of the Java side but still being able to connect both as desired. This idea was first put forward by the JiBX data binding framework. Jadex XML pushes it further by combining it with the configuration by exception principle. The framework can detect obvious correspondences between both sides automatically and only needs configuration information when translations are necessary. The configuration information is currently specified directly in form of Java configuration classes.

This is an endorsed version of the original Deployment Client for Oracle GlassFish Open Source Edition. The purpose of the endorsement is to provide a shaded JAR which has the OSGI meta data removed because it causes the original Deployment Client to fail when used within a module running within a GlassFish container due to some class loader configuration conflicts between the container and the deployed module. This issue has been reported to the GlassFish project at https://java.net/jira/browse/GLASSFISH-20856 . It is hoped that it can get fixed so that this workaround project can get deprecated soon.