Support for OmniFaces @ViewScoped

[BalusC]

Support for OmniFaces @ViewScoped

[BalusC]

I went for a different approach: https://balusc.omnifaces.org/2023/11/using-omnifaces-cdi-viewscoped-with.html

[larsgrefer]

The first and most important step would be to implement the org.springframework.beans.factory.config.Scope interface in order to give Spring access to the OmniFaces ViewScope. Our Implementation for the "normal" ViewScope can be found here: https://github.com/joinfaces/joinfaces/blob/4.7.x/joinfaces-autoconfigure/src/main/java/org/joinfaces/autoconfigure/viewscope/ViewScope.java

After this, a bit of plumbing is needed to get it to work:

The new Scope Implementation needs to be registered with the Spring ApplicationContext. We do this here: https://github.com/joinfaces/joinfaces/blob/4.7.x/joinfaces-autoconfigure/src/main/java/org/joinfaces/autoconfigure/viewscope/ViewScopeAutoConfiguration.java

With these two steps, the new Scope could be used with the @org.springframework.context.annotation.Scope("omnifaces-view") annotation. (Or whatever name you have chosen for the scope)

In order to support @org.omnifaces.cdi.ViewScoped as marker-annotation as well, you can define a CustomScopeAnnotationConfigurer as we do here for the "normal" JSF Scope annotations: https://github.com/joinfaces/joinfaces/blob/4.7.x/joinfaces-autoconfigure/src/main/java/org/joinfaces/autoconfigure/scopemapping/JsfScopeAnnotationsAutoConfiguration.java
(This is a BeanFactoryPostProcessor which modifies the scope information in the BeanDefinitions if the bean class has a given annotation)

[BalusC]

Thank you for the response. So in other words, the OmniFaces ViewScopeManager needs to be ported to Spring in its entirety, including the unload/destroy features?

[JohannesProbst]

@BalusC we tried your approach but the cdi-extension doesn't get our @Named annotated class - so weld doesn't found them in the first place?

Can you please have a look at our example project based on the joinfaces example project? Would be a great feature for joinfaces to deliver full omnifaces capabilities :)

Here the forked example: https://github.com/JohannesProbst/joinfaces-gradle-war-example

[zeners]

@JohannesProbst it's not working inside IntelliJ.

Building a .war file and run it alone works as expected.

[zeners]

the following org.jboss.weld.environment.deployment.discovery.BeanArchiveHandler service helped out:

@Priority(Integer.MAX_VALUE)
public class IntelliJFileSystemBeanArchivHandler extends FileSystemBeanArchiveHandler {
    @Override
    public BeanArchiveBuilder handle(String path) {
        final Path target;
        try {
            target = Path.of(path);
        } catch (Exception e) {
            return null;
        }
        return super.handle(target.getParent().resolve(Path.of("classes")).toString());
    }
}

[JohannesProbst]

@zeners Thx - you are right - it was the different places of binaries and resources while running it in intellij! Your ArchiveHandler helped.