[jsr-314-open-mirror] [jsr-314-open] Attribute and State Management in Custom ClientBehaviors

[Cagatay Civici]

Sure, I'll check the spec issues today and file one if necessary.

I'd be happy to use a getStateHelper() from ClientBehaviorBase :)

Regards,

Cagatay

On Aug 4, 2010, at 8:32 AM, Martin Marinschek wrote:

> Hey guys,
> 
> +1 from me - I have long back felt the need for support for this in
> converters and validators; so of course, client behaviours should have
> it as well.
> 
> Catagay, can you check the issues, and if there is none open, open one?
> 
> best regards,
> 
> Martin
> 
> On 8/3/10, Andy Schwartz <andy.schwartz at oracle.com> wrote:
>> Hey Cagatay -
>> 
>> Yes, this is definitely a problem.  Ideally we should have generic
>> support for both:
>> 
>> - ValueExpression-based attributes and...
>> - State saving (including partial state saving)
>> 
>> Across components, behaviors, converters and validators.
>> 
>> In Trinidad-land we solve this problem by reusing FacesBean across these
>> various types of objects (ie. FacesBean is not component-specific).  We
>> should take a look to see whether we can do something similar with
>> StateHelper.
>> 
>> Andy
>> 
>> On 8/3/10 9:26 AM, Cagatay Civici wrote:
>>> Hi,
>>> 
>>> When working on a custom client behavior implementation, I've noticed that
>>> there is no state helper that we have for UIComponent.
>>> 
>>> Also checked implementation of AjaxBehavior in mojarra&myfaces and there
>>> seems to be a lot of private implementation of state management, evals,
>>> handling of valueexpressions.
>>> 
>>> So my question is do I miss something because it doesn't seem to be
>>> trivial process to create a clientbehavior properly with attributes and
>>> handle state management.
>>> 
>>> Thanks,
>>> 
>>> Cagatay
>> 
>> 
> 
> 
> -- 
> 
> http://www.irian.at
> 
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
> 
> Professional Support for Apache MyFaces