Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 68409 invoked by uid 500); 30 Jun 2003 11:09:13 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 68372 invoked from network); 30 Jun 2003 11:09:12 -0000 Received: from unknown (HELO insiders.de) (193.22.3.98) by daedalus.apache.org with SMTP; 30 Jun 2003 11:09:12 -0000 Received: (qmail 28798 invoked from network); 30 Jun 2003 11:08:22 -0000 Received: from kingkong40.insiders.de (HELO KINGKONG40) (193.22.3.69) by insiders.insiders.de with SMTP; 30 Jun 2003 11:08:22 -0000 From: "Holger Dewes" To: Subject: portal-fw: coplet configuration with XSP Date: Mon, 30 Jun 2003 13:09:04 +0200 Message-ID: <001f01c33ef8$04867cc0$450316c1@KINGKONG40> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Dear all, I'm currently playing around with the portal framework (2.1 M2, jdk 1.3.1, resin 2.0.4). I'm trying to create a configurable coplet. Because the basis for the configuration is dynamic, I want the configuration to be created by an XSP instead of a static XML. However, I get really weird results. Most often it does not work, because I get NullPointerExceptions (from different places, e.g. org.apache.cocoon.environment.AbstractEnvironment, line 511), or the portal simply refuses to show the content of the coplet and keeps showing the configuration (but no errors in the logs). But what's really frustrating: sometimes it works. I have been trying for the last couple of hours to create an easy example for this list that never works, but it seems impossible. Anyway, this shows basically what I'm trying to do: for(int i=3D1; i < 4; i++) { /coplet-data/valuei Valuei } This is the pipeline: This didn't work half an hour ago, now it works... right, I'm just back from lunch, now it doesn't work anymore. I tried it with Cocoon 2.0.4 and ran into the same problems (no NullPointerException yet, but also the refusal to show the content after doing the configuration). Any ideas? Are there any known problems with configuring coplets via XSP? To me, this smells like a race condition, but I have no idea how to pinpoint it. Cheers, Holger --=20 Holger Dewes