Xavier Lawrence wrote:
Thanks a lot ATE !!! I'll try what you advise. Things are a bit difficult for me since I did not write the initial application...
I just have 1 comment about the Guess number portlet. See below.
<snip/>
A strange thing was that when I tried to launch the portlet, Jetspeed started to print out these lines, just after the XSLT filter was called:
cheater: target value = 99 cheater: target value = 59 cheater: target value = 55 cheater: target value = 29
So what is going on ? It seems that the filter reloads the Number Guess portlet ??? Why would it do so ?
Totally unrelated.
The Number Guess porlet is on the start page of Jetspeed-2 and writes out a few debug messages to the console. You can ignore these. I guess you have your Portlet Application also defined on the start page and that is why you see the XSLT Filter being called as result of the same (Portal) request (if its before or after the Number Guess Portlet depends on the order the Poral Aggregator invokes the portlets).
No, my portlet is invoked from another PSML page, that's why I found it strange that the Guess number portlet was logging debug messages.
Any idea why a portlet in a separate portal page would make a portlet in another portal page reload ???
I don't know. and I can't reproduce that, I tested it out just a sec ago. If I start Tomcat and open my browser on: http://localhost:8080/jetspeed/portal/jpetstore.psml I don't get that message. Only when I access a page containing the NumberGuess portlet.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
