Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.
'Quick and easy' doesn't mean that a resulting application will suffer from a maintainability or a performance issue. Netty has been designed carefully with the experiences earned from the implementation of a lot of protocols such as FTP, SMTP, HTTP, and various binary and text-based legacy protocols. As a result, Netty has succeeded to find a way to achieve ease of development, performance, stability, and flexibility without a compromise.
Apache ESME (Enterprise Social Messaging Environment) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information.
You can hardly turn a web page these days without seeing a story that describes how people are using social networks, whether it is Twitter, Facebook or some other service to develop and build their personal communities.
When solving problems, how useful might it be if a user was able to tap into the collective knowledge of her peers or surrounding groups of people with whom she might naturally network in the workplace setting? How much quicker and with greater precision might she be able to solve daily problems? What if there was a communications mechanism that takes the best of what services like Twitter offers and co-mingled that with readily recognizable business processes? That solution is Apache ESME.
Swirrel is a little framework (in alpha state) which allows to annotate AWT or Swing Components instead of writing listeners. Swirrel reads the annotations and attaches the aproriate listeners automatically. All you have to do is to provide the name of the methods which should be called by the Swirrel listener.
Swirrel is a double edged sword, it can make things much easier, but you can shoot yourself in the foot (hey, a sword you can shoot with!). Please consider carefully if Swirrel is right for you and your project, especially if it contains deeply nested, complex, dynamic and/or time critical GUIs. Note that using Swirrel requires more testing, as things that caused compile time errors before cause runtime errors now. That said I must say Swirrel runs much smoother than I expected.
jConfig is an extremely helpful utility, arming the developer with a simple API for the management of properties. Parts of the implementation are based on the idea that Properties, from Java's perspective, are a good thing, but can be better. jConfig employs the use of XML files for storing and retrieving of property information. The information can be stuffed into nice categories, which makes management quite a bit simpler. The ability to load from a URL is also a nice feature. It allows for a central repository where multiple instances of jConfig can read a single file. The nifty ability to
switch between XML and Properties files isn't fully exploited yet, but will be coming soon. That will mean that the developer would take their existing Properties files and export them to XML. That means less time to get up and get going with jConfig.
With jConfig we hope to have provided the developer with another powerful accessory for his or her's toolbox.
Java applications are typically deployed in multiple environments and platforms, each requiring some unique configuration. JFig gives developers a simple yet powerful tool to manage their applications’ configuration. It allows them to:
1. Store application configuration in one common repository of XML files
2. Access configuration data using one common, convenient interface
3. Easily define multiple configurations, dynamically modifying those variables that need to change in different situations
4. Eliminate the error prone practice of defining the same configuration variables in multiple locations
5. Ease the management, deployment, and control of configuration files
Flesh is a cross-platform, open source Java application designed to quickly analyze a document and display the difficulty associated with comprehending it. It is available for all platforms that support Java. Flesh has been released under the GPL (license for use).
After processing a document, Flesh produces two scores: the Flesch-Kincaid Grade Level and the Flesch Reading Ease Score. Each of these scores is calculated after determining the number of sentences, words and syllables a document contains. Using those numbers, the Flesch-Kincaid Grade Level and Flesch Reading Ease Score can then be calculated
Chameleon can be used to host web applications. Thanks to OSGi and the services offered by Chameleon, these applications exhibit a high degree of modularity, making them extendible and evolutionary. These types of web apps rely on web technologies such as JSON, ATOM and JavaScript.
Applications like these require Chameleon services such as:
json-service
internationalization-service
syndication-service
session-service
rose (json-rpc)
Communication Server
Chameleon is also used to build communication servers. A communication server is a gateway collecting data from field devices, processing them and sending them to an enterprise server (JEE). A communication server must be flexible and extensible in order to manage new devices, as well as remotely configurable.
These applications require Chameleon components such as:
json-service
naming-service
syndication-service
jboss communication stack
jms bridge
Desktop Client
Chameleon is also heavily used to create desktop clients in a modular way. The UI is implemented either with Swing or with Web technologies such as HTML 5 (akquinet ChameRIA). The resulting desktop clients are highly modular and enforce a clear distinction between the view, the controller and the models. The application maintainability benefits greatly from the modularity offered and enforced by Chameleon and OSGi.