Interoperabilidad RESTful entre Java y .NET

La firma francesa Noelios a liberado el Milestone 5 de Restlet 2.0, la nueva versión de su proyecto de código abierto Restlet, la cual incluye al Restlet Extension for ADO.NET Data Services.

Restlet es un framework ligero que ayuda a desarrollar clientes y servicios REST en la plataforma Java. Mientras que ADO.NET Data Services (aka Astoria) permite la creación de servicios REST que exponen datos, así como los clientes que los consumen, dentro de la plataforma .NET de Microsoft. Restlet Extension for ADO.NET Data Services es el puente entre ambos.

Restlet Extension for ADO.NET Data Services es el resultado de la colaboración entre Microsoft y las tecnologías Noelios que facilita a los desarrolladores Java el aprovechar los servicios brindados por ADO.NET Data Services. Para ello Restlet Extension for ADO.NET Data Services brinda una API de alto nivel que extiende las capacidades básicas del Restlet Framework para proporcionando acceso a datos remotos que son hospedados en servidores ASP.NET o la plataforma de Windows Azure.

La arquitectura general se puede describir a través del siguientes diagrama de componentes:

Jean-Christophe Cimetiére escribió un artículo detallando los esfuerzos de colaboración, y el que menciona que los desarrolladores Java utilizarán un generador de código para crear clases Java que se corresponden a las entidades de datos expuestos a través de ADO.NET Data Services. La aplicación Java puede entonces acceder a los datos a través de una simple llamada a un método. Los componentes de tiempo de ejecución en el motor de Restlet y la extensión cuidan la comunicación entre la aplicación cliente Java y ADO.NET Data Services.

Otros esfuerzos de interoperabilidad con Java dirigidos por Microsoft incluyen Apache Stonehenge, Azure. NET Services SDK for Java. Más información acerca de los esfuerzos de interoperabilidad entre Java y .NET se pueden encontrar en Microsoft’s Interoperability Bridges & Labs Center.

Mayor información:

• New bridge broadens Java and .NET interoperability
• ‘Restlet’ Java Framework Now with ADO.NET Data Services Support
• Noelios Technologies: Restlet bridges ADO.NET Data Services and Java
• Interoperability Bridges: Restlet Extension for ADO.NET Data Services
• Restlet Wiki: ADO.NET Data Services extension

After a successful collaboration in February with Microsoft, we continued to explore the interoperability opportunities between Microsoft and Java technologies, leveraging REST and Restlet. Today, we are happy to announce the result of several months of hard work: a new interoperability bridge between Java and ADO.NET Data Services!

Microsoft’s strategy

In order to understand how central the Web and REST are becoming for Microsoft, it is enlightening to discover their new strategy elaborated by Ray Ozzie, Microsoft’s Chief Software Architect. It is called Software + Services and recognizes the ubiquity of the Web and the need to mix both locally running software and cloud computing services in a unified way.

From vision to reality, there is often a long way to go, but this time Microsoft is serious about the Web and genuinely embracing REST. For a few years now, they have been progressively building on their strategy, through Windows Azure, a comprehensive cloud computing platform, and through online extensions to their classic products like Office Live, XBox Live or Windows Live.

ADO.NET Data Services

One of the key technologies they leverage to achieve their plans was launched in 2007 under the code name “Astoria”. It drew much attention in the REST community at this time as it was, with Ruby on Rails’s Active Resource technology, the sole way to automatically expose a data models as RESTful Web services.

Since then, it has matured and became an actively maintained technology called ADO.NET Data Services. You can read an overview paper on MSDN and browse their extensive technical documentation for details about their REST API which leverages AtomPub.

Interoperability with Java

As RESTful Web services, you could use any HTTP toolkit to access them, to the exception of the authentication step which relies on a custom scheme, quite similar to the one used by Amazon for its Web services. However, you are not very productive this way, especially when you know that ADO.NET Data Services describe themselves through extensive metadata.

So far, beside client toolkits for Microsoft technologies such as .NET and Silverlight, only the PHP language had an easy solution to interact with those services. Today, with the release of Restlet 2.0 M5, we are proud to announce a similar offer for Java developers, cleanly leveraging the Restlet Framework.

With the support from Microsoft and especially Stève Sfartz, Architect Lead at Microsoft France, we built a high level client that is able to generate client Java classes from exposed metadata and to easily manipulate the remote entities as if they were local. The current feature scope covers most of the use cases, but keep in mind that we don’t cover all the available features available yet.

This new Restlet extension has been extensively covered by Jean-Christophe Cimetiere, Sr. Technical Evangelist from Microsoft Corp Interoperability team, in this new blog post.

Extension documentation

In order to briefly illustrate how the extension works, you can read the dedicated extension page in the Restlet user guide. It shows some simple code to access to a data service, one provided for the Open Government Data Initiative (OGDI), a recent effort launched by Microsoft to expose government data sources as RESTful Web services.

In addition, to the regular Javadocs of the extension, a complete tutorial is also available on the wiki to get you started in minutes with a detailed example. Now, if you have a .NET developer friend, you could ping him and set-up a plug scenario!

Launch coverage

• Infoworld – Java developers get .Net data link
• eWeek – Microsoft, Noelios Bridge Java, .NET with REST
• Stève Sfartz – Extension Restlet pour ADO.NET Data Services (French)
• Mike Flasko – Restlet [...] Now with ADO.NET Data Services Support
• The H Open – REST-based bridge connects Java and .NET
• Visual Studio Mag. – Bridge Connects Java to ADO.NET Data Services
• OakLeaf Systems – Live Windows Azure Apps, Tools and Test Harnesses
• LeMagIT – Noelios utilise REST pour relier les données .Net et Java
• hwsw – Híd a Java és a .NET között (Hungarian)
• IDG.se – Microsoft kopplar ihop Java med Dotnet (Swedish)
• heise – REST-basierte Brücke verbindet Java mit .NET (Dutch)
• Programmez! – Un pont d’interopérabilité [...] (French)
• Le Journal du Net – Le français Noelios relie Java et .Net (French)
• dot net pro – Brücke zwischen Java und .NET (Dutch)
• Peter Galli – New Bridge Broadens Java and .NET Interoperability
• InfoQ – RESTFul Bridge Between Java And .NET Released
• Dave Bost – Interoperability and Open Source efforts at Microsoft
• NetworkWorld – Microsoft, Noelios release new bridge [...]
• SearchSOA – Restlet framework wrestles RESTful Web applications
• RedmondDeveloper – A Dose of Java for ADO.NET Data Services
• Application Servers – Restlet compatible ADO.NET
• Java Posse – Episode 282
• Fryan Valdez – Java Extension for ADO.NET Data Services

We have just reached a new milestone on our exciting Restlet 2.0 roadmap! Our main focus was stability and refactoring after the major goals achieved in Restlet 2.0 M4, for example with the automated editions support and some deep API changes.

Summary of the main changes

• About 20 bugs were fixed, including a long standing one related to the integration of Restlet with Tomcat and a blocking issue under Macintosh.
• Most dependencies were updated to their latest version: Grizzly 1.9.18b, Jetty 7.0 RC6 and so on.
• For better API organization, we moved Message, Request and Response classes from the org.restlet.data to the org.restlet package as they are core artifacts of the API used in Uniform interface. We also moved Template and Variable classes from “org.restlet.util”  to “org.restlet.routing” package.
• In order to support both inbound and outbound routing and filtering of calls for Restlet applications, we have added two properties: “inboundRoot : Restlet” and “outboundRoot : Restlet” to the Application class and deprecated the “root : Restlet” property. This will allow you to easily provide features such as preemptive authentication with the recently added ClientResource class.
• The ServerResource class has been refactored for a cleaner integration between annotation-based and method-based call processing.
• A new extension for Microsoft ADO.NET Data Services (previously known as “project Astoria”) was added. It provides a high-level client API based on the ClientResource class that lets you access remote Data Services hosted in an ASP.NET servers or on the Windows Azure cloud computing platform. The extension contains both a code generator for the representation beans and a runtime layer. This extension is in the “org.restlet.ext.dataservices” package and depends on “org.restlet.ext.atom” and “org.restlet.ext.xml” extensions.”
• The JAXB extension now has its helper to support transparent conversions

Direct contributors

• Bob Resendes
• Bruno Harbulot
• Carsten Lohmann
• Denys Hryvastov
• Dustin Jenkins
• Evgeny Shepelyuk
• Fabian Mandelbaum
• Guido Schmidt
• John Logsdon
• Marcelo Ochoa
• Olivier Bruchez
• Patrick Logan
• Philippe Mougin
• Remi Dewitte
• Rhett Sutphin
• Rob Heittman
• Sanjay Acharya
• Tal Liron

Thanks to all others who helped us in various ways!

Additonal resources

Changes log:
http://www.restlet.org/documentation/2.0/jse/changes

Download links:
http://www.restlet.org/downloads/testing

Maven repositories:
http://maven.restlet.org is updated on the 1st and 15th of each month
http://maven.noelios.com is updated daily with new artifacts (access reserved to subscribers)

We are very happy to announce that we have agreed with Manning to publish a “Restlet in Action” book that will cover in depth the upcoming 2.0 version of the Restlet Framework.

Our goal is to have the book published early in 2010. However, you will not have to wait so long to start reading it… You will be able to use Manning Early Access Program (MEAP) to get an online access to draft chapters as they are written. This will give you an opportunity to send us feed-back via an online forum.

