Crispy 1.1.1 reviewDownload
Crispy is a client for remote invocation for different kinds of services via proxies. The intention for this project is a very sim
Crispy is a client for remote invocation for different kinds of services via proxies.
The intention for this project is a very simple API for call different kinds of services (provider/technology). Crispy's aims is to provide a single point of entry for remote invocation for a wide number of transports: eg. RMI, EJB, JAX-RPC or XML-RPC.
It works by using properties to configure a service manager, which is then used to invoke the remote API. Crispy is a simple Java codebase with an API that sits between your client code and the services your code must access.
Crispy provides a layer of abstraction to decouple client code from access to a service, as well as its location and underlying implementation. The special on this idea is, that these calls are simple Java object calls (remote or local calls are transparent).
From Crispy supported service-provider are:
Web-Service (JAX-RPC, for example Axis),
EJB (with JNDI lookup),
XML-RPC (for example Apache XML-RPC)
Burlap and Hessian (Caucho)
REST (REpresentational State Transfer), a pure Crispy implementation,
Here are some key features of "Crispy":
Very easy to use.
Very simple and minimal to configure.
You can call a remote method from Java object, like a local call.
You don't need to know, how the (remote) technology work.
You can easy change the technology (for example from XML-RPC to RMI).
The services don't know a remote-interface or a RemoteException (how RMI).
The parameter can be a complex object (in parts without programming a Serializabler (Marshalling) or Deserializabler (Unmarshalling))
You can intercept methods before and after invocation (for logging, time stopping, ...).
You can modify or extends method parameter and the result (transformation, set a authorization (login) token for the request in the background, ...).
Crispy 1.1.1 search tags