Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of general.equal.700@gmail.com
 designates 209.85.221.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:x-mailer:mime-version:subject:date
         :references;
        b=XJ3e2O+W9qv6B8T6vSkobG30wEhul2Iu8aly983uX0RmXjJDq0eMnKRSMRhkQnGssZ
         mgMZR+rrjtR30/8683LGwnzL8C8xN+3+ATSw1XTvEQvkLD00q3gqpNXhBtm3qweN9Ngr
         6jNjJG/Eo0kneOAZ6gKQz3kca1BivuDOPniNQ=
Message-Id: <A27FB042-8FF8-49A8-82FF-8E1C18D7B83E@gmail.com>
From: Omar Elprince <general.equal.700@gmail.com>
To: MyFaces Discussion <users@myfaces.apache.org>
In-Reply-To: <52A646452EB3AB40B87EB3F2BA17342E05B249D8@gzs-msx-3.gzs.de>
Content-Type: text/plain;
	charset=utf-8;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPhone Mail 7A400)
Subject: Re: AW: [Trinidad] How to use an iterator,
 selectOneChoice and  partialTriggers?
Date: Wed, 9 Sep 2009 10:45:07 -0400
References: <52A646452EB3AB40B87EB3F2BA17342E05B249D8@gzs-msx-3.gzs.de>

Use immediate=3D"true"

--Omar

On Sep 9, 2009, at 8:24 AM, "Roeder, Andreas" =
<Andreas.Roeder@firstdata.de=20
 > wrote:

> Thanx a lot, that worked like a glue. Just one problem is left: all =20=

> the selectOneChoice components are on required=3D"true". How can I =20
> avoid the validation?
>
> I already tried to call at the end of the ValueChangeListener the =20
> call:
>
>    FacesContext.getCurrentInstance().renderResponse();
>
> but no success.
>
> -Andreas
>
> -----Urspr=C3=BCngliche Nachricht-----
> Von: Andrew Robinson [mailto:andrew.rw.robinson@gmail.com]
> Gesendet: Montag, 7. September 2009 02:46
> An: MyFaces Discussion
> Betreff: Re: [Trinidad] How to use an iterator, selectOneChoice and =20=

> partialTriggers?
>
>
> If you give partial triggers an EL expression it must evaluate to =20
> type String[]. The value change listener is fired for the current =20
> iteration, so if you click item 3, the event will be broadcast for =20
> the selectOneChoice inside the index 2 of tr:iterator. To move the =20
> iterator to a new index you need to save the current row index, set =20=

> the new index, evaluate code and then set it back.
>
> An iterator stamps out one component and a component only has 1 ID, =20=

> so you cannot put EL in the ID like you did below. I would advise =20
> using <f:attribute/> if you need to store the ID on the component, =20
> but just give the choice a static ID.
>
> The resulting IDs on the client will be like "i1:0:soc1", =20
> "i1:1:soc1", etc if your iterator had ID "i1" and your =20
> selectOneChoice had ID "soc1". So the :#: in between represents the =20=

> stamp index.
>
> -Andrew
>
> On Fri, Sep 4, 2009 at 7:32 AM, Roeder, =
Andreas<Andreas.Roeder@firstdata.de=20
> > wrote:
>> I'm trying to create generic selectOneChoice elements. When the first
>> selectOneChoice value changes it should update the next one in the
>> list and so on. I tried to do that via the id, partialTriggers and a
>> ValueChangeListener:
>>
>> <tr:iterator value=3D"#{genericFormBean.formDesc.fieldList}"
>>                                var=3D"field">
>>  <tr:selectOneChoice
>>        id=3D"#{field.id}"
>>        partialTriggers=3D"#{field.partialTriggers}"
>>        valueChangeListener=3D"#{genericFormBean.valueChange}"
>>        value=3D"#{genericFormBean.formDesc.modelMap[field.id]}"
>>        <f:selectItems
>>
>> value=3D"#{genericFormBean.selectItemMap[field.itemList]}" />
>>  </tr:selectOneChoice>
>> <tr:iterator>
>>
>> But I cannot set the id of the selectOneChoice element. When I try to
>> get the other selectOneChoice elements in the valueChangeListener I
>> just see one element in the iterator.childs() collection. Why is =20
>> that?
>>
>> I also tried to use a custom renderer to set the id, but as soon I
>> change the id of one selectOneChoice element all other elements are
>> getting the same id. It's pretty confusing to me.
>>
>> Is there another way to do that?
>>
>> Best Regards,
>>
>> Andreas
>>
>>
>