Hello Neeme,
I want to use Cocoon-XSP to access jetspeed user-information.
You had done exactly the same thing - so I have some questions
concerning your implementation.
> From: "Neeme Praks" <[EMAIL PROTECTED]>
> Date: 2000-09-20 10:40:03
>...
>I have the portlet cache turned off right now (to avoid the threading
bugs)
How to turn off the portlet cache???
Can you show me the code you used for that?
Do you use Jetspeed1.2b1 or a newer CVS version?
> RE: cocoon portlets reusing bug
> From: Neeme Praks
> Subject: RE: cocoon portlets reusing bug
> Date: Thu, 07 Sep 2000 02:00:21 -0700
> well, I figured it out finally... It is "feature" is Jetspeed:
Jetspeed
> caches portlets, so when there are two threads accessing the
portlet
> simultaneously they both get reference to the same instance of a
portlet (or
> at least same RunData). When I commented out the caching part,
everything
> works fine. This caching is ok for portlets that have the same
data for all
> the portlets, but doesn't work in the case of "personalized"
portlets.
So if you turn off portlet caching, there is no thread-problem with
cocoon-XSP-portlets any more? Even if the RunData is still shared by the
two threads?
Thanks in advance!
Johannes
�y� �杶�m������j����+��ګ����r��z7����v���p��"�h��(�:.�˛���m��^y� ~X��
+�)�v�,r����b���ӭ�����f�r�^j)���.��&�X�^y�롹^���
+�)�v�,r�
