Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Example:
Say there is a method:
String getFullName()
{
return "Some full name";
}
Even without the standard member variable fullName, the expression will still evaluate correctly on the test server, but will fail on the production server.
For example, <h:outputText value="#{fooBean.fullName}"> will be evaluated correctly and display "Some full name" on the dev server.
The deployed app will throw a NullPointerException when attempting to render the specific control with the EL statement in question. In order to circumvent this behavior other libraries are needed to update the default EL support to allow regular method calling:
Example: <h:outputText value="#{fooBean.getFullName()}"> will work both locally and live if there is proper additional library support for the more recent Java EL syntax.
Operating System: Ubuntu 64 bit (Utopic)
Java SDK (AppEngineDev 1.9.11, JDK 1.7)
To reproduce the result just create a simple getter method inside a backing bean without a corresponding class member variable. Testing locally, and the method will be called correctly -- but will fail in deployment. This may be intended behavior according the the Java EE standard (getter without associated member variable?) but the dev and production server maybe should at least agree on their evaluation.
Best,
Brendan