An update:
We're still not sure why the wrong port number is being used - the
cause seems to be in whatever is implementating the javax.portlet
package.
For now, we've fixed a bug in our apache configuration that was
supposed to be eliminating the need for the port number at all. Now,
no port number is necessary, so the fact that it would be wrong is
not an issue.
This one is being filed on the back burner for now. Thanks to
everyone for your input!
--
Anastasia Cheetham [EMAIL PROTECTED]
Software Designer, Fluid Project
Adaptive Technology Resource Centre / University of Toronto
"Even if you're on the right track,
you'll get run over if you just sit there."
-- Will Rogers
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
