Hi all !
I'm using JS1 + fusion (without the latest deployment model)
1. The user logs in (let's say he's in role 'dummy') 2. the default dummy psml page is rendered 3. the user chooses another PSML Page using the drop down menu at the top right of the page and is now on a psml page from anon user. 4. User clicks on a link which has been rendered by a renderResponse.createActionURL().toString() on a JSR168 portlet. And that's where the trick happens... He's redirected on the default user's psml page ('dummy' psml page). (Which of course is not what we want : the previously clicked portlet is even not displayed). So the problem won't occur if the JSR168 porlet is in the 'dummy' psml page.
After investigating it seems that the rendered URL is something like /jetspeed/portal/_ns:XXXXXXXXXXX/media-type/html/language/-1/user/anon/Accueil.psml/js_pane/P-XXXXXXXXXX-10003 (XXXs are to be replaced with a alphanumeric sequence) and if I remove the _ns:XXXXXXXXXXXX part everything works fine !
Am I wrong ? What is this mysterious _ns:part ?
Thats the navigational state for JSR 168 portlets.
I tried your case against a running version of Fusion here, and it works fine (it stays on the same page and tab). Unfortunately all of my work (and installed applications) with Fusion was before the new navigational state implementation in Jetspeed-2.
I will need to upgrade my Fusion installs soon. Hope to get some time to work on this over the next week. Will look out for this bug, thanks
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
