At one point I can understand you frustration in having to get webware
correctly configured with apache just to see it work. However, this is
really no different they many other web application frameworks, (the
difference is java which almost always ship with their own httpd
servers), but this is really no different then PHP, coldfussion, just
regular CGI or about any other situation where you want to pump data out
to the web. Sorry for not being totally sympathetic, but a working
httpd is just a requirement, and frankly webware is not all that hard to
set up, with apache it is just a couple of lines added to the
httpd.conf, which can be found in the either the documentation or on the
[mailto:webware-discuss-admin@...] On Behalf Of deelan
Sent: Wednesday, May 05, 2004 9:19 AM
Cc: Ian Bicking
Subject: Re: [Webware-discuss] Stand-alone appserver (Unhappy with
Ian Bicking wrote:
> It's got to have something to do with the socket handling, which is
> something all the adapters do the same way. If, for instance, he used
> the built-in HTTP server (in CVS, I think if you do "AppServer.bat
> you'll get it), I suspect this might not happen.
this is *very* nice and should be publicized a bit more!
one of the most irritating things for a webware newbie (or for me at
least) is to be forced to deal immediately with apache in order to
see something running.
i've just downloaded the latest CVS webware's snapshot, installed
it, created a work dir and run "AppServer.bat http". it started the app
and listened to port 8080 for incoming web requests.
again, very nice!
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
Webware-discuss mailing list