Thank you for the response. After more investigation, and looking over the
WSRP specification, it appears that the remote portlet producer is
responsible for maintaining a users session with a portlet. The particular
producer i am using is from ibm, and it seems that its interpretation (or
maybe
Sorry I can't be of much help, as I have never tried a scenario like
this. I assume this happens because the WSRP-container request and the
servlet request acts as two different "clients". I did find an
interesting thread [1] that's not really the same as your problem, but
might contain some intere
2 matches
Mail list logo
