Jmx4Perl provides an alternate way of accessing Java JEE Server management interfaces that are based on JMX (Java Management Extensions). It is an agent-based approach where a small Web application deployed on the application server provides HTTP/JSON-based access to JMX MBeans registered within the application server. It is set up from a handful of Perl modules, which can be integrated seamlessly in your own programs. It also includes a Nagios plugin, check_jmx4perl, a jmx4perl command line tool for remote JMX queries and operations, and a readline-based JMX shell j4psh, with context sensitive command completion and syntax highlighting.
DooPHP is a very fast PHP framework. It enables developers at all levels to rapidly develop robust Web 2.0 applications. It is quite feature rich. DooPHP supports some common stuff found in a Web framework, such as an MVC-base structure, RESTful APIS, a REST client, URI routing, database ORM tools, a model generator, HTTP Digest Authentication, a flexbible compiling template engine, logging and profiling tools, and more.
VRaptor3 is a fully-fledged Java Web framework focused on fast development and maintainable code. It intends to make RESTful application development easy. A resource corresponds to a business logic annotated with its path and HTTP method. It runs inside DI Containers (Spring or Pico out of the box) and, therefore, enables full integration with them. Also, using Hibernate is easier: its session is automatically injected by VRaptor, so you just have to use it. VRaptor3 is refactor-friendly, especially in its redirecting configuration. It is also nicely extensible.
Osgish is a command line shell for OSGi. It is based on the Readline Library, Jmx4Perl, as the OSGi backend, and Aries JMX as the OSGi Management layer. It is different than other OSGi shells, as it is implemented in pure Perl and provides unique features like wildcard support, context-sensitive command line completion, syntax highlighting, bulk lifecycle operations, advanced query facilities, and remoting via HTTP. It uses jmx4perl and Aries JMX OSGi bundles for accessing the OSGi container remotely.
The UniversalContainer class is an attempt to provide a class which can act in a manner similar to the untyped variables, arrays, and hash-maps found in popular scripting languages such as Perl and PHP. The result is a class that can hold a wide variety of data and meta-data in a very flexible structure. UniversalContainers can hold integers, doubles, booleans, single characters, strings, and wide character strings. UniversalContainers may also be used as associative maps between strings and other UniversalContainers, or as arrays of UniversalContainers. Routines for database access and REST programming are included, including a JSON serialization engine.
Google Custom Search is a class that performs searches against a Google Custom Search engine, processing the response (search results and/or spelling suggestions) into properties of the object. It uses either cURL or the HTTP stream wrapper, depending on what is available on the server. The user can also specify the character encoding for the search query. Results are also made available in that encoding.
WSF Staff is Web Service Framework for C++, AJAX, and J2ME that is based on Apache Axis2/C. WSF Staff wraps Apache Axis2/C code into C++, and also provides many additional features: a stateful Web services implementation in C++ with instance support, a synchronous and asynchronous client implementation in C++, AJAX, and J2ME, a service-component architecture implementation, support for RESTful Web services and clients, WSDL support with xsd import and export, J2ME client support (based on ksoap), a flexible and extensible code generator to generate any sort of Web service related source code (not only in C++), security support (users, groups, sessions, ACLs, etc.), and a Web application toolkit (webapp) with widget support.
Huxley is a set of classes that makes it trivial to produce legitimate output for queries made by the prevailing standard of REST queries. Instead of writing a network API with many methods, being run over RPC, you instead write only a couple of methods that are accessed by HTTP GET requests. You then return the results (in either XML, JSON, or text) for processing. XML and JSON are chosen because of the ease by which they can be parsed by most languages. In this way, you open up the scope of your network services to many more people than would otherwise have access to it.