Re: Something weird happening with fusion/pluto
Fabrice Dewasmes wrote:
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:XXX/media-type/html/language/-1/user/anon/Accueil.psml/js_pane/P-XX-10003
(XXXs are to be replaced with a alphanumeric sequence)
and if I remove the _ns: 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]
Re: Something weird happening with fusion/pluto
Le 30 mars 05, à 18:45, David Sean Taylor a écrit :
Fabrice Dewasmes wrote:
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:XXX/media-type/html/language/-1/user/
anon/Accueil.psml/js_pane/P-XX-10003
(XXXs are to be replaced with a alphanumeric sequence)
and if I remove the _ns: 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.
Thanks for your reply and interest David. In fact I'm using Jetspeed
1/fusion that depends on the M1 release of J2. Is it your case ?
Be careful that everything works pretty fine when you're on the user
default psml page. Did you use another psml page in which is the JSR168
portlet ?
Thanks again for your help. I will test this evening with latest from
CVS head.
Fabrice
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Something weird happening with fusion/pluto
Fabrice Dewasmes wrote: Le 30 mars 05, à 18:45, David Sean Taylor a écrit : Fabrice Dewasmes wrote: 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. Thanks for your reply and interest David. In fact I'm using Jetspeed 1/fusion that depends on the M1 release of J2. Is it your case ? No, all my Fusion builds here are from September 2004 Slippery slope since then Be careful that everything works pretty fine when you're on the user default psml page. Did you use another psml page in which is the JSR168 portlet ? yes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Something weird happening with fusion/pluto
Fabrice Dewasmes wrote:
Le 30 mars 05, à 18:45, David Sean Taylor a écrit :
Fabrice Dewasmes wrote:
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:XXX/media-type/html/language/-1/user/
anon/Accueil.psml/js_pane/P-XX-10003
(XXXs are to be replaced with a alphanumeric sequence)
and if I remove the _ns: 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.
Thanks for your reply and interest David. In fact I'm using Jetspeed
1/fusion that depends on the M1 release of J2. Is it your case ?
Be careful that everything works pretty fine when you're on the user
default psml page. Did you use another psml page in which is the
JSR168 portlet ?
Thanks again for your help. I will test this evening with latest from
CVS head.
Fabrice
David,
I've tested the same scenario against the latest from head + the fusion
refactoring sync. The same problem appears...
This is really bad news for us as we definitely need to switch between
psml pages
Please could you help us ? I've investigated a bit but it's difficult to
find my way. Any pointers ?
Fabrice
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Fabrice Dewasmes
Responsable du domaine urbanisation des systèmes d'information
[EMAIL PROTECTED]
06.89.88.65.37
--
Open Wide
14 rue Gaillon
75002 PARIS
www.openwide.fr
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Something weird happening with fusion/pluto
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:XXX/media-type/html/language/-1/user/anon/Accueil.psml/js_pane/P-XX-10003
(XXXs are to be replaced with a alphanumeric sequence)
and if I remove the _ns: part everything works fine !
Am I wrong ? What is this mysterious _ns:part ?
Thank you very much for your help.
Best regards
Fabrice
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
