Hi Vidar, > A more REST-like approach would be to post to /account-entry/*. You > would then use a SlingPostOperation or SlingPostProcessor to do the > validation and/or persisting.
If I post to /account-entry/*. It still find the resource resolver I have which has resource type as "myapp/account-entry.jsp.". Plus, In PostProcessor or PostOperation, I do not get handle to HttpServletResponse so I can not redirect to Url I want. So it ends up showing up same JSP again. I think using servlet for handling POST request gave a lot more control. (But doesnt fit well in the REST style) Am I missing anything here.? Thanks, Unmesh > ... or to /account-entry/some-newly-created-identifier.html, which > displays the state of the created account. > >> 3. A GET request is made to /account-summary > > ... account-entry/some-newly-created-identifier > >> a) I have a resource resolver which resolves /account-summary to resource >> b) This resource resolver makes a back end web service call to get >> account details >> c) This resource resolver has resource type as >> /apps/myapp/account-summary.jsp >> d) account-summary.jsp is presented to the user. > > So to wrap it up, instead of mapping your servlets to absolute paths, > and have the end-user request them, let the end-user request the > account resource itself. > > -- > Vidar S. Ramdal <[email protected]> - http://www.idium.no > Sommerrogata 13-15, N-0255 Oslo, Norway > + 47 22 00 84 00 / +47 22 00 84 76 > Quando omni flunkus moritatus! >
