Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Composite Type Descriptor"
(→Background) |
|||
Line 19: | Line 19: | ||
} | } | ||
</pre> | </pre> | ||
+ | |||
+ | With the default symbol resolution mechanisms in both JSF 1.1 and 1.2, the bean property called ''property'' will never be referenced because the class implements ''Map''. |
Revision as of 20:06, 2 October 2006
Background
At runtime, the EL symbol resolution supports the ability to coerce a symbol into one or more appropriate types. For example, consider the following the expression:
#{var.property}
Furthermore, suppose that var resolves to a managed bean class defined like this:
public class MyBean implements java.util.Map { ... // has a bean property called 'property' public String getProperty() { return this.name; } .... }
With the default symbol resolution mechanisms in both JSF 1.1 and 1.2, the bean property called property will never be referenced because the class implements Map.