Subj : Re: web services
To   : netscape.public.mozilla.jseng
From : "Jim Wang" <jimw@olymtech.com>
Date : Sat Dec 06 2003 12:16 pm

Thanks for the reply to my message.  Could not agree more on making things
simple.  I was very curious if such facade exsited already.

We are making a platfrom that would allow developers to develop web based
applications using just JavaScript and JSP.  The applications will run on a
runtime platform we built that in turn runs on J2EE applicaiton servers.
The goal is RAD and simple enough for all the web developers (assume most of
the web developers know how to use JavaScript) and no JAVA is needed.  We
are at the final stage of making our 0.5 release for beta.

To plan ahead, we wanted to include web service support into the next
release.  We want some thing that is very simple for JavaScript developers
to use (no Java).

WebServiceProxyFactory seems to be fairly easy to use.  Unfortunately it is
not available to server side JavaScript yet.  A facade is certainly much
better.

Thanks

Jim

"Mark Turansky" <markturansky@hotmail.com> wrote in message
news:bqq8g5$rds1@ripley.netscape.com...
> I profess ignorance about the WebServiceProxyFactory or other APIs in
> Mozilla, but I still have my $0.02.....
>
> If there is a component responsible for web services, couldn't a simple
> JavaScript object (extending ScriptableObject) be used to wrap the
> component, thereby making it available to javascript?
>
> I think the Facade pattern would fit here.  Make the Facade an easy
> pass-through to the more complicated web service API.  As per the Gang of
> Four, the Facade to the web service would make the entire subsystem (the
web
> service) easier to use.
>
> would that not work?
>
> "Johnny Stenback" <jst@mozilla.jstenback.com> wrote in message
> news:3FCFD700.6000306@mozilla.jstenback.com...
> > Jim Wang wrote:
> > > Is it possible to take the web service API such as
> WebServiceProxyFactory in
> > > Mozilla to be available to server-side JavaScript?  How?
> > >
> >
> > Possible? Yeah. Trivial? No. To do that you'd need to pull in all of the
> > code that the web services code depends on, and that means at least
> > XPConnect, the JS engine (obviously), XPCOM, parts of the Mozilla DOM
> > code (mozilla/content and mozilla/dom), xmlectras, necko, expat (and
> > parts of mozilla/htmlparser) and probably more. On top of that you need
> > to re-think the async/sync IO model that's used in Mozilla.
> >
> > It'd be awesome to have this done and have instructions on how to do it,
> > so if this is a task you're interested in doing, let us know and I (and
> > onthers too) can try to advice as much as I can.
> >
> > > Thanks
> > >
> > > Jim
> > >
> > >
> >
> >
> > --
> > jst
>
>

.