On Oct 3, 2007, at 7:09 AM, Eric Dalquist 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.
Right.
My curiosity (never having used a bridge library) was how the bridges
that try to smoosh servlets into portlets have some kind of wrapping
or translation they do at that level to fake portletURL generation
through the HttpServletRequest methods. Not sure what approach RSF
takes.
Jason
--
Jason Shao
Application Developer
Rutgers University, Office of Instructional & Research Technology
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http://
jay.shao.org
--
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
