Projects tagged ‘restlet’

Lightweight REST framework for Java Do you want to embrace the architecture of the Web and benefit from its simplicity and scalability? Leverage our innovative REST engine and start blending ... [More] your Web Sites and Web Services into uniform Web Applications! [Less]

This project's main objective is to provide routing functionality to PostGIS / PostgreSQL. pgRouting is part of PostLBS, which provides core tools for Location Based Services (LBS) as Open Source ... [More] Software (OSS). Its tools are similar to those found on proprietary software. [Less]

Kauri is a Java-based framework for RESTful (web) application development. It's based on Restlet, jQuery, Maven, Spring and the sweaty hands of its core development team.

Introductiongrails-jaxrs is a Grails plugin that supports the development of RESTful web services based on the Java API for RESTful Web Services (JSR 311: JAX-RS). It is targeted at developers who ... [More] want to structure the web service layer of an application in a JSR 311 compatible way but still want to continue to use Grails' powerful features such as GORM, automated XML and JSON marshalling, Grails services, Grails filters and so on. This plugin is an alternative to Grails' built-in mechanism for implementing RESTful web services. At the moment, plugin users may choose between Jersey and Restlet as JAX-RS implementations. Both implementations are packaged with the plugin. Support for Restlet was added in version 0.2 of the plugin in order to support deployments to Google App Engine. Other JAX-RS implementations such as RestEasy or Apache Wink are likely to be added in upcoming versions of the plugin. Please let us know if you'd like to have them added. Latest ReleaseRelease notes for grails-jaxrs version 0.3 FeaturesMakes the JSR 311 (JAX-RS) available to Grails applications for developing RESTful web services. New Grails artefact types, Resource and Provider, for JAX-RS classes. JAX-RS Resource classes under grails-app/resources are auto-detected and can be modified at runtime. JAX-RS Provider classes under grails-app/providers are auto-detected and can be modified at runtime. Extended Grails command line interface Create new resources and unit test templates via grails create-resource . Generate ready-to-use resources from domain objects via grails generate-resources . Scaffolding Generate RESTful service interfaces for Grails domain objects Content negotiation support for XML and JSON representations Ability to use any Grails feature within JAX-RS resources and providers such as GORM can be for interacting with persistent domain objects. Grails filters for intercepting requests to JAX-RS resources. Grails services which can be auto-injected by name. Entity providers Domain object providers that convert between Grails domain objects and XML or JSON representations Support classes for developing custom entity providers Support for content negotiation using the Accept request header Plugin users may choose between Jersey and Restlet as JAX-RS implementations by means of configuration. grails-jaxrs applications can be deployed to Google App Engine (GAE). Getting startedIf you've used an older version of grails-jaxrs take a look at the release notes for version 0.3 Detailed installation instructions can be found on the InstallationInstructions page. First steps with the grails-jaxrs plugin are described in the GettingStarted guide. Advanced grails-jaxrs features are described on the AdvancedFeatures page. [Less]

Edgebox, the application-over-web development toolkit News11/16/08, RestGwt 0.0.1 released. Maven repository and site are also updated. Edgebox maven repository edgebox-release ... [More] http://edgebox.googlecode.com/svn/repo-release/ edgebox-snapshot http://edgebox.googlecode.com/svn/repo-snapshot/ [Less]

JATComm is an application to use a mobile phone connected to your PC to send SMS messages. It has three parts: * Serial Connection - handles the serial connection to the mobile phone using ... [More] RXTX library and sends SMS messages through AT commands. * SMS Server - a server using RESTlet library to deploy a remote service to send SMS messages. * SWING client - uses RESTlet to connect to the remote service as a client. The project supports sending message messages with a number and message, or using a XML version of a single SMS, or a XML version a batch of SMS messages, all sharing the same prefix. It uses XStream for XML to Object mapping. The AT code was done for a Motorola V980 mobile phone. [Less]

Restils provides common API that is useful for RESTful projects written on the Java platform. The library consists of: ResourceOrganizer which makes the consumption of distributed ... [More] resource-oriented web services easier JAAS CasLoginModule which provides a mechanism to leverage the CAS authentication protocol FaultBarrier which facilitates the recovering of concurrent runtime failures [Less]

Tabula is comprised of several subprojects, such as a server and GUI tools. The framework is based on SOFEA, removing the UI responsibilities from the server to other applications. The server itself ... [More] deals with business logic and persistence, among other issues. In order to expose this functionality, there is a REST service layer, implemented with the RESTlet library. I've created a simple XML format specification to declare and configure the services, allowing for runtime changes. The implementation supports Java and Groovy classes as request handlers. The main goal of the framework is to reduce app restarts during development as much as possible, while providing a simple environment for prototyping and developing small to medium applications. [Less]

