[
https://issues.apache.org/jira/browse/DELTASPIKE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561110#comment-14561110
]
Gerhard Petracek commented on DELTASPIKE-912:
---------------------------------------------
if you just have one webapp in your ear-file, it should work.
if it fails as well, please check how you added the ds-jars (and file an issue
for the server you are using if you package them in WEB-INF/lib and it doesn't
work)
> Custom JsfModuleConfig not working in EAR
> -----------------------------------------
>
> Key: DELTASPIKE-912
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-912
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.2.1, 1.3.0, 1.4.0
> Environment: Wildfly 8.2
> Reporter: Akhbar Falafel
>
> I have created a custom implementation of JsfModuleConfig so that I can
> override the behavior in getDefaultWindowMode(). I followed the instructions
> found here: http://deltaspike.apache.org/documentation/jsf.html.
> My code looks like this...
> @Specializes
> public class CustomJsfModuleConfig extends JsfModuleConfig {
>
> @Override
> public ClientWindowRenderMode getDefaultWindowMode() {
> ...snip...
> }
> }
> I am able to make use of this code when deploying my app as a WAR file with
> no problem. However, if my app is packaged as an EAR, I see the following
> errors:
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
> dependencies for type JsfModuleConfig with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.jsfModuleConfig
> at
> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.jsfModuleConfig(DefaultClientWindow.java:0)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:372)
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:293)
> at
> org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:167)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:531)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> I realize that DeltaSpike has some "issues" when it comes to EAR files. Is
> there no way around this error, however? Can I leverage
> apache-deltaspike.properties? Anything?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
