Re: WOApplet ... why URL is wrong
Re: WOApplet ... why URL is wrong
- Subject: Re: WOApplet ... why URL is wrong
- From: MacFirst <email@hidden>
- Date: Fri, 14 Jan 2005 13:33:53 -0800
on 1/14/05 11:04 AM, Chuck Hill <email@hidden> went on and on
saying, in part:
>> there is no 'cgi-bin' folder in '/Library/WebServer/Documents/' !!
>> where this uri is coming from ?
> Your app.
> Chuck
Chuck,
I know you're a smart guy who knows your WO very well, but I have to ask: do
you work for Microsoft? Your recent answers to this thread (which I've been
following fairly closely as I've also never gotten this working and received
zero replies when asking if anyone else has -- twice!) remind me of the old
joke about the guy lost in a helicopter/balloon who gets answers that "while
technically correct, provide no useful information." ;)
I saw in a recent post that you hate direct connect -- aside from the
problem that it messes with WOApplets, is there a reason one should avoid
this seemingly very-useful development tool?
More to the point, can you provide any information about how to hook-up a
WOApplet to make it work? Something beyond the rather vague and ambiguous
(and, seemingly, not-accurate) information provided in the docs, I mean <G>.
I'd really-really love to see an example of a working WOApplication that
received parameters from the WO-app and returned information to that WO-app,
using standard WOApplet communication techniques (vice some silly hack that
bypasses the WOApplet.) Heck, I'd be willing to PAY for a decent example of
such a thing!
Thanks!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden