Hi ,
Why don't we do web-remoting. Since we dont have a
servlet container we cannot go for servlet based approaches for web
remoting (Current standard ones being DWR or JSONRPC-JAVA) . These two
can make it possible for us to have javascript proxies of java objects
at the client side. Since we have an httpserver we can probably do
something similar to these frameworks and allow Ajax XHR calls direct
to the ejbs.
I have not yet investigated the webadmin :( .so i am not
aware how it currently functions but it think it allows me to call
ejbs via HTTP. We may be able to use some Ajax libraries like DOJO (or
any other one) which provide standard widgets for a good look and feel
at the client side.
So the approach i am proposing is that we have HTML
pages using the standard dojo widgets hosted on the http server and we
directly make async calls to the ejbs via http. But again I am just
shooting in the dark here.
Regards
Manu
On 8/28/07, Mohammad Nour El-Din <[EMAIL PROTECTED]> wrote:
> Hi Karan, what did u mean by the Apache Commons Http, did u mean Apache
> Commons HttpClient, but it does not support building Http servers just
> clients !!!
>
> On 8/26/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
> >
> > I have been thinking about this. Would it be a good idea to port
> > WebAdmin to a more commonly known MVC framework like JSF?
> >
> > We could embed an HttpServer using apache commons Http which could
> > service web requests.
> >
> > The benefits I see here are
> > 1. Standard framework which becomes easier to maintain and add more
> > features to
> > 2. Standard out of the box GUI components which could be dropped into
> > the web interface
> > 3. Availability of more powerful and complex GUI components , e.g.
> > myfaces.apache.org
> > 4. Easier/Faster for other contributors to jump in and provide
> > enhancements (no steep learning curve)
> > 5. Can be AJAX'ed easily through libraries like ajax4jsf etc.
> >
> > What do you think?
> >
> > --
> > Karan Singh Malhi
> >
>
>
>
> --
> Thanks
> - Mohammad Nour
>