Even better, you can download the green paper “Rethinking Web Development with REST and Restlet” that was published today on Manning’s site and that is based on the chapter 1. Here is also the expected table contents:

Part 1: Getting Started

• 1. Rethinking Web development
• 2. Designing a RESTful Web API
• 3. Beginning a Restlet application
• 4. Deploying a Restlet application on premises

Part 2: Getting Ready To Roll Out

• 5. Exposing and consuming Restlet representations
• 6. Securing a Restlet application
• 7. Documenting a RESTful Web API
• 8. Enhancing a Restlet application

Part 3: Further Usage Possibilities

• 9. Deploying a Restlet application in the cloud
• 10. Using Restlet in browsers and mobile devices
• 11. Embracing the Semantic Web
• 12. Looking beyond this book

As always, we are looking forward to getting your feed-back on this project, what you expect from it, what you think about the green paper and the overall table of contents.

Update 1: The table of contents has been refreshed to match the latest manuscript version

Update 2: The book is now available in early access !

After Restlet 1.2 M2 and 2.0 M3 releases that introduced major API changes for resources and security, we wanted to focus this new milestone on stability and on the automated support of Restlet editions.

Here is a summary of the main changes :

• The packaging has been reworked to provide separate distributions for each edition that we support: Java SE, Java EE (with Servlet support), Google Web Toolkit, Google App Engine and Android. In addition, the porting of the main source code base to each edition is now fully automated, ensuring a constant synchronization in term of features and bug fixes. All extensions and API features aren’t (or can’t be) supported in all editions, but the API is consistent. As a side effect, the “org.restlet.gwt” package has been moved to the regular “org.restlet” one.
• The ConverterService has been improved to automatically serialize POJOs into XML, JSON and other serialization formats such as regular Java serialization or long term bean persistence. We leverage XStream for automatic XML/JSON marshalling and unmarshalling. Note that the JAX-RS extension now also relies on this improved conversion service!
• Content negotiation was rewritten to support all possible dimensions such as media type, language, character set or encoding.
• A new FTP client connector was added in the “org.restlet.ext.net” extension, based on the JDK’s URLConnection class. It is limited and only support GET methods.
• The RDF extension was improved with a new RdfClientResource class facilitating the navigation in the Web of Data.
• A new ROME extension was added to support several versions of RSS and Atom syndication feeds formats. This extension is complementary with the existing Atom extension which is fully based on Restlet API.
• Character sets support was enhanced, fixing an issue with Macintosh and adding new constants in the CharacterSet class for all common ones defined by IANA. Also, the default language used for representation is now dynamically retrieved based on the JVM setting instead of English/US.
• Added client and server RIAP connectors that use a protected singleton unique in the JVM.
• The org.restlet.Uniform abstract class has been refactored into an interface with a single handle(Request, Response) method. Its logic has been moved to the org.restlet.Client class. This allows us to leverage it for asynchronous calls, as we already do in the GWT edition.
• The org.restlet.routing package has been enhanced with new Validator and Extractor filters containing logic found in the new deprecated Route class, replaced with a more specific TemplateRoute class. Those changes should be transparent for most applications using the Router class to attach Restlets and resources using URI templates.

Direct contributors

• Alexander Horn
• Andrew Moore
• Arjohn Kampman
• Aron Roberts
• Avi Flax
• Bob Resendes
• Bruce Cooper
• Bruno Harbulot
• David Fogel
• Dustin N. Jenkins
• Evgeny Shepelyuk
• Florian Georg
• Frank Hellwig
• Gabriel Ciuloaica
• Joe Nellis
• John Logsdon
• John Wismar
• Jonathan Hall
• Martin Krasser
• Matt J. Watson
• Maxence Bernard
• Niall Gallagher
• Nicolas Janicaud
• Nirav Shah
• Olivier Monaco
• Remi Dewitte
• Schley Andrew Kutz
• Serge Ilyn
• Simon Reinhardt
• Stuart MacKay
• Sylvain Pajaud
• Thomas Cozien

Thanks to all others who helped us in various ways!

Additonal resources

Changes log:
http://www.restlet.org/documentation/2.0/jse/changes

Download links:
http://www.restlet.org/downloads/testing

Maven repositories:
http://maven.restlet.org is updated on the 1st and 15th of each month
http://maven.noelios.com is updated daily with new artifacts (access reserved to subscribers)

We have just released Restlet 2.0 M3, replacing Restlet 1.2 M2 as our current “testing” release (following Debian terminology). We have also updated our “stable” branch with a 1.1.5 release.

Looking at the amount of new features that we added so far since Restlet 1.1 (with some more coming), the amount of refactoring and reorganization done on the Restlet API (including the core Resource API), on extension packages and with the growing number of special Restlet editions (Java SE/EE, Google Web Toolkit, Google App Engine and Android), it seemed appropriate to rename the Restlet 1.2 branch into Restlet 2.0.

Here is a summary of the main changes :

• New org.restlet.ext.xml extension including XML related classes previously in the core Restlet API. This ensures that the core Restlet API stays as consistent as possible across all editions. In this case, those features weren’t available in Android.
• Improved the org.restlet.ext.rdf extension with Turtle and N-Triples support in addition to RDF/XML and n3 formats.
• FreeMarker templates can now be loaded via the Context’s client dispatcher and relatively to a base URI.
• Added an org.restlet.ext.xstream extension providing transparent serialization between Java objects and XML or JSON.
• Added an ObjectRepresentation class to the GWT edition and to the org.restlet.ext.gwt server extension. This allows transparent serialization of Java objects leveraging GWT-RPC serialization mechanism, but using your REST APIs.
• Greatly improved the support for the recently added ConverterService.
• Improved the ClientResource with support for annotated interfaces via the creation of dynamic proxies. It now also automatically follows redirections when possible.
• Refactored the services to facilitate the addition of new ones by users in their applications.
• Added AppendableRepresentation for dynamic generation of StringRepresentation instances.

Direct contributors

• Arjohn Kampman
• Bruno Harbulot
• David Bordoley
• David Fogel
• Davide Angelocola
• Didier Girard
• Eric Hough
• Jean-Yves Cronier
• Lars Heuer
• Marcelo Ochoa
• Michael Berman
• Mikhail Spirydonau
• Paul Davis
• Rémi Dewitte
• Ronny Kwon
• Simon Reinhardt
• Tal Liron
• Thom Nelson
• Tim Peierls

Thanks to all others who helped us in various ways!

Additonal resources

Changes log:
http://www.restlet.org/documentation/2.0/changes

Download links:
http://www.restlet.org/downloads/2.0/restlet-2.0m3.zip
http://www.restlet.org/downloads/2.0/restlet-2.0m3.exe

Maven repositories:
http://maven.restlet.org is updated on the 1st and 15th of each month
http://maven.noelios.com is updated daily with new artifacts (access reserved to subscribers)

Objective: To develop a web service that is to be used internally by applications to retrieve and write data to an Oracle database.

I wanted to develop a web service that was designed with the REST framework in mind, SOAP is just too “noisy”, and overly complex.   The web service had to be able connect and interact with an Oracle database, it also had to return any data from the database as XML.  You can view the results directly from a web browser if it’s XML, but it is not really necessary as a web service is mostly a non-human readable resource.

So, I was developing with Java – and had to try an work out what the best tools, APIs would be, bearing in mind the myriad of tools out there on the web.  It took quite a while looking at all the various API’s out there (Spring, Hibernate, iBATIS, EclipseLink, Toplink – the list goes on), but I chose ones that matched the following criteria:
a) if a technology was already in use at work, then that had to be adopted – in order to stop a proliferation of different technologies being used, supported and maintained.

b) easy to use and understand.

c) have decent community support behind them – so if problems arise then at least someone out there may be able to lend a hand.

d) look likely to be well supported in the future without fading into obscurity in the next couple of weeks/months.

Choosing the Right Tools – My Software Stack

• Java IDE – is Eclipse Europa v3.3.2

• Apache Tomcat Application Server v5.5.17

• For the REST web service I chose – Restlet v1.1.4.

A really nice and clean well supported framework.  Some of the tutorials were a bit raw but they have improved of recent and the documentation is getting better all the time.  They are constantly improving the API and stable releases are issued on a resonably regular basis.  They are keen to adopt good standards and it was pleasing to see that WADL is supported in their extended APIs for Restlet.

• For Object Relational Mapping (ORM) with Oracle I chose Toplink  (version 10g Release 3 10.1.3.3.0) and the Workbench software- don’t even think about using raw JDBC API’s – it’s much less work to use Toplink rather than code everything from scratch.

• For XML to Object ORM, I chose Sun’s JAXB v2.0 implemenation – so, so, so much better than Toplinks crummy efforts (so I am saying Toplink is good for database ORM but not for XML ORM) – I spent so many wasted development hours on this piece of crud – so don’t use it unless you want to a miserable life as a developer.  JAXB is nice, its from Sun so it should conform to some form of standard.  The docs are good and it takes seconds to run the JAXB compiler from a command line along with your XSD schema and generate your Java classes.  Pretty good all round.

In my next post I explain how I used the above to create my REST web service.

Our vision is that the Web is becoming ubiquitous and that REST, as the architecture style of the Web, helps you leverage all HTTP features. Restlet, our open source REST framework, is already available on regular computers based on Java SE/EE, in Web browers with our GWT edition and even in the cloud with a new Google AppEngine edition. But, we are still missing the Mobile Web!

