| Brian J. Sayatovic 2006-05-11, 1:17 pm |
| When I tried this, I used the content node "wps.My Portal" which is for the
main My Portal. My hope was that this would render "/wps/myportal" so I
could follow it up with some URL contexts I have relative to that...
<portalwps:urlGeneration contentNode="wps.My Portal">
<a href="<% wpsURL.write(out); %>/MySpecialContext" > Link to
another portal page </a>
</portalwps:urlGeneration>
But the URL that was rendered to the page was something like:
.../wps/myportal/!ut/p/_3_07/_7_A3/MySpecialContext
And that doesn't work. What I wanted was
.../wps/myportal/MySpecialContext
What causes the extra "!ut/p/_3_07/_7_A3"? Isn't that related to actions?
I believe a solution might be to set a Custom Unique ID for the
MySpecialContext content node, and then use that. But I have quite a few
URL context mappings in WPS, so I'm ready to set this up for each of them.
It seems like an unnecessary step that I have to go through only because I
don't want to hard-code the string "/wps/myportal".
<bmargoli@us.ibm.com> wrote in message
news:1715368052.1147269869977.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> The urlGeneration tag will do this for you:
>
> <%@ taglib uri="/WEB-INF/tld/portal.tld" prefix="portalwps" %>
>
> ..
>
> <portalwps:urlGeneration contentNode="nodeid"
accessControlCheck="NoCheck">
> <a href="<% wpsURL.write(out); %>" > Link to another portal page </a>
> </portalwps:urlGeneration>
|