users@glassfish.java.net

Re: _at_Named CDI Bean of a WAB is not available in a jsf page

From: Tang Yong <tangyong_at_cn.fujitsu.com>
Date: Tue, 27 Nov 2012 10:22:18 +0900

Hi sahoo, siva,

I have seen GLASSFISH-15225 and should be the same with my issue.
And I just used the same faces-config.xml to resolve the issue.

I think that we should raise the Priority of 15225 and fix it.

Thanks.
--Tang

Sahoo wrote:
> On Monday 26 November 2012 10:22 PM, Sivakumar Thyagarajan wrote:
>> Hi Tang
>> [removing the dev alias]
>>
>> On Monday 26 November 2012 11:23 AM, Tang Yong wrote:
>>> Hi sahoo, siva,
>>>
>>> I have confirmed that if I put a faces-config.xml into META-INF, then,
>>> after redeploying the WAB and accessing
>>> http://localhost:8080/module3/faces/index.xhtml, the result is right.
>>
>> What were the contents of your faces-config.xml?
>>
>>> However, I do not know why needing to put faces-config.xml in WAB scene,
>>> in common WAR scene, we need not put it.
>>
>> The weld-integration module by default enables a custom
>> faces-config.xml (through a FacesConfigProvider) that adds in Weld
>> PhaseListener and application factory. In the WAB scenario we may not
>> be doing this.
>>
>> Thanks
>> --Siva.
>>
> Siva,
>
> Your response reminded me of an earlier issue like this that both of us
> had investigated in the past.
>
> Tang,
>
> See if the work around [1] mentioned in issue GLASSFISH-15225 fixes your
> issue or not.
>
> Thanks,
> Sahoo
>
> [1]
> http://java.net/jira/browse/GLASSFISH-15225?focusedCommentId=149138&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_149138
>
>