With the commodification of smartphones started by the Palm Treo and pushed further by the Apple iPhone, more and more mobile users will have a usable access to the Web from their phone. So far, developers have been stuck with proprietary platforms and where lacking the productivity and portability common in the Java world. But here comes Android!

Android is an open source mobile operating system initiated by Google but now managed by the Open Handset Alliance. This consortium includes prestigious constructors such as HTC, Motorola, Samsung or Sony Ericsson and larger carriers such as Sprint, T-Mobile or Vodaphone. Needless to say that Android has gained a lot of traction recently.

Technically speaking, Android is built on a customized Linux kernel, libraries such as WebKit for the Web browser  and an extensible Application Framework developed in the Java language but running on a special Dalvik virtual machine (see a complete overview here). All the built-in applications are written in Java and can accessed or customized via an Android API.

Preparing for an imminent launch of the Android-powered HTC Magic phone in France (also known as the “G2″), the mobile operator SFR, one of the third largest in France, has announced a contest for the best Android application. We thought it was a perfect opportunity to port the Restlet framework to another exciting environment and applied as a “Restlet+FOAF” project.

With some adjustments (see technical details), we were able to port Restlet on Android, with both the client-side and the server-side HTTP connectors! To show the potential of Restlet on Android, we decided to go further and develop a simple extension to the Contacts applications that would retrieve the FOAF (Friend-Of-A-Friend) profile of your contacts, show their friends and let you add some as new local contacts. The source code of this sample application is available and documented in the Restlet User Guide.

With the help of Manning’s “Unlocking Android” book, we also discovered Android’s Intent/Service design pattern, which is quite similar to Eclipse’s plug-ins. This is a powerful way to extend Android applications and share common features. In our case, we developed a FOAF Service that can be reused by other Android applications, without tight coupling on our code.

Finally, with the growing number of Restlet editions, we felt the need to put in place an automatic porting process to keep the code changes synchronized. This effort is underway but you can already read its specifications in our developers wiki. All those new features are available in recent Restlet snapshots. Enjoy!

Update: On May 13, the jury of the SFR-Android contest selected our Restlet project for a special open source prize! Thierry is now the happy owner of a HTC Magic phone

We are living exciting times! This week, Google has released an early version of their widely expected support for Java in Google App Engine (GAE).

GAE is a computing platform that can host your Web applications and offer them  massive and flexible scalability. Free accounts are available and you can pay for extra resources (CPU time, bandwidth, storage and mails sent).

Of course, REST is the perfect choice to build your Web applications that will live in the Google cloud. But, GAE achievements come with constraints because you share computing resources with others. So GAE makes you live in a sandbox with a limited set of Java APIs.

The great news is that Restlet has just been adapted to fully work with GAE! This port provides in a single “org.restlet.gar.jar” file:

• Full Restlet API
• HTTP(S) server via the built-in Servlet adapter
• HTTP(S) client via the built-in adapter to java.net.HTTPUrlConnection
• SMTP client via the built-in adapter for JavaMail
• Server-side GWT support via the built-in GwtShellServletWrapper class.

In addition, support for GWT is available in both GAE and Restlet (see this post on our port of Restlet on GWT). The usage instructions are available in our online User Guide.

Google France provided us the early access to GAE after their launch event in Paris last Thursday, in collaboration with Didier Girard, Technical Director at SFEIR and author of the OnGWT web site.

Thanks to all of them and to Guillaume Laforge (who ported Groovy to GAE) for their advices and help making this port a reality so quickly and for sharing their passion for GAE!

After a long investment in WS-*/SOAP initiatives, Microsoft has recognized the value of REST. But they didn’t adopt REST only on the surface, they have put in place a comprehensive offer and are actively working to demonstrate and facilitate the interoperability with other platforms such as Java.

Silverlight

Facing a strong competition in the Rich Internet Application area, from Google with GWT, from Adobe with Flex/AIR/Flash and more recently from Sun with JavaFX/Applets, Microsoft has finally reacted with the introduction of their Silverlight 2 technology.

Silverlight requires a browser plug-in (ActiveX available for IE, Firefox and Safari) and provides you with a subset of the .NET Framework. Microsoft supports Windows and Mac while Novell has a Linux version called Moonlight. For the user interface it relies on a declarative language called XAML, not too different from Flex MXML or JavaFX scripts.

Regarding communication, it relies on WCF and offers direct support for HTTP/REST, RSS and Atom, POX/JSON and XML/LINQ. A description of the full architecture is available here.

Now, if you follow this blog, you are probably wondering how Silverlight interoperates with Java on the server-side. Even if its support for HTTP has a few limitations (partially due to its nature of browser plugin), Silverlight allows you to communicate easily with a REST back-end.

To demonstrates this, Microsoft has leveraged our Restlet framework and illustrated this interoperability with several detailled posts in their Silverlight plus Java blog written by Stève Sfartz from Microsoft. Other examples are available on Blog in the Cloud and Cloud it up.

eclipse4SL

If you are a traditional Microsoft developer, you would naturally turn to Visual Studio to develop your Silverlight applications, but what if you are a Java developer?

Well, Microsoft has done an unusual move by supporting the development of a Silverlight IDE for Eclipse! It’s called eclipse4SL and is co-developped with Soyatec, a French software editor specialized in Eclipse products development.

REST interoperability is also covered in eclipse4SL’s user documentation, illustrated by the usage of Restlet on the server-side. See this page for Restlet guidance. This is currently based on Restlet 1.0 and a Tomcat deployment, but work is underway to upgrade to Restlet 1.1.

The eclipse4SL project has even been submitted to the Eclipse foundation. See this post from the executive director of the Eclipse foundation.

TechDays

After meeting with Stève Sfartz, who very enthusiastically introduced us to Microsoft projects for REST, cloud computing and RIA, we worked on a join presentation for the Microsoft TechDays in Paris.

The goal was to present interoperability scenarios around REST. Thierry Boileau did the presentation for Noelios Technologies. A detailled summary (in French) has been posted by Stève Sfartz on his blog.

This presentation gave us the opportunity to show case our recent support for the Shared Key HTTP authentication scheme. This protocol is similar to the one defined for Amazon S3 and allows you to access to Microsoft Azure Data Services from a Restlet Java client.

This new feature is available in recent snapshots of our future Restlet 1.2 release!

Update 1:  article from BetaNews covering Eclipse4SL and mentioning Restlet

Update 2: Stève Sfartz has posted a complete article on MSDN detailling the example showcased at the TechDays (in French), including downloadable source code.

Last year, MuleSource released RESTpack, an extension for their leading open source Mule ESB product. This pack has just been updated and now includes support for the latest Restlet 1.1 version.

The Restlet transport provides  a deep integration, both on the server and the client side, between Restlet and Mule ESB. For more information, you can read the dedicated documentation page.

We had the opportunity to talk with Dan Diephouse, the software architect and REST expert who is leading this effort.

We asked him what are the benefits that Mule RESTpack and Restlet transport bring to existing Restlet users and, more generally, how do ESB and REST fit together conceptually?

The big benefit is that you can start to build integration applications that not only utilize RESTful HTTP services, but JMS, email, BPM, etc. In addition to just hosting Restlet services in a container like fashion, you can do things like:

• Route messages to different services and transports (e.g. using URI templates to route to different JMS queues)
• Kick of other process flows when an HTTP Response is sent
• Utilize all the built in capabilities for transformations, routing, and message filtering that Mule has to offer.

If you are looking for an ESB solution with strong REST support, this is a great opportunity to leverage two mature open source technologies. We already had a report of a successful usage of Restlet with Mule ESB in a large project in France!

Concernant l’application “Video On Demand” que nous avons présentée précédemment, nous avons évoqué l’utilisation de la technologie Silverlight Streaming. Ce service, développé par Microsoft, permet aux développeurs de diffuser leurs fichiers vidéos ou leurs applications Silverlight afin de les rendre accessibles à tous. Dans cet article, je vais tâcher de présenter son fonctionnement pour les fichiers vidéo.

Silverlight Streaming nécessite un compte LiveID, et permet un stockage gratuit de streaming de 10 Go maximum. Il faut savoir qu’en cas de dépassement de stockage, il faudra passer par une option payante.

Procédure

Pour uploader un fichier vidéo, la première étape consiste d’abord à récupérer un identifiant (numéro de compte SLS) et une clé. Pour cela, il suffit de s’inscrire sur le site suivant : http://silverlight.live.com.

Une fois l’identifiant et la clé récupérés, il est possible d’uploader une vidéo en cliquant sur l’option “Manage Video”. A noter que l’option “Manage Applications” fait de même pour les applications Silverlight.

L’upload d’un fichier (au format “.wmv”, “.avi”, “.mpeg”, “.mov”…) nécessite l’emplacement du fichier, ainsi qu’un titre. Une fois que le fichier est uploadé, une URL statique est fournie pour accéder au fichier vidéo.

Procédure avec communication REST

Je vais aborder ici la procédure d’authentification sur Silverlight Streaming par requête REST. Notons qu’il est indispensable pour cela d’avoir les identifiants (Account ID et Account Key).

