Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4427A3D8.4040209@anyware-tech.com>
Date: Mon, 27 Mar 2006 10:35:36 +0200
From: Philippe Gassmann <philippe.gassmann@anyware-tech.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051117)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: CForms and Portlets - making form ids dynamic
References: <44266347.4060901@apache.org> <4426AEB4.60207@apache.org>
 <442799D3.6090302@apache.org> <44279FE6.9050300@apache.org>
In-Reply-To: <44279FE6.9050300@apache.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Sylvain Wallez a �crit :

>Carsten Ziegeler wrote:
>  
>
>>Sylvain Wallez schrieb:
>>  
>>    
>>
>
>  
>
>>>What about simply adding Form.setId(String formId)?
>>>    
>>>      
>>>
>>Yes, that was my first thought as well - but I was wondering if it's a
>>good idea to "always"
>>allow to change the id. So I thought that if the id is dynamic, it
>>should be part of the constructor - therefore the above changes.
>>
>>But of course just adding setId() works fine as well.
>>  
>>    
>>
>
>It seems to me that the form writer should not have to care about
>setting a dynamic ID on the form, as it's more an integration concern (a
>form could run equally well standalone or within the portal).
>
>Is there a simple test that can be performed (without introducing a
>dependency on the portal block) that can allow us to detect that we're
>running as a coplet and then set a dynamic ID on the form?
>
>  
>
Yes, it is possible to test if an entry "cocoon-portal-copletId"  is in 
the objectModel.

>Sylvain
>
>  
>


-- 
Philippe GASSMANN
Solutions & Technologies
ANYWARE TECHNOLOGIES
Tel : +33 (0)5 61 00 52 90
Fax : +33 (0)5 61 00 51 46
http://www.anyware-tech.com/