16 projects tagged "Apache 2.0"
Unlike other Java to Objective-C solutions, Java-Objective-C Bridge doesn't require any code generation of class stubs. It allows you to use any Objective-C libraries and frameworks from Java without having to write any native code. In addition to being able to use Objective-C objects, it allows you to pass Java objects to the objective-c runtime as delegates, so that you can write an entire Cocoa application in Java. The bridge provides 3 levels of abstraction. At the lowest level, it provides wrappers around the Objective-C runtime functions. At a slightly higher level of abstraction, it provides a procedural API to send messages to the Objective-C runtime. At the highest level of abstraction, it provides a Proxy class that serves as a wrapper around any Objective-C object that allows you to work with it in Java almost the same as if you were in Objective-C.
vert.x (formerly known as node.x) is a polyglot asynchronous application framework. It embraces the good bits of event-driven frameworks like node.js without the bad bits. Everything is non-blocking, runs on the JVM, and is polyglot. You can use it from Ruby, Groovy, Java, JavaScript, Python, Clojure, and Scala.
Rerun is a lightweight tool-building framework useful to those implementing management procedure with shell scripts. It will help you organize your implementation into well-defined modular interfaces. Collections of management modules can be archived and delivered as a single executable to facilitate team handoffs. Using the "stubbs" module, rerun will even facilitate unit tests. When users execute rerun module commands, rerun can record execution data into log files which can later be replayed.
MochiPHP is a lightweight framework for PHP that adopts component and page oriented design with a simple database and object-persistence library. Page oriented design: write a class and template pair per page. Form components hide complex HTML markup and user interaction handling. Persistent objects with auto-generated property accessors.
DynaSpring is a dynamic, extensible DSL (Domain Specific Language) tailored for building a Spring Application Context. Like Spring/XML, it is a declarative, tree-structured language; but, unlike XML, it supports all the kinds of abstractions found in common programming languages: conditional evaluation, iteration, definition of functions and variables, etc. DynaSpring also offers a set of utilities that make working with Spring easier and that build upon Spring to give you even more options in structuring your enterprise application.
tadedon is a set of utilities that form a foundation for applications written with one of the many Java frameworks, such as GWT, GIN, Guice, Google App Engine, commons-configuration, and many others. It lets you specify the default configuration of your application and upgrade it automatically on each new release. It can redirect all java.util.logging to slf4j and easily configure logback. It can bind application configuration in a Guice module. It supports @PostConstruct and @PreDestroy annotations (JSR 250) in Guice applications. It lets you annotate your methods with @Transactional annotation. It supports Guice injector stage in your Web application. It lets you test your Guice managed servlets and filters without needing a real servlet container. It lets you use Guice Matchers for matching super class, interface, and type literal annotations. It can inject event bus to your GWT applications with the help of GIN.
SerfJ provides a very easy way of developing Java REST Web applications. It helps you to develop your application over an elegant MVC architecture, giving more importance to convention than configuration. This means, for example, you will not need configuration files or annotations in order to specify which view serves a controller's method. However, SerfJ is very flexible, so if you want to jump over those conventions, you can configure the behavior of your applications as you like. The framework tries to meet the JSR 311 specification, but it doesn't follow every point of the specification, because the purpose is to have a very intuitive library, and some some aspects of the specification are out of the scope of SerfJ.