Tags : Browse Projects

Select a tag to browse associated projects and drill deeper into the tag cloud.

Restlet Framework

Compare

  Analyzed about 6 hours ago

The leading RESTful web framework for Java Do you want to blend your web services, web sites and web clients into unified web applications exposing and consuming RESTful web APIs? Leverage the open source Restlet Framework and its unique Java API available in six consistent editions: Java SE ... [More] , Java EE, OSGi, GAE, Android and GWT! Current versions: 2.2.0 (Stable) 2.3 M1 (Testing) both released on Mar. 27, 2014 [Less]

251K lines of code

6 current contributors

3 months since last commit

46 users on Open Hub

Low Activity
4.69231
   
I Use This
Licenses: Apache-2.0, CDDL-1.0, EPL-1.0

Kauri

Compare

  Analyzed 10 months ago

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.

218K lines of code

0 current contributors

over 4 years since last commit

3 users on Open Hub

Activity Not Available
5.0
 
I Use This

grails-jaxrs

Compare

  Analyzed about 1 year ago

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 want to structure the web service layer of an application in a JSR 311 compatible way but still want to ... [More] 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]

4.62K lines of code

3 current contributors

about 1 year since last commit

3 users on Open Hub

Activity Not Available
5.0
 
I Use This

BIC LCF Server

Compare

  Analyzed 7 months ago

Java reference server for the BIC Library Communication Framework. The Library Communications Framework (LCF) is a set of library interoperability standards which defines a framework for the communication of data between self-service and other library terminal applications to and from library ... [More] management systems. This LCF standard is recommended by BIC as the best way to implement communications between systems within a library, for example between a Library Management System (LMS/ILS) and an RFID Self-Service Solution. [Less]

11.7K lines of code

2 current contributors

7 months since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This

Prudence

Compare

  Analyzed about 1 year ago

Prudence is an open source container and framework for scalable web frontends and network services. It comes in several flavors: Python, Ruby, Clojure, JavaScript, PHP and Groovy. Your applications can support rich clients (AJAX), thin clients (pure HTML), and happy mixes between the two. ... [More] Prudence addresses real-world, practical concerns, from virtual hosting and URI rewriting to flexible server- and client-side caching. [Less]

271K lines of code

0 current contributors

over 5 years since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This

xeerkat

Compare

  Analyzed about 1 year ago

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. Each service is available over both HTTP and XMPP. A service is a rest-style service that can ... [More] 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]

32.6K lines of code

0 current contributors

over 6 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This

tabulasoftmed

Compare

  Analyzed about 1 year ago

Tabula is a Java Web Framework, comprised of several subprojects, such as a server and GUI tools. Right now there is a preview version of the server available for Windows and Linux. The framework is based on SOFEA, removing the UI responsibilities from the server to other applications. The server ... [More] itself 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. The controller layer uses another project of mine, named JTAction. It's a library for handling composite actions. Each action is a state machine, where each state is built by several steps. Actions are cached but can be changed via a remote refresh request. Action steps can be implemented with Java or Groovy scripts. JTActions can also be used as request handlers for the service layer. There is also a custom AOP system which defines an approach to create, edit and apply aspects to JTActions through a rule system based on request parameters. This allows to add for example logging and authorization aspects, and is already used to automatically refresh the REST service layer when any PUT, POST or DELETE methods are performed on the stored rest service configuration objects. The persistence layer uses a custom persistence abstraction layer. Ideally, I would have used JPA, and though I like it, it doesn't support real time changes such as redefining groovy classes. The implementation uses Neodatis ODB, an object based database system, which is still under development, but is showing great promise. There will be SWING-based editors for some of these components, such as configuring REST services, building JTActions from groovy scripts and applying aspects. The goal is to ease development of the whole application, hide any XML details from the developers, instead showing a configuration interface, and support runtime changes of the application. The whole purpose of the project right now is to try out different ideas and approaches to web development. As such, currently this is a proof of concept and should not be used for deployment. Due to time restraints, some aspects of the framework may be changed or removed. The source code also reflects the time restraints unfortunately, but as this is something I plan of using and developing along the way, it will improve. [Less]

23.1K lines of code

0 current contributors

over 7 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This

Tabula web framework

Compare

  Analyzed about 1 year ago

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 deals with business logic and persistence, among other issues. In order to expose this ... [More] 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]

23.1K lines of code

0 current contributors

over 7 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This

anysuites

Compare

  Analyzed about 1 year ago

A suite of personal software on web or RIA.

10.7K lines of code

0 current contributors

about 9 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This

restlet-spring-security

Compare

  Analyzed about 1 year ago

Project dedicated to provide Spring Security authorization/authentification features to Restlet framework.

459 lines of code

0 current contributors

almost 9 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This