A suite of personal software on web or RIA.

Xeerkat is a P2P computing framework that utilizes XMPP as a communication protocol. The basic model is that of a agent computing where an agent runs a number of services that available to peers. ... [More] Each service is available over both HTTP and XMPP. A service is a rest-style service that can communicate using any web-oriented protocol and implemented as a Restlet Application. This allows reuse of any Restlet implementation as a agent service. An agent-oriented set of services are provided throught Restlet context to facilitate building services. News2008-07-07: The 2.1.0 release is now available. See the release notes for a list of changes. 2008-07-07: The 0.6.0 release of the XMPP server is now available. It now implements a heartbeat presence message to detect dead clients and also contains several fixes for stability related to network connections. StatusThe current code base is very stable an usable for applications. The only major missing feature is better discovery mechanisms. The current code relies upon presence management and works well in situations where every "worker" agent knows a common "broker" agent". Those workers who have the same broker agent will know about each other by periodically checking with the broker agent. The current version is 2.1.0 and now uses an installer. Just double-click on the jar file or type: java -jar xeerkat-2.1.0.jarXMPP ServerWhile the Xeerkat agent code will work with any XMPP server I've been frustrated by the lack of features for my needs in may other XMPP servers. As such, I built an experimental server that utilizes the same infoset processing technology and restlet engine as the client. The current version supports basic presence handling and rosters and also supports dynamic configuration of "virtual hosts" via Atom feeds. The server requires a basic auth webservice for authentication. I use my authservice from the atomojo project. The server does not support server-to-server connections and so does not federate with other services. It does support inter-communication between different hosts on the same server. These documents should help the brave try out this server Server Administration Using Atomojo's Auth Service HistoryThe Xeerkat project grew out of a P2P grid computing project that originally used JXTA. Eventually issues with JXTA forced a re-examination of what technologies were needed. As each peer is actually on the edge, XMPP was a good choice for a communication technology. The project was originally hosted as xeerkat at java.net and was moved to this project. The original code is available there with the JXTA support and that is considered the "1.0" version. This code has been completely refactored and removes many of the restrictions to XML and opens up the ability to create P2P REST-oriented services. Underneath, XML is used as appropriate in the XMPP transport. XMPP URI ReferencesXeerkat uses URIs to tunnel requests over XMPP. The general format of the URI is: xeerkat://{sender-id}/{sender-resource}/{receiver-id}/{receiver-resource}/{path}The final {path} part of the URI is the same path as the service over HTTP. For example, if the 'status' service is available from: http://localhost:8080/statusthen for sender 'test@talk.example.com' and agent host 'peer@talk.example.com', that same service is available (depending on resource names) at: xeerkat://test@talk.example.com/shell/peer@talk.example.com/agent/statusYou can also omit the resource of the receiver: xeerkat://test@talk.example.com/shell/peer@talk.example.com//statusAs the local client makes a connection to the XMPP server as themselves, the "host" information is the local connection and that's why the URI starts with your XMPP id. Since XMPP messaging is asynchronous, a client can use the sxeerkat scheme to simulate a synchronous request. DocumentationGetting Started with Xeerkat The Agent API documentation. A Distributed Ping ExampleThe simplest test infrastructure is distributed ping where an single agent is going to "ping" other agents for a certain number of times. All Xeerkat services are just Restlet Application instances and so we need to do is write a simple Restlet Application and then package it for the agent. The main part of a Application in Restlet is the createRoot method. Here we'll create a Router to route requests: public Restlet createRoot() { // Create a router for the root of the application Router router = new Router(getContext()); and then we'll create a main restlet for processing ping requests: Restlet main = new Restlet(getContext()) { public void handle(Request request, Response response) { } } and then we attach it to the router: router.attach("",main); router.attach("/",main);The two attach statements above let the service respond to ping and ping/. The service receives an XML message with the number of requests. We won't bore you with the details of parsing the XML. Once the number is known, all that is necessary is to loop until a maximum time has been reached or the number of pings have been received. That code looks like: // loop till we've timed out or received all the responses while(stat.receivedNow, pings are received at "/ping/echo" and so we just define a simple restlet to handle them: router.attach("/echo",new Restlet(getContext()) { public void handle(Request request, Response response) { response.setEntity(request.getEntity()); response.setStatus(Status.SUCCESS_OK); } });The neat bit here is that all these resources are available over both HTTP and XMPP. The last step is to package the service for the agent. The agent currently requires the service to packaged as a separate jar file. At the root of the jar file there must be an 'application.xml' resource that looks like: That's it. The full source is available from subversion as PingApplication.java. [Less]