Chuck, as usual you have shone a bright light onto proceedings.
We use shortened URLs and apache rewrites which explains the
appearance of the -9999 early in the URL. That wasn't the problem.
This is what made me understand:
3. You had storing the session ID and Instance Number in cookies
enabled
So wotaskd can route the request if:
a) It has the negative port number in the URL = go straight there
b) It has the port number in a cookie associated with a session = go
straight there
c) No session, no port number specified = find a running instance and
route to one of those
It so happened that my colleague had a session active when he was
checking the links for me. When I triggered a session first, my hand-
rolled links with no negative port number worked too - like magic. So
it has always been this way but finally I now know why. I was hitting
c) above and in development I don't have such instances available.
I suspect it relates to my Run... script as that seemed to get
hosed by an SVN checkout at one point.
The launch config gets stored in the workspace metadata, not in the
project. So svn checkouts should not affect this.
Yeah, I think I had done what Florijan said and made the launch file
part of the visible project.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
