huh? wicket is trying to address a completely different problem space - which is orthogonal to what restlet and other rest-like services are trying to achieve.
do any of these restlet-like services provide anything to help you generate the ui? do they have jstl tags? components? templating? nothing out of the box right? you have to glue that yourself on top of them. -igor On Wed, Apr 1, 2009 at 10:05 AM, Casper Bang <[email protected]> wrote: >> restlet is for building services not uis, that quote makes absolutely no >> sense. >> > > While I agree the quote smells of FUD, one doesn't necessarily exclude the > other. The beauty of REST is its statelessness, addressability, > representation negotiation, caching and other ways it embraces HTTP rather > than run away from it (and use overloaded POST's with tiny RPC handlers for > everything). > > In Jersey it's also possible to serve (dynamic) HTML through a standard > templating engine, I'm doing this currently and achieving very high > scalability while keeping things simple. The caveat with this approach is > that you are stuck to the classic templating model and components don't > really exist apart from whatever jQuery/ExtJS stuff you wire up manually. > > So probably like the OP, I can't help but wonder about the possebility of > Wicket running on top as a model-view technology - or perhaps just a > programming model adopted after Wicket. > > /Casper > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
