I have two instances of WPS 5.0 with what I believe to be comparable configu
rations, but a portlet I wrote is producing different results on the two por
tals when invoking the PortletResponse.createURI() method (or at least in th
e PortletURI.toString() met
hod from an object created by the createURI() method). One portal is concate
nating a page sequence number (for lack of a better term) in the format "/.d
/n" where 'n' is a single digit (0..9) on the end of the URI (before any par
ameters) and the other is n
ot. Each performance of doView() assigns the same digit to all URIs, and the
 digit is bumped up by one on each successive call back to the portlet via o
ne of the generated URIs. Does anyone know what configuration setting contro
ls this? Is there an API ca
ll that can disable this behavior (i.e. override the setting for this portle
t)?

This is for an internal news portlet, and the URIs are calls back to the por
tlet to display different articles. I have a page designer who wants the sta
ndard visited links coloration to work so that the user knows which articles
 they have read, and the se
quence number is creating some URI differentiation that I don't want, so I w
ould like to turn it off.

No other links generated by the portal appear to have this "/.d/n" added to 
the URI. Even wild speculations are welcome.

[ Post a follow-up to this message ]

Dave,
Trying to make any predictions with regard to how the portal server generate
s its URI's will get you into trouble. They change per version and/or releas
e.
You could try setting uri.requestid = true and see if the URI's are better b
ehaved.
Have you tried URL Mapping for these pages? That would eliminate the funky p
ortal URI's since you assign the mappings in the portal configuration.

[ Post a follow-up to this message ]