Download JAR files tagged by xapi with all dependencies

A jre client-side implementation of xapi-core-io. xapi-server-api will extend this functionality to servlets.

In order to implement the core XApi dependency injection in gwt, we had to swap out the injection methods themselves with magic methods that call into generated-on-the-fly provider classes.

This module contains only interfaces, annotations and static service classes used throughout XApi.

The core dependencies of the XApi gwt/java cross-platform library. This module contains the basic interface layer, logging, dependency injection and a slew of gwt jre emulation classes.

All jre-specific runtime implementation for dependency injection goes in here. Note that the xapi-core-inject core library can operate without runtime support; so long as your services are correctly mapped in META-INF, you will not need runtime classpath scanning or bytecode lookup.

Everything needed to run a comprehensive dev environment. Just type X_ and pick a service from autocomplete; new dev modules will be added as they are built. The only dev service not included in the uber jar is xapi-dev-maven, as it includes all runtime dependencies of maven, adding ~4 seconds to build time, and 6 megabytes to the final output jar size (without xapi-dev-maven, it's ~1MB).

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)

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other modules, like java.lang.reflect for the reflection submodule, have their super-source here, and generators or other implementations in their own modules. This is to maintain consistency in what is or isn't whitelisted in XApi GWT. Some modules, like appengine, provide dependency-specific super-source in their own packages. This module is for jre, junit and core XApi services.

XApi is a dependency injection, service-oriented, polyglot java framework. It is comprised of standalone modules for use in web, desktop and mobile java applications. This codebase enables complete reuse of all code across your java stack, as well as the ability to easily define your own Platform, so you can build your own customized runtime environment to extend or replace existing platforms. It is currently geared towards servlets and gwt clients, but the target we are currently developing include: java, gwt [webkit, firefox, ie], javafx, playn [android, ios, flash], appengine & vert.x For Google Web Toolkit, we also include reflection support, more complete emulation of java.lang.Class, zero-overhead dependency injection, a range of code generation utilities, and even "magic-method injection" (for production compiles any method in the app can be swapped out with others based on configuration properties, or any AST mangling / code generating methods you wish to write). There is also a bytecode transformer in the works which will replace calls into the DI utility with direct references to static final factories, to allow the java compiler to completely erase all injection overhead in all java runtimes.