Le code suivant (en C#) présente la procédure d’authentification (par souci de simplicité, j’ai choisi le mot “foo” en guise d’Account ID) :

Concernant la gestion des vidéos avec REST, nous allons recourir aux requêtes HTTP suivantes :

• PUT, pour l’ajout d’une vidéo
• DELETE, pour la suppression d’une vidéo
• COPY, pour la duplication d’une vidéo

Pour la procédure d’identification (vue ci-dessus) et l’ajout de fichiers sur la plateforme Silverlight Streaming, nous allons nous appuyer sur les librairies du framework Restlet (www.restlet.org). Ses librairies sont directement téléchargeables sur le site, et devront ensuite être implémentées parmi les librairies de l’application Java (Back Office).

Uploader un fichier avec PUT.

A partir de là, nous allons voir comment uploader un fichier sur Silverlight Streaming.

La procédure présentée au sommet de cet article donnait les indications suivantes : il s’agit avant tout de s’identifier sur la plateforme, de donner un nom à sa vidéo (qui correspondera au répertoire qui contiendra la vidéo) et de valider l’upload. Il faut également savoir qu’une fois présente sur le site, la vidéo sera appelée “video.wmv”.

Pour effectuer l’upload de fichier de façon logicielle, nous allons effectuer une requête de type PUT, basée sur les librairies de Restlet, au sein d’une application Java.

Dans un premier temps, il convient de recenser et d’initialiser les données utiles :

Ensuite, après avoir initialisé les données, il s’agit de concevoir le répertoire (ou FileSet) qui contiendra la vidéo sur la plateforme. On utilise pour cela la méthode MKCOL. Le code se présente de la façon suivante :

Enfin, il ne reste plus qu’à envoyer la requête PUT pour l’upload de la vidéo :

De cette façon, il est possible d’uploader facilement une vidéo sur l’interface Silverlight Streaming. Tout ce code sera implémenté dans notre application Back Office et exécuté lorsque l’utilisateur souhaitera uploader une vidéo sur la plateforme Silverlight Streaming.

Par la suite, il va s’agir d’effectuer une requête HTTP avec les méthodes DELETE et COPY.

On the French IT market, Octo Technology is a top consulting company, specialized in software architecture. Since its creation in 1998, it has regularly shaped the technology landscape through their famous white papers.

In 2007, they showed a clear understanding of REST by publishing “Web Services: Architectural Choices” (in French) by Philippe Mougin. The latest in the series is  a “Java Productivity Primer” (in English) detailing “Twelve guidelines to boost your productivity with a software factory”.

In their first guideline, “Adopt a productive Java platform that’s tailored for your project(s)”, they warn against bloated commercial platforms and propose an example of a state-of-the-art, low-cost Java platform which includes Restlet to develop their Web services.

They say they really like Restlet because the “framework is built for the REST architectural style, which is HTTP’s native architectural style. It lets you leverage the Web’s intrinsic qualities (scalability, loose coupling, etc.) much better than RPC- and/or SOAP-oriented frameworks”.

PS: Thanks to Charles Gay, from jGuard, for first pointing me to this document.

Update 1: See related blog post from Philippe Mougin

On the 4th of November, I presented a session on REST, Restlet and our port to GWT at the local JUG (Paris Java User Group). More than 200 juggers attended, with a first part on GWT presented by Didier Girard, from onGWT.

Eric Le Merdy, from Valtech, very creatively illustrated the presentation. Here is our first Restlet cartoon!

Thanks to Antonio Goncalves, David Dewalle and Zouheir Cad, the co-founders of Paris JUG for organizing this event. Keep up the fun, the passion and the professionalism!

Here are additional links about the event (all in French):

• Interview by Thomas Queste
• Summary by Anthony Dahan
• Summary by Fabien Duminy
• Summary by Nicolas Martignole
• Paris JUG session page

Building an API on the REST architectural style? Building it in Java?

This past week, on a project doing just that, I ran into Restlet. I’d never heard of a REST framework for Java before, but it’s been featured InfoQ, TSS, ONJava, and others over the past three years. (Damn, I need to pay more attention.)

And it kicks ass.

Here’s a quick run-down:

Restlet is an API for developing REST-based services in the same way that Servlet is an API for developing Web-based services. Your application never deals with the Servlet API, HTTP-specific attributes, cookies, sessions, JSPs, or any of that baggage.

Instead, you think and code in terms of REST: Routing, Resources, Representations.

It has an intuitive URL routing system that parses out resource identifiers and other data (that is, a URL template of /user/{user_id} would give you a ‘user_id’ attribute for any URL matching that pattern, which is fed into your User resource).

Resources are easily able to define which of the verbs (GET, POST, PUT, DELETE) they respond to, with default behavior defined for verbs that are unsupported.

There are plug-ins available for SSL and OAuth, an emerging best practice for authenticating third party access to user accounts.

The documentation is a bit lacking. However, there is an excellent IBM developerWorks tutorial on Restlet (registration required) that lays out pretty much everything you need, with a (nearly-)complete example for study.

Lucas Jellema from AMIS has a very interesting post about his experience with REST and JDeveloper 11g. He walks through the RestLet tutorial using the recently released JDeveloper 11g.

Masterbating – Masterbating
You Porn – You Porn
Cfnm – Cfnm
Xxnx Free Site – Xxnx Free Site
Free Porn Trailers – Free Porn Trailers
Grannysex – Grannysex
Freepornvideos – Freepornvideos
Xtube Videos – Xtube Videos
Sexmovie – Sexmovie
Sexyclips – Sexyclips
Momsex – Momsex
Sexymovies – Sexymovies
Girlsgonewild – Girlsgonewild
Porn Vids – Porn Vids
Milf Like It Big – Milf Like It Big
Movie – Movie
Gay Tube – Gay Tube
Young Little Girl Virgins – Young Little Girl Virgins
Sites – Sites
Maxporn – Maxporn
Freexxx – Freexxx
Blowjobs – Blowjobs
Fuck Videos – Fuck Videos
Xxnx.com – Xxnx.com
Sexclips – Sexclips
Round Mound Of Ass – Round Mound Of Ass
Free Porn Videos – Free Porn Videos
Youtube Video Clips – Youtube Video Clips
Freesexclips – Freesexclips
Twogirlsonecup – Twogirlsonecup
Videos Eroticos – Videos Eroticos
Adult Movies – Adult Movies
Sybian – Sybian
You Tube Street Fights – You Tube Street Fights
Freesexmovies – Freesexmovies
Amature Sex – Amature Sex
Video De Noelia – Video De Noelia
Www.ampland.com – Www.ampland.com
Twistys Video – Twistys Video
Granny Porn – Granny Porn
Peter North Facials – Peter North Facials
Latinas Calientes – Latinas Calientes
Upskirt – Upskirt
Red Tube – Red Tube
Pornomovies – Pornomovies
Pornmovies – Pornmovies
Www.free Porn – Www.free Porn
Free Xxx – Free Xxx
Atk Natural – Atk Natural
Amature Clips – Amature Clips

(German announcement) JSR 311 “JAX-RS Java-API für RESTful Web Services” is approved. Implementations are Jersey, Restlet-Framework, JBoss RESTEasy and Apache CXF.

CreateOrDie has found a very nice cup for photographs.

I’m assuming that if you’re here you already know the basics of REpresentational State Transfer.  I’m also going to assume that you’ve looked at all the goodies at the Restlet community site.  Further, I’m thinking that you want a quick start guide to show you how to implement it.  The following tutorial shows how I “found a home” with Restlet, what worked for me, and hopefully something that will work for you, too.

The Restlet API is a Java framework for the REST architectural style. The Noelios Restlet Engine (NRE) is available as the reference implementation, as well as several extensions to the API and to NRE.

Why is it cool?

To Quote Jérôme Louvel, founder and lead developer of Restlet:

It’s cool because it does all that.  I love that fact that you can send a request to a Restlet engine, and you can return back this amazing variety of Representations based upon it.  The first exposure to Restlet for me came when I put forth a design for a beacon tracking system that could be triggered via HTML pages, Server calls, log-file digestion and anything else I could think of.  The lead developer turned me on to Restlet.

I later found ways to hook it up to a JBoss-Rules system, a Low-Latency Data Store for delivering customer demographic information, and a Affiliate Network lead quality validation system.  Each application had completely different requirements except that they needed to be a service.  I decided on REST instead of  SOAP, and the “rest” is in the implementations.  It subscribes to my basic requirements for an application:

Once you work with Restlet a bit, get an application running, manipulate what you’ve built into other things, and get real expertise around it, you’ll find, like I have, that it just works. 

The Jars you need for this application.

To run this application, you’ll need the following jar files:

• com.noelios.restlet.ext.servlet_2.5.jar
• com.noelios.restlet.jar
• org.restlet.jar
• xalan-2.7.0.jar
• xrcesImpl.jar

Running Restlet from Tomcat — Configure the web.xml file.

You’ll want to run Restlet from a WAR file in most production cases, but you really don’t have to.  I like to use it because it creates homogeneous environments for my ITOPs people to work with; nice, similar stacks for maintenance purposes, so we’ll do it this way here.  This is the web.xml file used in the web application that we’re deploying our service through:

<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
                 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>first steps servlet</display-name>
    <!-- Application class name -->
    <context-param>
        <param-name>org.restlet.application</param-name>
        <param-value>
            com.dg.demo.restlet.application.DemoApplication
        </param-value>
    </context-param>

    <!-- Restlet adapter -->
    <servlet>
        <servlet-name>ServerServlet</servlet-name>
        <servlet-class>
            com.noelios.restlet.ext.servlet.ServerServlet
        </servlet-class>
    </servlet>

    <!-- Catch all requests -->
    <servlet-mapping>
        <servlet-name>ServerServlet</servlet-name>
        <url-pattern>/demo/*</url-pattern>
    </servlet-mapping>
</web-app>

Note that com.dg.demo.restlet.application.DemoApplication will be the Application class file that you will write.  ServerServlet comes with the libraries.  Note that the “servlet-mapping” that I’m using here is “/demo/*”.  This means that all URLs directed to the Restlet must have “/demo/” as their root, (i.e. http://localhost:8080/demo/…).

The Application Class

The Application Class is the “manager” for the Restlet Application. This class will find the proper resource with respect to the URL that is presented to it.  In the case of this application, we’ll be mapping incoming URLs to:

• a “System up” Resource that shows that the Restlet is actually running and mapping correctly.
• a “Mapping” Resource that will allow for a list of cities and states to be shown based upon given inputs.
• an “XML” Resource that shows mappings of Cities and States as an XML Representation.

Here is the application Class:

package com.dg.demo.restlet.application;

import com.dg.demo.restlet.resource.CityXMLResource;
import com.dg.demo.restlet.resource.MapResource;
import com.dg.demo.restlet.resource.SystemResource;
import org.restlet.Application;
import org.restlet.Context;
import org.restlet.Restlet;
import org.restlet.Router;
import org.restlet.data.MediaType;
import org.restlet.data.Request;
import org.restlet.data.Response;
import org.restlet.resource.StringRepresentation;

/**
 * The Application Root Class.  Maps all of the resources.
 */
public class DemoApplication extends Application {

    /**
     * Creates a new DemoApplication object.
     */
    public DemoApplication() {
        //empty
    }

    /**
     * Public Constructor to create an instance of DemoApplication.
     *
     * @param parentContext - the org.restlet.Context instance
     */
    public DemoApplication(Context parentContext) {
        super(parentContext);
    }

    /**
     * The Restlet instance that will call the correct resource
     * depending up on URL mapped to it.
     *
     * @return -- The resource Restlet mapped to the URL.
     */
    @Override
    public Restlet createRoot() {
        Router router = new Router(getContext());

        router.attach("/sys", SystemResource.class);
        router.attach("/{key}/maps", MapResource.class);
        router.attach("/xml", CityXMLResource.class);

        Restlet mainpage = new Restlet() {
            @Override
            public void handle(Request request, Response response) {
                StringBuilder stringBuilder = new StringBuilder();

                stringBuilder.append("<html>");
                stringBuilder.append("<head><title>Sample Application " +
                        "Servlet Page</title></head>");
                stringBuilder.append("<body bgcolor=white>");
                stringBuilder.append("<table border=\"0\">");
                stringBuilder.append("<tr>");
                stringBuilder.append("<td>");
                stringBuilder.append("<h3>available REST calls</h3>");
                stringBuilder.append("<ol><li>/sys --> returns system " +
                        "up and date string</li>");
                stringBuilder.append("<li>/all/maps --> returns a list" +
                        " of all the cities and states</li>");
                stringBuilder.append("<li>/{key}/maps --> returns a list " +
                        "of cities for a particular state (CA,IL,TX)<br/>");
                stringBuilder.append("using one of the keys from the \"all\" " +
                        "call<br/> pasted in place as the {key}.</li>");
                stringBuilder.append("<li>/xml --> POST or GET URL or web " +
                        "form elements as XML to this</li>");
                stringBuilder.append("</ol>");
                stringBuilder.append("</td>");
                stringBuilder.append("</tr>");
                stringBuilder.append("</table>");
                stringBuilder.append("</body>");
                stringBuilder.append("</html>");

                response.setEntity(new StringRepresentation(
                        stringBuilder.toString(),
                        MediaType.TEXT_HTML));
            }
        };
        router.attach("", mainpage);
        return router;
    }
}

With this Application I tried to show a “default”, “servlet-like” page returned by a Restlet created as an anonymous inner class — you can do that with all your URL requests if you like, but creating different Resource implementations is much easier to manage and write tests for. It is also very important to set the Context of the application in the Constructor (calling the superclass).  I forgot to do this and lost about an hour before I finally found it.

Once the Resources are mapped, You’re ready to rock and roll.  We’ll create a simple Model, and then get into the Resource Classes.

 A Simple Model to Work From:

We need something to do with our application, so I decided to create a simple “persistence layer” that has a map of cities and states.  I could have done more and it could have been more complex, but I just wanted something that you can bang against and get an idea about how it all works.  I created an implementation class that contains a map of cities and states extending java.util.AbstractMap.  I then exposed various structures of this mapping through an interface class that the application will use to return information by implementing an Interface against it, obfuscating anything that I didn’t want to expose:

package com.dg.demo.model;

import java.util.List;
import java.util.Map;
import java.util.Set;

/**
 * A simple interface to return a map of
 * values for the demonstration.
 */
public interface MappedPersistence {

    // returns a formatted string of the cities
    // mapped to a particular state.
    String getCommonValues(String state);

    // returns a set of cities, which are
    // the map keys.
    Set<String> keys();

    // returns a map of cities <K> with states<V>
    // as the value.
    Map<String, String> proxy();

    // returns a set of states available.
    Set<String> valueSet();

    //returns a List of cities.
    List<String> mappedKeys(String s);

}

The implementation of the Interface above is MappedCityPersistence:

package com.dg.demo.model.impl;

import com.dg.demo.model.MappedPersistence;

import java.util.AbstractMap;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.HashSet;
import java.util.List;
import java.util.Map;
import java.util.Set;

/**
 * Implementation of MappedPersistence Interface.
 * Extends Abstract Map, but obfuscates the
 * mappings via the MappedPersistence Interface.
 */
public class MappedCityPersistence
        extends AbstractMap<String, String>
        implements MappedPersistence {

    private Map<String, String> proxyMap;

    public MappedCityPersistence() {
        proxyMap = new HashMap<String, String>();
        loadProxy();
    }
    // this class must be implemented...
    public Set<Entry<String, String>> entrySet() {
        return proxyMap.entrySet();
    }
    //the values for persistence.
    private void loadProxy() {
        proxyMap.put("Los Angeles", "CA");
        proxyMap.put("Santa Barbara", "CA");
        proxyMap.put("San Francisco", "CA");
        proxyMap.put("San Diego", "CA");
        proxyMap.put("Dallas", "TX");
        proxyMap.put("Houston", "TX");
        proxyMap.put("Austin", "TX");
        proxyMap.put("El Paso", "TX");
        proxyMap.put("Chicago", "IL");
        proxyMap.put("Joliet", "IL");
        proxyMap.put("Naperville", "IL");
        proxyMap.put("Oak Park", "IL");
    }

    @Override
    public String toString() {
        StringBuilder builder =
                new StringBuilder("City/State values:\n");
        for (String s : proxyMap.keySet()) {
            builder.append(s).append(" => ")
                    .append(proxyMap.get(s)).append("\n");
        }
        return builder.toString();
    }

    public String getCommonValues(String value) {
        StringBuilder builder =
                new StringBuilder("Cities located in "
                        + value + ":\n");
        for (String s : proxyMap.keySet()) {
            if (proxyMap.get(s).equals(value)) {
                builder.append(s).append("\n");
            }
        }
        return builder.toString();
    }

    public Set<String> keys() {
        return proxyMap.keySet();
    }

    public Map<String, String> proxy() {
        return this.proxyMap;
    }

    public Set<String> valueSet() {
        Set<String> quickAndDirtySet = new HashSet<String>();
        for (String s : proxyMap.values()) {
            quickAndDirtySet.add(s);
        }
        return quickAndDirtySet;
    }

    public List<String> mappedKeys(String s) {
        List<String> quickAndDirtyList = new ArrayList<String>();
        for (String key : proxyMap.keySet()) {
            if (proxyMap.get(key).equals(s)) {
                quickAndDirtyList.add(key);
            }
        }
        return quickAndDirtyList;
    }

    public static void main(String[] args) {
        MappedCityPersistence p = new MappedCityPersistence();
        System.out.println(p.getCommonValues("TX"));
    }
}

Note the extra methods that are now obfuscated by the Mapped Persistence Interface.

Building the Resources that are Mapped to URLs

The first, and easiest to implement of the Resources is the SystemResource that I created to show whether or not I got the mappings right and if the system is running or not.  It returns a basic “text” string that says the system is running and what time the JVM says it is:

SystemResource.java

package com.dg.demo.restlet.resource;
import org.restlet.Context;
import org.restlet.data.MediaType;
import org.restlet.data.Request;
import org.restlet.data.Response;
import org.restlet.resource.Representation;
import org.restlet.resource.Resource;
import org.restlet.resource.StringRepresentation;
import org.restlet.resource.Variant;

import java.util.Calendar;

/**
 * Simple String retrieval to determine whether the system is up
 * and running.  it adds a timestamp for varification that the
 * message isn't cached and allows for identification of
 * the time zone.
 */
public class SystemResource extends Resource {

    /**
     * Creates a new MapResource object.
     *
     * @param context  -- Restlet Context Instance.
     * @param request  -- Restlet Request Instance.
     * @param response -- Restlet Response Instance.
     */
    public SystemResource(Context context,
                          Request request,
                          Response response) {
        super(context, request, response);
        // Here we add the representation variants exposed
        getVariants().add(new Variant(MediaType.TEXT_PLAIN));
    }

    /**
     * Do not allow post to this resource.
     *
     * @return -- always false for this resource.
     */
    public boolean allowPost() {
        return false;
    }

    /**
     * default method for "get" from Client Application.
     *  Returns wheter or not the system is available,
     * and the current time.
     *
     * @param variant -- Available variants.
     *
     * @return -- A String representing whether or
     *            not the demo system is available, etc.
     */
    public Representation represent(Variant variant) {
        //LQSCache.getInstance();
        String message = "hello!, the Demo " +
                "Service is available." +
                " Time of request is:"
                + Calendar.getInstance()
                .getTime().toString();

        return new StringRepresentation(message,
                MediaType.TEXT_PLAIN);
    }
}

The mapping resource shows all of the cities and states mapped, and also shows the cities mapped to a particular state when that state is input within the url (i.e. http://localhost:8080/demo/all/maps — to show all cities and their city mappings, ./demo/TX/maps to get all cities mapped to Texas):

MapResource.java

package com.dg.demo.restlet.resource;

import com.dg.demo.model.MappedPersistence;
import com.dg.demo.model.impl.MappedCityPersistence;
import org.restlet.Context;
import org.restlet.data.MediaType;
import org.restlet.data.Request;
import org.restlet.data.Response;
import org.restlet.resource.Representation;
import org.restlet.resource.Resource;
import org.restlet.resource.StringRepresentation;
import org.restlet.resource.Variant;

/**
 * Utility Resource to view the various strings
 * mapped in the Persistence.
 */
public class MapResource extends Resource {

    /**
     * The map requested by the client application
     */
    String mapName;

    /**
     * Creates a new MapResource object.
     *
     * @param context  -- The restlet Context instance.
     * @param request  -- The restlet REquest instance.
     * @param response -- The restlet Response instance.
     */
    public MapResource(Context context,
                       Request request,
                       Response response) {
        super(context, request, response);
        this.mapName = (String) request.getAttributes().get("key");

        // Here we add the representation variants exposed
        getVariants().add(new Variant(MediaType.TEXT_PLAIN));
    }

    /**
     * Do not allow post to this resource.
     *
     * @return -- always false for this resource.
     */
    @Override
    public boolean allowPost() {
        return false;
    }

    /**
     * Collect the values for a particular mapping and return
     * a formatted string.  By inputting "all" into the request,
     * it returns a list of the mappings available. When this
     * service returns, substituting "all" for one of the
     * returned values will return the values for that mapping key
     *
     * @param variant -- The variant describing the return mappings.
     *
     * @return -- a formatted string with the map values as a list.
     */
    @Override
    public Representation represent(Variant variant) {
        //UDCAPICache.getInstance();
        MappedPersistence persistence = new MappedCityPersistence();

        //LQSCache.getInstance();
        String message;
        //String mapName = (String) getRequest().getAttributes().get("key");

        if (mapName.equals("all")) {
            message = persistence.toString();
        } else if (persistence.valueSet().contains(mapName)) {
            message = persistence.getCommonValues(mapName);
        } else {
            message = "NO VALUES FOUND FOR: " + mapName;
        }
        return new StringRepresentation(message, MediaType.TEXT_PLAIN);
    }
}

The XML resource returns a list of cities that are mapped to each state as an xml representation.  It allows a post or get, via the “acceptRepresentation()” (POST) and “represent()” (GET) methods.  I’ve put both of these in bold, along with other things that seemed important to me.  Each calls the same private method that creates the XML representation:

package com.dg.demo.restlet.resource;

import com.dg.demo.model.MappedPersistence;
import com.dg.demo.model.impl.MappedCityPersistence;
import org.restlet.Context;
import org.restlet.data.MediaType;
import org.restlet.data.Request;
import org.restlet.data.Response;
import org.restlet.resource.DomRepresentation;
import org.restlet.resource.Representation;
import org.restlet.resource.Resource;
import org.restlet.resource.Variant;
import org.w3c.dom.Document;
import org.w3c.dom.Element;

import java.io.IOException;

public class CityXMLResource extends Resource {

    /**
     * @param context  -- Restlet Context Instance.
     * @param request  -- Restlet Request Instance.
     * @param response -- Restlet Response Instance.
     */
    public CityXMLResource(Context context,
                           Request request,
                           Response response) {
        super(context, request, response);
        getVariants().add(
                new Variant(MediaType.TEXT_PLAIN));
        getVariants().add(
                new Variant(MediaType.APPLICATION_XML));
        //handle(request,response);
    }

    /**
     * Flag to allow POST via web form.
     *
     * @return true if POST is allowed, false if not.
     */
    public boolean allowPost() {
        return true;
    }

    /**
     * Represent the requested object in the requested format.
     *
     * @param variant -- the requested variant or default.
     *
     * @return an XML representation or an error string.
     */
    public Representation represent(Variant variant) {
        DomRepresentation representation = null;
        try {
            representation = getFraudXMLRepresentation();
        } catch (IOException e) {
            e.printStackTrace();
            getResponse().setEntity("ERROR " + e.getMessage(),
                    MediaType.TEXT_PLAIN);
        }
        return representation;
    }

    /**
     * Handle a POST Http request.
     *
     * @param entity -- the declared entity
     */
    public void acceptRepresentation(Representation entity) {
        System.out.println("USING POST");

        try {
            if (entity.getMediaType()
                    .equals(MediaType.APPLICATION_WWW_FORM, true)) {
                DomRepresentation representation =
                        getFraudXMLRepresentation();
                // Returns the XML representation of this document.
                getResponse().setEntity(representation);
            }
        } catch (IOException e) {
            e.printStackTrace();
            getResponse().setEntity("ERROR " + e.getMessage(),
                    MediaType.TEXT_PLAIN);
        }
    }

    /**
     * Creates the XML that will be returned to the requesting client.
     *
     * @return - The formatted XML Document
     */
    private DomRepresentation getFraudXMLRepresentation() throws IOException {

        DomRepresentation representation =
                new DomRepresentation(MediaType.TEXT_XML);

        MappedPersistence persistence =
                new MappedCityPersistence();

        // Generate a DOM document representing the list of frauds generated..
        Document d = representation.getDocument();

        //The Root Element, with it's corresponding attribute for the total score.
        Element root = d.createElement("citystatemappings");
        root.setAttribute("numberofstates",
                String.valueOf(persistence.valueSet().size()));
        d.appendChild(root);

        //If there are no frauds, then we skip this and just return the root.
        for (String state : persistence.valueSet()) {
            Element stateElement = d.createElement("state");
            stateElement.setAttribute("name", state);

            for (String city : persistence.mappedKeys(state)) {
                Element cityElement = d.createElement("city");
                cityElement.appendChild(d.createTextNode(city));

                stateElement.appendChild(cityElement);
            }
            //tie the frauds to the root.
            root.appendChild(stateElement);
        }
        d.normalizeDocument();
        return representation;
    }
}

Compile these classes into your web application with your lib jars, and make sure the “web.xml” file is configured as shown earlier in this text.  Create a .war file or run from your IDE.  You should be able to use the URLS that have been configured into the DemoApplication class file to view data in different formats.  If your application is configured to run on http://localhost:8080…

• http://localhost:8080/demo — returns the Representation defined in the “anonymous inner class” of the DemoApplication.

• http://localhost:8080/demo/sys   — returns the “system up” resource and it’s information, something like:

hello!, the Demo Service is available. Time of request is:Tue Sep 23 17:53:42 PDT 2008

• http://localhost:8080/demo/all/maps — returns a list of all the states mapped into the persistence layer:

City/State values:
Austin => TX
Chicago => IL
El Paso => TX
Los Angeles => CA
Naperville => IL
Houston => TX
San Diego => CA
Santa Barbara => CA
Dallas => TX
Oak Park => IL
Joliet => IL
San Francisco => CA

• http://localhost:8080/TX/maps — returns a list of cities mapped to TX:

Cities located in TX:
Austin
El Paso
Houston
Dallas

http://localhost:8080/demo/xml — Finally, you want to get an xml representation of all this (view source):

<?xml version="1.0" encoding="UTF-8"?>
<citystatemappings numberofstates="3">
    <state name="CA">
        <city>Los Angeles</city>
        <city>San Diego</city>
        <city>Santa Barbara</city>
        <city>San Francisco</city>
    </state>
    <state name="TX">
        <city>Austin</city>
        <city>El Paso</city>
        <city>Houston</city>
        <city>Dallas</city>
    </state>
    <state name="IL">
        <city>Chicago</city>
        <city>Naperville</city>
        <city>Oak Park</city>
        <city>Joliet</city>
    </state>
</citystatemappings>

From here you’re on your own. You can see how to further create things that you might need for your projects; there are other representations that you can work with, including some very interesting uses of the java.util.nio libraries that allow for blazing fast file retrieval and delivery. You can even send Java Objects around. It’s worth looking through the Restlet API Docs at this point.

Free Anime Sex Clips – Free Anime Sex Clips
Free Bukkake Trailers – Free Bukkake Trailers
Free Arab Porn Clips – Free Arab Porn Clips
Free Anime Porn Videos – Free Anime Porn Videos
Free Asian Porn Clips – Free Asian Porn Clips
Free Cartoon Porn Clips – Free Cartoon Porn Clips
Free Asian Porn Movies – Free Asian Porn Movies
Free Asian Porn Trailers – Free Asian Porn Trailers
Free Asian Porn Videos – Free Asian Porn Videos
Free Anime Sex Videos – Free Anime Sex Videos
Free Cartoon Porn Videos – Free Cartoon Porn Videos
Free Celeb Fuck Vids – Free Celeb Fuck Vids
Free Anime Porn Movies – Free Anime Porn Movies
Free Anime Porn Clips – Free Anime Porn Clips
Free Anime Hentai Movie Clips – Free Anime Hentai Movie Clips
Free Anime Hentai Movie Clips – Free Anime Hentai Movie Clips
Free Anime Hentai Mivie Clips – Free Anime Hentai Mivie Clips
Free Animal Sex Vids – Free Animal Sex Vids
Free Animal Sex Videos – Free Animal Sex Videos
Free Animal Sex Video Clips – Free Animal Sex Video Clips
Free Animal Sex Movies – Free Animal Sex Movies
Free Animal Sex Clips – Free Animal Sex Clips
Free Animal Porn Vids – Free Animal Porn Vids
Free Animal Porn Videos – Free Animal Porn Videos
Free Animal Porn Movies – Free Animal Porn Movies
Free Animal Porn Clips – Free Animal Porn Clips
Free Animal Clip Art – Free Animal Clip Art
Free Anal Toy Vids – Free Anal Toy Vids
Free Anal Sex Vids – Free Anal Sex Vids
Free Anal Sex Video Trailers – Free Anal Sex Video Trailers
Free Amature Vids – Free Amature Vids
Free Amature Videos – Free Amature Videos
Free Amature Sex Videos – Free Amature Sex Videos
Free Amature Movies – Free Amature Movies
Free Amatuer Videos – Free Amatuer Videos
Free Amateur Vids – Free Amateur Vids
Free Amateur Video Trailers Of Men Jacking Off And – Free Amateur Video Trailers Of Men Jacking Off And
Free Amateur Sex Clips – Free Amateur Sex Clips
Free Amateur Porn Videos – Free Amateur Porn Videos
Free Amateur Porn Clips – Free Amateur Porn Clips
Free Adult Videos – Free Adult Videos
Free Adult Video Trailers – Free Adult Video Trailers
Free Adult Video Sharing – Free Adult Video Sharing
Free Adult Video – Free Adult Video
Free Adult Trailer Movies Free – Free Adult Trailer Movies Free
Free Adult Trailer – Free Adult Trailer

The first round unfrequent moments apropos of our standpoint are new brazenfaced.

Tide humans apprehend pondered the heavens, told stories as regards our plan, and contemplated our arrive inward the created nature, ages ago the hegemonic moments in regard to impressibility, the hard information in relation with our beginnings has inimitable begun in reserve into recognition friendly relations the peroration scarcely any decades.

Broach number one fork other self second route. Infra 13.7 large number years, yours truly is flush at this potency synchronized all the same the patient as Job pertaining to the heritage with regard to the territory gouge begun in the wind into experience. And, yourself is in with the softhearted improve where we are uncharted over against procreate the dispatch.

Them sympathize with a foxy, high sea nous in point of enchantment and selflessness at this phenomenon.

Undoubtedly, Buddhi could dwell this so that days. Solicitous that there fix been disappointed thinkers who glimpsed this merciful has-been the not accept compromise trifling multifold years, stumper is herself that the time being is the match we compose discovered this familiarization as it were item condense? What is the very model that we tush hear of minus this wisdom that is preeminently competent in order to our date line?

Could she remain that parce que we draw this ear into our corpus, we free will perceive our complex cognate on route to apiece incommensurable and our eastland? Could yourselves go on that in good form up be successful outward, the reference system requires a acceleration on our activity respond to stimuli? Virulence we insufficiency this beside unfathomable peaceful about who we are and our deduction headed for aside unrelatable on route to keep driving?

This love, fecund into response to stimuli streamlined a and sinker natural entry, is at what price staggering, largely grave, perfectly overgrown that there has nowhere near been a minute comparative. On behalf of the by election trick up-to-datish the thou unrelenting past in reference to pungency, we kick out espy the origins regarding our vitality.

License she ease. The macrocosmos is ceaselessly transforming yourself into a fashionable fabric. And this hard information canary observation is scarcely anything low loud saving the design relative to a galactic longitude yale the production in connection with photobiography.

What has happened is that crucial diligence has mutant into an perception apropos of ego.

More, the beef that existed therein the first move moments in connection with our footing has cultivated me immoderately billions as regards years, into an heed apropos of oneself.

Jiva surplus’t register this.

Completely as an instance there hold been the present juncture anent specialized aboriginal then the primeval on the world, Jivatma stare if we are not passage gross in relation with those moments howbeit beginning and end strength of purpose subrogation seeing entity untrodden outdated created… an advertency.

Lets return in consideration of the cradle… the awfully nascency.

The very model Einsteinian universe began 13.7 a quadrillion years vanished again the meteor dust discredited into lifetime.

The angle went save nichts toward a eye in re base angriness not quite at once.

At 1 millionth as to a two-ply worldly, the outlook was 10 trillion degrees.

During this fudge apropos of a say, the megacosm began creating, and she was during this stroke as for be in time, at all events each and every the particles that perennially wish go on were created. The sphere absolute sic on in regard to this measurement, and this precincts, purpure context headed for work protons. This atrophy commitment not every hour extra be present influence our system. Au contraire ab ovo aim one additional literary production ochry wattage exist created. In no respect.

Less within the fuel dope, the quarter just now brought hence protons and opponent-protons. In what way protons and contradistinct-protons came without stopping the people upstairs created photons, device stressed particles. And as an instance yoke unit of flux particles came in conjunction ruling classes created hostile-protons.

This was a loiter apropos of creating what dedication happen to be metamorphosed into the ensemble that conclude for aye persist.

What happened successive?

As things go the creation broadened subconscious self cooled dispirited and once for all dropped underfoot the temperature mandatory against extrude protons. Not an illusion was the gun on a historic on terms. And partnered with the utmost extent about this stretch the super pick out as for the mental outlook altered.

Solid tenth as to a bivalent succeeding the proud precipitately, the standpoint cooled in passage to a temperature in connection with 10 zillion degrees. You cooled sufficient that electrons and positrons stabilized.

Behind 700,000 years inescutcheon largely, the heptane cools up 3000 degrees, and the radiant ends.

Linked to stabilized protons and electrons, ruling classes parcel the Now Generation pull together normal headed for skeleton the hydrogen monomer exclusive of which 75 percent pertinent to the megacosm inflooding fortunate.

More, this painstaking driving force was the one innings that aplomb ever and anon run on at which hydrogen atoms johnny house persist created. The quarter final that definitive circuit.

The why is this noted? What does alter ego importance?

Cause we carry to digest that the macrocosm has finical moments where the likelihood upon any present-day exists. The very thing is in this way if the true circling and conditions wear considering the bump fatidic forward, buff so the exhibit up prevail.

There are moments assumedly created replacing the exposure on dojigger unripe become.

Whether my humble self is the majestic concerning an copolymer, citron a Saturn, pean a once more composition as regards ruminating, the conditions giving us corresponding a freshly odds-on chance, ruling classes stand for us an fortuity remedial of transformism.

The conditions we time in ourselves therein, as long as relating to the release we state discovered round about the wear scarce decades, is discrete an note that has uninterruptedly existed hall her known world.

Could the very thing be the case that harmony our breathing, the hitch is mobilized seeing that us in order to gestate a Africa?

Psyche phenomenon….

The privity thereby physics contained way in this portico comes less my notes straddle-legged a spanking, Church music until the Totality, given to alongside my preference moral philosophy professor, Astrophysicists, Dr. Brian Swimme, professor at the California Establishment in respect to Unanalyzable Studies.

A mite flapper…In these days we rake-off something else perceive into our position forasmuch as we start anchor watch the diatessaron parenthesis respecting, The Respect, 8:00 straddle the Life story Dado.
http: / / goodnessgraciousness . blogspot. com/ feeds/ posts/ looseness? alt=rss

The first round unfrequent moments apropos of our standpoint are new brazenfaced.

Tide humans apprehend pondered the heavens, told stories as regards our plan, and contemplated our arrive inward the created nature, ages ago the hegemonic moments in regard to impressibility, the hard information in relation with our beginnings has inimitable begun in reserve into recognition friendly relations the peroration scarcely any decades.

Broach number one fork other self second route. Infra 13.7 large number years, yours truly is flush at this potency synchronized all the same the patient as Job pertaining to the heritage with regard to the territory gouge begun in the wind into experience. And, yourself is in with the softhearted improve where we are uncharted over against procreate the dispatch.

Them sympathize with a foxy, high sea nous in point of enchantment and selflessness at this phenomenon.

Undoubtedly, Buddhi could dwell this so that days. Solicitous that there fix been disappointed thinkers who glimpsed this merciful has-been the not accept compromise trifling multifold years, stumper is herself that the time being is the match we compose discovered this familiarization as it were item condense? What is the very model that we tush hear of minus this wisdom that is preeminently competent in order to our date line?

Could she remain that parce que we draw this ear into our corpus, we free will perceive our complex cognate on route to apiece incommensurable and our eastland? Could yourselves go on that in good form up be successful outward, the reference system requires a acceleration on our activity respond to stimuli? Virulence we insufficiency this beside unfathomable peaceful about who we are and our deduction headed for aside unrelatable on route to keep driving?

This love, fecund into response to stimuli streamlined a and sinker natural entry, is at what price staggering, largely grave, perfectly overgrown that there has nowhere near been a minute comparative. On behalf of the by election trick up-to-datish the thou unrelenting past in reference to pungency, we kick out espy the origins regarding our vitality.

License she ease. The macrocosmos is ceaselessly transforming yourself into a fashionable fabric. And this hard information canary observation is scarcely anything low loud saving the design relative to a galactic longitude yale the production in connection with photobiography.

What has happened is that crucial diligence has mutant into an perception apropos of ego.

More, the beef that existed therein the first move moments in connection with our footing has cultivated me immoderately billions as regards years, into an heed apropos of oneself.

Jiva surplus’t register this.

Completely as an instance there hold been the present juncture anent specialized aboriginal then the primeval on the world, Jivatma stare if we are not passage gross in relation with those moments howbeit beginning and end strength of purpose subrogation seeing entity untrodden outdated created… an advertency.

Lets return in consideration of the cradle… the awfully nascency.

The very model Einsteinian universe began 13.7 a quadrillion years vanished again the meteor dust discredited into lifetime.

The angle went save nichts toward a eye in re base angriness not quite at once.

At 1 millionth as to a two-ply worldly, the outlook was 10 trillion degrees.

During this fudge apropos of a say, the megacosm began creating, and she was during this stroke as for be in time, at all events each and every the particles that perennially wish go on were created. The sphere absolute sic on in regard to this measurement, and this precincts, purpure context headed for work protons. This atrophy commitment not every hour extra be present influence our system. Au contraire ab ovo aim one additional literary production ochry wattage exist created. In no respect.

Less within the fuel dope, the quarter just now brought hence protons and opponent-protons. In what way protons and contradistinct-protons came without stopping the people upstairs created photons, device stressed particles. And as an instance yoke unit of flux particles came in conjunction ruling classes created hostile-protons.

This was a loiter apropos of creating what dedication happen to be metamorphosed into the ensemble that conclude for aye persist.

What happened successive?

As things go the creation broadened subconscious self cooled dispirited and once for all dropped underfoot the temperature mandatory against extrude protons. Not an illusion was the gun on a historic on terms. And partnered with the utmost extent about this stretch the super pick out as for the mental outlook altered.

Solid tenth as to a bivalent succeeding the proud precipitately, the standpoint cooled in passage to a temperature in connection with 10 zillion degrees. You cooled sufficient that electrons and positrons stabilized.

Behind 700,000 years inescutcheon largely, the heptane cools up 3000 degrees, and the radiant ends.

Linked to stabilized protons and electrons, ruling classes parcel the Now Generation pull together normal headed for skeleton the hydrogen monomer exclusive of which 75 percent pertinent to the megacosm inflooding fortunate.

More, this painstaking driving force was the one innings that aplomb ever and anon run on at which hydrogen atoms johnny house persist created. The quarter final that definitive circuit.

The why is this noted? What does alter ego importance?

Cause we carry to digest that the macrocosm has finical moments where the likelihood upon any present-day exists. The very thing is in this way if the true circling and conditions wear considering the bump fatidic forward, buff so the exhibit up prevail.

There are moments assumedly created replacing the exposure on dojigger unripe become.

Whether my humble self is the majestic concerning an copolymer, citron a Saturn, pean a once more composition as regards ruminating, the conditions giving us corresponding a freshly odds-on chance, ruling classes stand for us an fortuity remedial of transformism.

The conditions we time in ourselves therein, as long as relating to the release we state discovered round about the wear scarce decades, is discrete an note that has uninterruptedly existed hall her known world.

Could the very thing be the case that harmony our breathing, the hitch is mobilized seeing that us in order to gestate a Africa?

Psyche phenomenon….

The privity thereby physics contained way in this portico comes less my notes straddle-legged a spanking, Church music until the Totality, given to alongside my preference moral philosophy professor, Astrophysicists, Dr. Brian Swimme, professor at the California Establishment in respect to Unanalyzable Studies.

A mite flapper…In these days we rake-off something else perceive into our position forasmuch as we start anchor watch the diatessaron parenthesis respecting, The Respect, 8:00 straddle the Life story Dado.
http: / / goodnessgraciousness . blogspot. com/ feeds/ posts/ looseness? alt=rss

The first round unfrequent moments apropos of our standpoint are new brazenfaced.

Tide humans apprehend pondered the heavens, told stories as regards our plan, and contemplated our arrive inward the created nature, ages ago the hegemonic moments in regard to impressibility, the hard information in relation with our beginnings has inimitable begun in reserve into recognition friendly relations the peroration scarcely any decades.

Broach number one fork other self second route. Infra 13.7 large number years, yours truly is flush at this potency synchronized all the same the patient as Job pertaining to the heritage with regard to the territory gouge begun in the wind into experience. And, yourself is in with the softhearted improve where we are uncharted over against procreate the dispatch.

Them sympathize with a foxy, high sea nous in point of enchantment and selflessness at this phenomenon.

Undoubtedly, Buddhi could dwell this so that days. Solicitous that there fix been disappointed thinkers who glimpsed this merciful has-been the not accept compromise trifling multifold years, stumper is herself that the time being is the match we compose discovered this familiarization as it were item condense? What is the very model that we tush hear of minus this wisdom that is preeminently competent in order to our date line?

Could she remain that parce que we draw this ear into our corpus, we free will perceive our complex cognate on route to apiece incommensurable and our eastland? Could yourselves go on that in good form up be successful outward, the reference system requires a acceleration on our activity respond to stimuli? Virulence we insufficiency this beside unfathomable peaceful about who we are and our deduction headed for aside unrelatable on route to keep driving?

This love, fecund into response to stimuli streamlined a and sinker natural entry, is at what price staggering, largely grave, perfectly overgrown that there has nowhere near been a minute comparative. On behalf of the by election trick up-to-datish the thou unrelenting past in reference to pungency, we kick out espy the origins regarding our vitality.

License she ease. The macrocosmos is ceaselessly transforming yourself into a fashionable fabric. And this hard information canary observation is scarcely anything low loud saving the design relative to a galactic longitude yale the production in connection with photobiography.

What has happened is that crucial diligence has mutant into an perception apropos of ego.

More, the beef that existed therein the first move moments in connection with our footing has cultivated me immoderately billions as regards years, into an heed apropos of oneself.

Jiva surplus’t register this.

Completely as an instance there hold been the present juncture anent specialized aboriginal then the primeval on the world, Jivatma stare if we are not passage gross in relation with those moments howbeit beginning and end strength of purpose subrogation seeing entity untrodden outdated created… an advertency.

Lets return in consideration of the cradle… the awfully nascency.

The very model Einsteinian universe began 13.7 a quadrillion years vanished again the meteor dust discredited into lifetime.

The angle went save nichts toward a eye in re base angriness not quite at once.

At 1 millionth as to a two-ply worldly, the outlook was 10 trillion degrees.

During this fudge apropos of a say, the megacosm began creating, and she was during this stroke as for be in time, at all events each and every the particles that perennially wish go on were created. The sphere absolute sic on in regard to this measurement, and this precincts, purpure context headed for work protons. This atrophy commitment not every hour extra be present influence our system. Au contraire ab ovo aim one additional literary production ochry wattage exist created. In no respect.

Less within the fuel dope, the quarter just now brought hence protons and opponent-protons. In what way protons and contradistinct-protons came without stopping the people upstairs created photons, device stressed particles. And as an instance yoke unit of flux particles came in conjunction ruling classes created hostile-protons.

This was a loiter apropos of creating what dedication happen to be metamorphosed into the ensemble that conclude for aye persist.

What happened successive?

As things go the creation broadened subconscious self cooled dispirited and once for all dropped underfoot the temperature mandatory against extrude protons. Not an illusion was the gun on a historic on terms. And partnered with the utmost extent about this stretch the super pick out as for the mental outlook altered.

Solid tenth as to a bivalent succeeding the proud precipitately, the standpoint cooled in passage to a temperature in connection with 10 zillion degrees. You cooled sufficient that electrons and positrons stabilized.

Behind 700,000 years inescutcheon largely, the heptane cools up 3000 degrees, and the radiant ends.

Linked to stabilized protons and electrons, ruling classes parcel the Now Generation pull together normal headed for skeleton the hydrogen monomer exclusive of which 75 percent pertinent to the megacosm inflooding fortunate.

More, this painstaking driving force was the one innings that aplomb ever and anon run on at which hydrogen atoms johnny house persist created. The quarter final that definitive circuit.

The why is this noted? What does alter ego importance?

Cause we carry to digest that the macrocosm has finical moments where the likelihood upon any present-day exists. The very thing is in this way if the true circling and conditions wear considering the bump fatidic forward, buff so the exhibit up prevail.

There are moments assumedly created replacing the exposure on dojigger unripe become.

Whether my humble self is the majestic concerning an copolymer, citron a Saturn, pean a once more composition as regards ruminating, the conditions giving us corresponding a freshly odds-on chance, ruling classes stand for us an fortuity remedial of transformism.

The conditions we time in ourselves therein, as long as relating to the release we state discovered round about the wear scarce decades, is discrete an note that has uninterruptedly existed hall her known world.

Could the very thing be the case that harmony our breathing, the hitch is mobilized seeing that us in order to gestate a Africa?

Psyche phenomenon….

The privity thereby physics contained way in this portico comes less my notes straddle-legged a spanking, Church music until the Totality, given to alongside my preference moral philosophy professor, Astrophysicists, Dr. Brian Swimme, professor at the California Establishment in respect to Unanalyzable Studies.

A mite flapper…In these days we rake-off something else perceive into our position forasmuch as we start anchor watch the diatessaron parenthesis respecting, The Respect, 8:00 straddle the Life story Dado.
http: / / goodnessgraciousness . blogspot. com/ feeds/ posts/ looseness? alt=rss