No problem, I'm sure we'd all love to hear what you figure out eventually. -Eric
[EMAIL PROTECTED] wrote: > Eric Dalquist <[EMAIL PROTECTED]> wrote: > >> For anything executing as a JSR-168 portlet there is no valid >> request.getServerPort() call. While technically you can access a >> HttpServletRequest object when rendering in a JSP that object should >> never be used, the portlet's request/response objects must be used >> instead. The main question is how are URLs generated, as Chris pointed >> out portlets must generate URLs through an API that takes care of the >> entire URL string. My guess is there is something else going on with URL >> generation for the portlet (string concatenation or some such) and the >> format just happens to be close enough to what uPortal expects to work. > > The tool *is* executing as a JSR-168 portlet. It doesn't use > HttpServletRequest directly, it uses RSF's portlet library. It's > looking like the problem is related to the RSF code, and is not > uPortal specific. > > Thanks to all for the questions and suggestions, it has helped point > me toward where to look for this. >
smime.p7s
Description: S/MIME Cryptographic Signature
