True, but as I said, one does not necessarily exclude the other. In its current state such a use of Jersey is best suited for low-interactivity, data-driven applications - but the same could be said for other web frameworks such as Stripes.
Jersey provides implicit and explicit views through JSP's out of the box: http://blogs.sun.com/sandoz/entry/mvcj That's the way I use it, people have plugged in their own template layers. I'd be interested in a component model such as Wicket on top, which is why I reacted to this thread. I think there's a broad understanding that the Wicket model makes programmers happy. /Casper On Wed, Apr 1, 2009 at 7:25 PM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > 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 <cas...@jbr.dk> 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
