Download JAR files tagged by pojos with all dependencies

The code consists of example POJOs which should be usable inside a JMS container. i.e. there are no API dependencies on the container whatnosever. Its pretty easy to write useful Message POJOs without any API dependencies whatsoever. There's also a couple of helper classes you can use to provide some JMS helper methods.

The code consists of example POJOs which should be usable inside a JMS container. i.e. there are no API dependencies on the container whatnosever. Its pretty easy to write useful Message POJOs without any API dependencies whatsoever. There's also a couple of helper classes you can use to provide some JMS helper methods.

Bridge to Babylon is a lightweight object relational mapper. The main goal of this library is simplicity. It is intended to be used with POJOs without the need of external XML mapping definition or any kind of annotation. This approache makes Bridge to Babylon the best compromize between simplicity (no xml mapping) and light library footprint: You don't use annotations so you don't have to deploy Bridge to Babylon along with your jars on remote clients.

Bridge to Babylon is a lightweight object relational mapper. The main goal of this library is simplicity. It is intended to be used with POJOs without the need of external XML mapping definition or any kind of annotation. This approache makes Bridge to Babylon the best compromize between simplicity (no xml mapping) and light library footprint: You don't use annotations so you don't have to deploy Bridge to Babylon along with your jars on remote clients.

The ServiceMix Bean component provides integration with beans (POJOs) with the JBI bus to make it easy to use POJOs to process JBI message exchanges. Like in an Message Driven Bean in J2EE a POJO will receive a message from the NMR and process it in any way it likes. Unlike in a JMS component where the coding is already done the Bean component gives the developer the freedom to create any type of message handling but it must be hand coded all the way.

Java Validation Framework (not a JSR-303 implementation). This framework allows to modify (correct) test values; supports validation of localized values; allows to convert values into and from text representation; formats error messages, depending on the context; supports metadata, which allows to check any entity types (not only Java Beans or POJOs) and more. Also this framework has long list of predefined validation components.

Extension for Jackson (http://jackson.codehaus.org) to offer alternative support for serializing POJOs as XML and deserializing XML as pojos. Support implemented on top of Stax API (javax.xml.stream), by implementing core Jackson Streaming API types like JsonGenerator, JsonParser and JsonFactory. Some data-binding types overridden as well (ObjectMapper sub-classed as XmlMapper).

Wicket Web Beans (WWB) is an Apache Wicket component toolkit for displaying and editing POJOs that conform to the JavaBeans specification. Web pages are automatically generated based on bean properties and certain conventions. If necessary, the layout, editability, and actions of these pages can be customized on an exception basis. In other words, the toolkit normally does what you'd expect, but when it doesn't, you can override its behavior.

JCQL is a tool allowing to generate boilerplate java code from existing cassandra schema. It is intended to be used with Cassandra 2.1+ due to support of UDTs (User Defined Types)/Tuples/Collections. Cassandra's UDTs/Tuples/Collections and an ability to introspect schema through java driver make it possible to automatically generate POJOs and corresponding mappers between database and java models. Properly generated java code saves development efforts and is less error-prone compared to hand coding. Accompanied with proper CI and deployment it can also guarantee consistency between database and java models at any point of application lifecycle from development to production rollout. JCQL does not rely on java reflection or annotations which means all discrepancies between actual cassandra schema and what client code expects it to be will be identified during compilation not at runtime in the middle of the night right after production release. No need to worry about Cassandra client code performance implications due to use of reflection.