Re: [xwt-users] xwar file launch from IIS??

Emiliano Heyns <[email protected]>
Newsgroups gmane.comp.java.xwt.users
Message-ID <[email protected]>
On Mon, Aug 11, 2003 at 06:53:44AM +0000, Charles Goodwin wrote:
> On Mon, 2003-08-11 at 06:02, arvin seluka wrote:
> > Can we launch xwar files from IIS locally?
> 
> It depends what you mean.  If you want to run your own launcher, then
> the answer is 'yes and no'.  Nice and confusing. :)
> 
> The Java version of the launcher, the version mainly supported for use
> with XWT, needs to be run as a servlet on something like Tomcat.  I
> don't know if IIS can run Java servlets, although I'd bet against it.

IIS itself can't, but there are servlet containers that IIS can connect
to much the same way as Apache can be configured to kick through
requests to the servlet container. xwt.org does this. I don't know any
open source servlet container that has an IIS connector, though. If you
can find one, the self-contained launcher is almost certainly the
easiest approach.

> However, there is a PHP version of the launcher.  I do not know how well
> that works - Emile would be the contact on that one as he translated the
> Java version into PHP.

The PHP version is available on xwt-services.sourceforge.net. Although
it hasn't seen all that much testing, the launcher isn't any kind of
voodoo; it is in fact simple enough that I could replicate it in some
300 lines of PHP. Any problems found should be easily fixed.

> > If so how to configure IIS and  make it work?
> 
> For the PHP version, you can set up PHP with IIS and then just drop the
> launcher in as a webpage, I guess.  I'm not big on PHP though, so it
> might be best to wait for Emile(@xwt.org) to respond or to ask him
> directly.

Yep, install PHP, put the launcher page inplace, done. If you don't want
PHP, it should take a competent coder no more than a day to transform it
into ASP.

-- 
Emiliano
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.