myfaces extval 2 and icefaces 2

today i had a quick look at the first version of icefaces 2. it looks really nice. so i added extval to the component demo project.

i tested simple constraints as well as cross-validation (cross-component-validation/inter component validation). both worked quite nice also with ajax enabled input components.

also new extval features like severity aware validation (e.g. non-blocking warn mode) work quite well.

i'm looking forward to seeing the final version!

the upgrade of the demo (with extval) was done quite fast:

just adding the jar files and using the constraints!

in this case i used the following maven dependencies for extval:

groupId: org.apache.myfaces.extensions.validator

artifactId: myfaces-extval-core

version: 2.0.3-SNAPSHOT

groupId: org.apache.myfaces.extensions.validator.validation-modules

artifactId: myfaces-extval-property-validation

version: 2.0.3-SNAPSHOT

currently we also need (we will see if we need it with the final version as well)

groupId: org.apache.myfaces.extensions.validator.component-support-modules

artifactId: myfaces-extval-generic-support

version: 2.0.3-SNAPSHOT

for sure also the myfaces extval support for jsr 303 works out-of-the-box after adding the needed jar files...

myfaces-extval and icefaces - 2

this is an update of the original post:

1)
extval and icefaces uses similar approaches to implement an internal mechanism. with mojarra there is no issue (by chance). in combination with myfaces-core there was an issue which is fixed with the following combination: icefaces 1.8.2 (see ) and an icefaces support module.

2)
internally icefaces components use some jsf 1.1 mechanisms. that's the reason why you have to use the described fallback. that will change with icefaces 2.0 (which will be compatible with jsf 1.2).
if you are using the support module + the current extval-snapshot + the upcoming version of icefaces (1.8.2 - or a pached version of 1.8.1), you don't have to follow the instructions of the original post. you just have to add the dependencies and everything will work as expected.

a very simple example is available here

myfaces-extval and icefaces

i did some quick tests with icefaces and extval.

behind the scenes icefaces does some tricks.
so it's required to deactivate 2 extval mechanisms. with this workaround a hello world icesfaces started working with myfaces extval.

#1: deactivate the extval el-resolver via web.xml context-parameter:

org.apache.myfaces.extensions.validator.DEACTIVATE_EL_RESOLVER
true


#2 switch or deactivate the default renderer proxy implementation via a extval-startup-listener.
deactivate it via:
...
protected void init()
{
ExtValContext.getContext().addGlobalProperty(ExtValRendererProxy.KEY, null);
}
...

i haven't tried more complex applications. you are welcome to try it out :)
if you find some issues please report them.