Crispy › Click to download › Updated Info

The intention for this project is a very simple API to 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. It 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).CRISPY = Client for Remote Invocation for different kinds of Services via ProxYs.



From Crispy supported transport providers are:

• Web-Service (JAX-RPC, for example Axis),
• XML-RPC (for example Apache XML-RPC),
• Burlap and Hessian (Caucho),
• RMI,
• EJB (with JNDI lookup),
• JBoss Remoting,
• REST (REpresentational State Transfer), a Crispy implementation with commons httpclient and
• Http invoker (http call with serializable Java objects), a Crispy implementation with commons httpclient
• CORBA (experimental)

What ist the special on this framework?

• 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, ...).

Where you can set in Crispy?

If two or more communication partner exist:

• In Service Oriented Architecture (SOA).
• By Enterprise Service Bus (ESB).
• Client for Java Business Integration (JBI).
• Communication by a Rich Client Platform (RCP) with the server (Client/Server Architecture).
• Communication between service consumer (Client) and service provider (Server) (in the WWW or intranet).
• And so on.