[ 
https://issues.apache.org/jira/browse/EXTVAL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Werner Punz resolved EXTVAL-92.
-------------------------------

    Resolution: Fixed

I added the cache clearing code on the ext-script side, for now I hacked it in 
because I am missing framework events which will be added post 1.0 for spring 
etc...
Good enough for now, but will be cleared up. 
Ext-Val now is hopefully fully supported by Ext-Scripting.


> Ext-Script+Ext-Val Validation list changes, do not refresh while constraint 
> validation changes are refreshed
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: EXTVAL-92
>                 URL: https://issues.apache.org/jira/browse/EXTVAL-92
>             Project: MyFaces Extensions Validator
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.3
>         Environment: OSX 10.6
>            Reporter: Werner Punz
>            Priority: Minor
>
> I am currently integrating Ext-Scripting and Ext-Val, so that both frameworks 
> work together as expected.
> So far things look good, but the issue I face is that while the Constraint 
> changes are picked up following is not
>     
>     @BeanValidation.List({
>             @BeanValidation(useGroups = Default.class),
>             @BeanValidation(viewIds = "/beanValidation.xhtml", useGroups = 
> User.class),
>             @BeanValidation(viewIds = "/groupValidation02.jsp", useGroups = 
> Admin.class),
>             @BeanValidation(viewIds = "/modelValidation01.jsp", useGroups = 
> Admin.class),
>             @BeanValidation(viewIds = "/modelValidation01.jsp", useGroups = 
> Name.class,
>                     modelValidation = @ModelValidation(isActive = true))
>     })
>     private Person person = new Person();
> when I change anything in the ValidationList nothing changes, as it seems the 
> Validation list is cached overaggressively, so that on object reloads
> it is not udpated.
> There are two solutions to the problem
> a) Either provide me a cache clear callback interface which I can trigger via 
> reflection from the core (and later from my event system)
> b) Disable the cache in development mode so that no caching happens at all
> Thanks Gerhard for providing me the feedback, I am just filing this issue so 
> that it does not get lost

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to