Hi, Jerome and Alex. What do you think on the implementation:
1) Coocoon map concept (http://cocoon.apache.org/2.2/core-modules/core/2.2/1376_1_1.html), just to provide more declarative way to configure URI - Restlets mapping? 2) Internal Restful design of web-application? means to get name for each of the individual classes/resources/restlet with the help of java5 annotation @uri("schema://internal/weatherwidgetresource") and use them as individual pipes (POST data to proccess and getTheRepresentation of the result) We can use http://smallx.dev.java.net or cocoon maps notation (http://cocoon.apache.org/2.2/core-modules/core/2.2/853_1_1.html) to provide info for the coordination of such a pipes / URI. I think that reasons to do this are a) to get all advantages that cocoon offers by providing declarative URI model and pipeline support b) do the mentioned actions in distibuted manner, since each pipe can be deployed in any place of the web (or in scope of your cluster), due to REST notion of the pipe (GET, POST) and ability to negotiate on the representation (JAVA_IN_PROCESS, SAX, DOM, or custom one). I 'd be pleased to work on such an feature.
