Eelco, you are right. But I'm not thinking about a whole application service
framework, but just a fast way to expose services.
There a lot of situation where you need to expose some "small" functionality
in a web application. Using Wicket as web application framework it think
would be nice and useful to have a fast way to expose embeded service in
your application jar.
Paolo
On 12/6/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I don't know. There are other frameworks that are great with such
services, and such services don't benefit as much from a stateful
model as web interfaces do. Theoretically, you can use Wicket for
anything that generates markup, but Wicket is not the golden hammer.
Eelco
On 12/6/06, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote:
> Wicket is a wonderful framework for handle web pages request. But I'm
> thinking that it would be nice too to publish general "web" service
without
> any visual component associated.
>
> In other word would be very useful to use Wicket to expose a server side
> services in protocol agnostic way.
>
> For example having something like that :
>
>
> public void init() {
>
> mount( "/trade", new TradeService() );
>
> }
>
>
> The protocol to be used could be SOAP, REST, JSON, XML-RPC, plain HTTP
or
> whatever else, but injected using a defined interface.
>
> What do you think about that?
>
> Any ideas/suggestions where to start from?
>
>
> Paolo
>
>
