How to return XML response in acceptRepresent?

Hi, My form has 2 fields which I'm submitting through POST request, say first name & last name. Now, as a reposnse back, I need to get the XML response in some format say 101 niles rd 589-423-4344 How do I get this XML? I mean where to prepare this XML? I'll be fetching input p

RE: Spring + Restlet 1.2-SNAPSHOT, NullPointerException

Thanks to Kevin and Jerome's help, I was able to get a working Spring configuration. It still uses the deprecated Resource class, but it works for now and that's good enough for my needs. In case anyone is following this thread, here are the details: applicationContext.xml: http://www.spring

authentication

Hi, i'm a student and i'm new of RESTlet. Can you help me about this problem? How can I allow or not the access to resources or posting of this ones in base to user that require it? How can I, one time the specific client is authenticated, filter allowed operations?? Is it possible to make to do

Distributed Observer Pattern

Hello everyone, I'd like to implement something based on the Distributed Observer Pattern as described by Duncan Cragg on http://duncan-cragg.org/blog/post/distributed-observer-pattern-rest-dialogues/ When a "client" GETs a resource, I like it to send an extra header saying it wants to receive

Re: restlet as a jax-rs implementation

Stephan Koops wrote: > Hi Philippe, > > is "prefix" also the @Path on your root resource class? No. > Than you have to use only "/*" as url-pattern. I can't do that. I can't control how my code is assembled into a web application. And even if I could if it worked only one way that would give i

Questions about HTTP Authentication

Hi, I am relatively new to Restlet and am facing a problem regarding HTTP Authentication. I have a Resource that when handling a POST Request has to decide dynamically wheter it requires authentication or not (basically based on the XML the client sends). I want that the clients can use the HTT

Re: restlet as a jax-rs implementation

Hi Philippe, you wrote, that your path is mapped to a subpath of the path, you expect. Could you show the path you configure (form @Path), the path you expect to use, and the path, where you reach the resource, but where you don't expect it? best regards Stephan

Re: Distributed Observer Pattern

So, in case people don't actually click the link, let me repeat from the article: "this only applies where the feed consumer is a visible and POSTable server ... and probably where the number of subscribers is relatively small ... This isn't done now simply because of the asymmetry of the current W

Re: How to return XML response in acceptRepresent?

Hello Rick, just simply set the entity of the Response. If you are using Restlet 1.1: Representation rep = ; getResponse().setEntity(rep); You can build your XML representation using a simpe StringRepresentation, or a DomRepresentation (have a look here http://www.restlet.org/documentation/1.

Re: What is allowPost & allowPut?

Hello, basically, when a resource does not support a method, a 406 status is resturned (Method not allowed). The way a resource defines its supported method is via the "allow*" methods and the "modifiable" attribute (which tells: "I support POST, PUT, DELETE methods"). >Can any one please expl

Re: authentication

Hello, Here is the head chapter in the wiki (aka "User guide") that explains security: http://wiki.restlet.org/docs_1.1/13-restlet/27-restlet/46-restlet.html You should have a look at the "authentication", "authorization" sub parts (see links at the left, in the vertical menu). Can you have a l

Re: post in putUser Bookmark throws error

Hi, the answer is no. If you know by advance the URI of a resource, you can (or must, or should) create it with a PUT request. Keep in mind that: - a resource is a concept. A URL says that "there is a concept located at this address", and there is no link with the fact that this resource has e

Restlet scripting update

Hi all, After discussion with Tal Liron, it has been decided that the "org.restlet.ext.script" extension that Tal had contributed to Restlet 1.2 would move to a separate "Restoration" project managed by Tal: http://threecrickets.com/restoration/ The Restlet project still has a plan for for dire

Redirector/Resolver relative path

Hi I'm using Redirector to proxy Requests from HTTP to HTTPS but I want to forward Requests from a sub URL to an external URL and all paths should be relative to a given path. For example: http://www.myapp.com/path/example.com/morepath/XYZ should be redirected to (in dispatcher mode): https://ww

Re: Questions about HTTP Authentication

Hi mstricker, the Guards could do the authentication for you, including decryption and so on, but only for the full resource or not. I propose to think about to use two different resources - one secured and the other not. But if this is not useful for your application, than you have to impleme

Re: Questions about HTTP Authentication

Hi Stephan, I cannot secure my whole resource, so I try to use the ChallengeResponse object. I need to get the password the user sends through http_auth but do not get it in cleartext. Using username user and password test the ChallengeResponse provides the following data: log

Re: Distributed Observer Pattern

You might want to check out the following IETF draft that proposes a standard for doing this with SIP. You'd probably want to follow at least the style of this proposal in your implementation. http://www.ietf.org/internet-drafts/draft-roach-sip-http-subscribe-01.txt dave On Mon, Apr 20, 2009 at

"CRUD Items" pattern

Hi everyone, I've been trying to think of a streamlined solution to a common task in Restlet, and would like to open it up to some brainstorming. The pattern would be very familiar to you, as it even appears in the Restlet tutorials. I've been clumsily calling it "CRUD items." It looks like

Re: "CRUD Items" pattern

First of all, it's not clear for me the POST operation against /item/{id}. I would suppose that we POST new representation on the non existed resource that will be created with the provided one. So /item/{id} will be created after such operation. Secondly, I would prefer to have POST [rep] to /ite

Re: "CRUD Items" pattern

Howdy, On Apr 21, 2009, at 11:59 , Tal Liron wrote: [...] > The pattern would be very familiar to you, as it even appears in the > Restlet tutorials. I've been clumsily calling it "CRUD items." It > looks > like this: > > We have one resource at a URI like: /items > > It responds to GET with a l

Re: "CRUD Items" pattern

Think John and I are in the same place. > We have one resource at a URI like: /items ... > It responds to PUT by creating a new item Unless PUT is putting back the full representation of the list of items (with some new items in it) this would seem like an unexpected REST semantic; I generally ex

Re: "CRUD Items" pattern

Thanks for the feedback, guys! Obviously there are many variations on this "pattern". I was trying to generalize, and I accept your quibbles as valid. :) For a good example, why not look at the Restlet tutorial? http://www.restlet.org/documentation/1.2/firstResource We here have "ItemsResou

Re: "CRUD Items" pattern

On Apr 21, 2009, at 12:49 , Tal Liron wrote: [...] > Thanks for the feedback, guys! Obviously there are many variations on > this "pattern". I was trying to generalize, and I accept your quibbles > as valid. :) > > For a good example, why not look at the Restlet tutorial? > > http://www.restlet.org

Re: "CRUD Items" pattern

Thanks, John. You're right, and of course I am abstracting the core behaviors! My solution so far is actually the opposite of what you suggest. I have two root classes, one for "Item", one for "Items". Each in turn routes to a separate class I created, for which each primary resource creates an