>From: Ryan Wynn <[EMAIL PROTECTED]>
>
> On 2/13/06, Craig McClanahan wrote:
> > Interestingly, that parallels a corresponding issue with the JSP rendition
> > of JSF components in JSF 1.0/1.1 ... if you have a property set in a tag
> > attribute, AND you set it in code, which wins? For JSP pag
>On 2/13/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>>
>> >Today I upgraded to the latest nightly build (2/13) for shale-core and
>> >shale-clay. It seems my clay onchange properties are being omitted
>> >now. Not sure in which nightly they stopped working. Anyone else
>> >having this problem?
On 2/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> Interestingly, that parallels a corresponding issue with the JSP rendition
> of JSF components in JSF 1.0/1.1 ... if you have a property set in a tag
> attribute, AND you set it in code, which wins? For JSP pages, we went round
> and round
On 2/13/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> >Today I upgraded to the latest nightly build (2/13) for shale-core and
> >shale-clay. It seems my clay onchange properties are being omitted
> >now. Not sure in which nightly they stopped working. Anyone else
> >having this problem?
> >
>
>Today I upgraded to the latest nightly build (2/13) for shale-core and
>shale-clay. It seems my clay onchange properties are being omitted
>now. Not sure in which nightly they stopped working. Anyone else
>having this problem?
>
>Thanks,
>Ryan
Gary
5 matches
Mail list logo
