Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@www.apache.org Received: (qmail 76627 invoked from network); 10 Feb 2005 09:57:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Feb 2005 09:57:00 -0000 Received: (qmail 17511 invoked by uid 500); 10 Feb 2005 09:56:59 -0000 Delivered-To: apmail-jakarta-jetspeed-dev-archive@jakarta.apache.org Received: (qmail 17052 invoked by uid 500); 10 Feb 2005 09:56:57 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 17037 invoked by uid 99); 10 Feb 2005 09:56:57 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of zazo@tlen.pl designates 193.17.41.27 as permitted sender) Received: from rekin7.go2.pl (HELO rekin7.go2.pl) (193.17.41.27) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 10 Feb 2005 01:56:56 -0800 Received: from poczta.o2.pl (rekin7.go2.pl [127.0.0.1]) by rekin7.go2.pl (o2.pl Mailer 2.0.1) with ESMTP id 87EA363062 for ; Thu, 10 Feb 2005 10:56:53 +0100 (CET) From: =?iso-8859-2?Q?zazo?= To: jetspeed-dev@jakarta.apache.org Subject: =?iso-8859-2?Q?Page_rebuilding_and_caching?= Date: Thu, 10 Feb 2005 10:56:53 +0100 Content-Type: text/plain; charset="iso-8859-2"; Content-Transfer-Encoding: 8bit X-Mailer: o2.pl WebMail v5.27 X-Originator: 212.126.11.125 Message-Id: <20050210095653.87EA363062@rekin7.go2.pl> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi all, I'm trying to add to J2 some kind of security constraints at the level of a single portlet. It's supposed to be as simple as possible. To achive this goal I'm using portlet enitity's preferences. I modified a little bit PageAggregatorImpl and according to these preferences above I can decide about page structure (which portlets should be hidden to logged user). The problem is that every time I rebuild the page: 1. I get this message [org.apache.ojb.broker.core.PersistenceBrokerImpl] WARN: No running tx found, please only store in context of an PB-transaction, to avoid side-effects - e.g. when rollback of complex objects but, the portlet that I don't want to be shown, disappers. So far, so good. 2. Even after I had changed preferences in database back to their previous values (before page rebulding) the portlets that disappeared don't appear again. I belive this is somehow connected with J2 caching system. Is there any way to avoid it? Or even better, to use it the way I would like to? By 'my way' I mean situation when I have one psml file common for couple of users. Let's say it has 3 portlets in it (A,B,C). According to the user logged in page appearance is diffrent. User 1 sees only portlet A on the page, and user 2 sees A and B... I know that this problem can be solved by using different psml files for different users, but this is not the way I would like to have it. It's far more easy for my to configure to portald doing it the way I described. I belive I described my problem and what I would like to achive quite clearly. If not feel free to ask for more detailed information. I am aware that my English can be understoodble only for me ;) Sorry for pretty long post. Any help will be appreciate. Thanks! Tomasz --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org