tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vootele Rotov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TOMEE-2262) JSF managed beans not found on TomEE plume 7.1
Date Wed, 24 Oct 2018 10:31:00 GMT
Vootele Rotov created TOMEE-2262:
------------------------------------

             Summary: JSF managed beans not found on TomEE plume 7.1
                 Key: TOMEE-2262
                 URL: https://issues.apache.org/jira/browse/TOMEE-2262
             Project: TomEE
          Issue Type: Bug
    Affects Versions: 7.1.0
            Reporter: Vootele Rotov


There seems to be an issue with finding JSF managed beans when WAR containing JSF managed
beans is deployed inside EAR to {{webapps}} folder on TomEE plume 7.1.

Following project reproduces the issue:

[https://github.com/vootelerotov/tomee-jsf-managedBean-and-ejb]

Building the EAR, deploying it to {{webapps}} folder of TomEE plume 7.1 and going to {{war}}
and clicking on theĀ {{Add}} button results in
{noformat}
/calculator.xhtml @34,51 value="#{calculatorBean.x}": Target Unreachable, identifier [calculatorBean]
resolved to null. 
{noformat}

It is the example app({{jsf-managedBean-and-ejb}}) taken from TomEE repo. The only difference
is that the WAR is wrapped in EAR and is not deployed directly.

I could not reproduce this when deploying the WAR directly. Also, this did not reproduce on
TomEE plus, even when deployed inside EAR.

I understand that deploying EARs to {{apps}} folder is the suggested approach, but as the
application is deployed when placed in {{webapps}}, it seems to me that this issue is still
worth looking into.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message