First off,
If you're using JBoss Portal Server (and you are) to develop a portal
application, you've basically made the following technical decisions:
* You want to use Sun's JSR168 Portlet specification as a model of how you
develop portlets
* You want to use the JSR168-Portlet API's
Given these facts, you need to spend some time reviewing the JSR 168 Portlet
specification to understand what you get when you opt to use JBoss Portal
Server - you can find the spec here
Having said these things, if you review PLT.11.1.1 Request Parameter's, you
will find the following statement:
anonymous wrote : A portlet must not see any parameter targeted to other
portlets.
What this means is that the behavior you are seeing is correct in JBoss Portal
- that is, the portlet that responds to the button click (submit?) correctly
can see the 'data' (request parameters) but other portlets correctly cannot see
the 'data.' If you need to 'share data' - you need to design a scheme in which
you place this 'data' in higher scope than request. You can use PortletSession
and PortletContext to 'share data' - in order to choose which scope to use,
reviewing the JSR168 spec and understanding how each scope behaves is mandatory.
Good Luck.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3906030#3906030
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3906030
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42 plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user