-
New Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
The current ZKCDI solution has some issues with standard EE 6 containers like Glassfish 3.1 or JBoss because it depends on a specific Weld implementation. CDI bekomes more and more a very important feature in business IT projects and should be part of ZK CE.
I have the following extension stages in mind:
1. Must have: Full support of CDI dependency injection. @Inject, @EJB, qualifiers. This might be as simple as hook in injection with BeanManager when a new Component or Composer instance is created by ZK... as shown in: https://github.com/oberinspector/zkdemo/blob/master/zkdemo-basics/src/main/java/net/empego/zkbasics/util/ZKCDIUtil.java
2. Should: Support of ZK specific scopes: @DesctopScoped, @PageScoped, @IdSpaceScopes, @ComponentScoped and @ExecutionScoped. To have managed beans related to ZK specific scopes.
3. Should: Provide a variable resolver to access managed beans in ZUL.
4. Nice to have: connect ZK events to the CDI event bus zu call backend/EJB methods on ZK events.
5. Nice to have: inject ZK components by ID in composers or other components (own high level components with business logik)
I can provide some code of my own ZKCDI extension in github which supports all of this features. But this... hasn't been updated for a long time, depends on a specific ZK version, is not well integrated in ZK (needs own composer and component base classes to perform injection)...
regards,
thomas