Download JAR files tagged by objects 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 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.

eFaps is a framework used to map objects with or without attached files to a relational database and optional file systems (only for attaches files). Configurable access control can be provided down to object and attribute level depending on implementation and use case. Depending on requirements, events (like triggers) allow to implement business logic and to separate business logic from user interface. The framework includes integrations (e.g. webdav, full text search) and a web application as 'simple' configurable user interface. Some best practises, example web application modules (e.g. team work module) support administrators and implementers using this framework.

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.

This powerful reporting library aims to simplify producing reports using iText. Looking at producing reports with iText the most demanding tasks are how to get from data to report blocks, how to style those blocks and how to evaluate (debug) the resulting report. Exactly those three major tasks are well supported by the VectorPrint report library: - (combination of) xml configuration and annotations to transform existing Java data objects into report block - provide styling information (css like) seperate from code - a firebug like debug mode to help evaluate your report.

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.

This module contains a classpath scanner, and bytecode reader. It is useful in any java runtime environment, and allows java code to parse bytecode into a meta structure of classes, annotations, methods and fields. This meta structure is used throughout xapi to allow us to extend java structures in a cross-platform compliant way (exposing services and service objects so you can hack support for whatever runtime you need). It is especially useful for fast runtime injection, and as an extensible structure during codegen (which exposes mutable interfaces for our meta structure)

JAXB 2.1.x XJC Boolean-Getter Plugin This plugin causes getter methods for Boolean Objects to be called "getXX" instead of "isXX". Downloaded from http://fisheye5.atlassian.com/browse/~raw,r=1.1/jaxb2-commons/www/boolean-getter/index.html on 18/03/10 Yiannis Paschalidis Sanity4J was created to simplify running multiple static code analysis tools on the Java projects. It provides a single entry point to run all the selected tools and produce a consolidated report, which presents all findings in an easily accessible manner.

Siena is a persistence abstraction layer made in Java with various implementations: * siena-jdbc: persists objects into a relational database using JDBC (status: deeply tested) * siena-gae: persists objects into the Google App Engine's datastore using its low-level API (status: beta) * siena-sdb: persists objects using Amazon's SimpleDB (very experimental) * siena-remote: persists objects remotely using a remote web application that uses siena. (planning) Siena is also: * Intrusive. You make a class persistent by extending a certain class. Relationships are defined also in an intrusive way. * Simple. Simplicity is the most important thing. * Limited. Due to the simplicity there are several unsupported things such as JOINs. * Extensible. There are two interfaces you can implement on your own way.

BRAP is a Java and Android remoting protocol that uses native Java object serialization, encapsulated in HTTP. It aims to be an alternative to Spring HttpInvoker and Spring Security especially when you don't need or want the dependencies of Spring in your client, for example when building a rich client app or an Android app where size is important. The authentication mechanism lets you use your own domain objects as credentials. Server configuration can be expressed solely in web.xml or by subclassing the ProxyServlet but there is also an optional SpringProxyServlet available for seamless Spring Integration. BRAP focuses on being easy to use, small in size (9 kb), yet powerful and extensible. The client uses a pluggable TransportProvider with default implementations for HttpURLConnection and Apache HttpClient.