Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: mako_dev; Suggested Target Milestone : Dev


Description:
DESCRIPTION OF PROBLEM
--------------------------------
After creating a page, I decided to externalize the text prompts to a resource
bundle. I create the bundle and enter the key/value pairs. If I go back to the
page and attempt to change the text property of a lable to 'use binding' and
enter a value like: 
#{msgs['homeolduser']}
When I select the "OK" button, it does not save this value. Instead, the old
text prompt is still there. If I go into the JSP source mode and make the
change, it sticks and the web app behaves appropriately upon deployment.
ERROR MESSAGES
----------------------
None
STEPS TO DUPLICATE
-------------------------
Create a page with a static text lable. Enter some text for the text property,
i.e. "Enter Password:".
Create a new properties bundle, input a key/value for this text string.
Drop a loadBundle component on the page, and establish a variable (i.e. "msgs"). 
Try to change the text property to bind to the bundle.
I do not see the bundle in the list of items to bind to on the tab - should I?
In any even, if I enter a binding that is appropriate, i.e.:
#{msgs['homeolduser']}
When I click OK this is not saved - the old text prompt is saved instead.
WORKAROUNDS
-------------------
Go into the JSP source editor, and change the reference of the text property to
properly reference the appropriate key in the bundle.

Evaluation:
There are two problems:

One, we have no design-time support for the JSF loadBundle tag, which means
messages in bundle files cannot be located by the design time property resolver.

Two, the new ValueBindingPropertyEditor attempts always to show the value of a
property binding in the properties sheet. Since this is null, it shows blank.

Workaround:
Any workaround found by the tester is in the Description field.