[
https://issues.apache.org/jira/browse/DELTASPIKE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285479#comment-14285479
]
Ron Smeral commented on DELTASPIKE-819:
---------------------------------------
>From the EAP point of view: this seems to be related:
>https://issues.jboss.org/browse/WFLY-3779 . There was an issue in WF/EAP Weld
>integration code, where it's not possible to create proxies of beans which
>reside in static modules and *have a package-private no-arg constructor*. I
>assume this must be the case in some DeltaSpike beans, is that true,
>[~gpetracek]?
Take a look at the Bugzillas in the mentioned JIRA, the problem pertains to
JBoss EAP 6.3.0 as well.
Look at https://github.com/wildfly/wildfly/pull/6644/files to see how this is
resolved in wildfly. The solution is similar for EAP.
> ViewConfigExtension produces IllegalProductException: Cannot return null from
> a non-dependent producer method on JBoss EAP 6.3
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-819
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-819
> Project: DeltaSpike
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: JBoss EAP 6.3 + DeltaSpike 1.0.0 (also tried 1.2.1) +
> JSF 2.1 + CDI
> Reporter: Martin E.
> Assignee: Gerhard Petracek
> Priority: Minor
> Attachments: ReproducerDemo.zip, jboss-modules-deltaspike.zip
>
>
> The Deployment of the app looks good, but on usage i get these error:
> The portlet threw an exception:
> org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return
> null from a non-dependent producer method: [method] @Produces
> @ApplicationScoped public
> org.apache.deltaspike.jsf.impl.config.view.ViewConfigResolverProducer.createViewConfigResolver()
> I have already tried to deactivate the ViewConfigExtension by Implementing
> ClassDeactivator, because i don't need it for now.
> But with no luck, i still get the same Exception.
> What elese could i do, to get rid of the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
