Hi. I have recently used restlet and found it great. Expecially, the REST approach helps you creating a more well crafted web application. Now I like to use wicket for the frontend and I wondered how to mix the two stuff: I wanted to keep the REST API and I'd like the web client uses the exact same backend.
That is, instead of injecting a service in the web client that direcyly access the JPA backend, I injected a client based on Restlet. So I make an HTTP call to the backend to persist, read and search the data. What do you think about such approach? Do you foresee any limitations? I like it a lot: Clean separation of responsability: you tend to do stuff better, cause you firsst think at the REST API for a task, then the web frontend follow in a natural I have an app with a REST API that's the same I use "internally". The client starts/stop/restart real faster as long as it is not connected to any spring/jpa/database connection. It's just wicket. Mocking is easy for unit testing. I can develop a second frontend based on the exact same backend instance, for mobile, new web prototype, another mashup. What I did not try yet is to make both server and web frontend run on the same OSGI server. Any advice on running wicket on a Felix/Karaf instance? -- Daniele Dellafiore http://danieledellafiore.net --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
