[JAVASERVERFACES_SPEC_PUBLIC-57] Converters - Tied into PropertyResolver (EL) Created: 11/Nov/04  Updated: 01/Aug/14  Resolved: 24/Nov/09

Status: Closed
Project: javaserverfaces-spec-public
Component/s: Uncategorized
Affects Version/s: 1.2
Fix Version/s: 2.0

Type: New Feature Priority: Minor
Reporter: jhook Assignee: javaserverfowner
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issue Links:
blocks JAVASERVERFACES_SPEC_PUBLIC-205 Custom by-class converters not consid... Open
blocks JAVASERVERFACES_SPEC_PUBLIC-204 Consider the use of converters when i... Closed
Issuezilla Id: 57


I believe it would simplify things greatly if Converters were not dependent on
UIComponents in the API:

public java.lang.Object getAsObject(javax.faces.context.FacesContext context,
java.lang.String value)

public java.lang.String getAsString(javax.faces.context.FacesContext context,
java.lang.Object value)

The PropertyResolver API could then allow developers to simply plug in
converters into the struts config and allow auto-resolution of specialized
property types.

b = object we are mutating
p = property descriptor that we are setting
o = object to be assigned

if (p.type not within EL spec & p.type is not assignable from o.class) {
c = application.getConverterForType by p.type
if (c)

{ o = c.getAsObject(context, o.toString) b.p = o; }


This behavior is similar to the popular Jakarta Common's Bean Utils.

e.g. if my orderline has a Money property, just by having a type Money, if no
converter is assigned on the inputText, the PropertyResolver will auto-convert
the String input to a Money Object for that inputText's expression property.

Comment by jhook [ 11/Nov/04 ]

changed issue type

Comment by Ed Burns [ 13/Jun/05 ]

move to P4

push out to 2.0

Comment by Ed Burns [ 09/Sep/08 ]

19, 57, 63 (reason: can be done with custom component), 129
(reason: handled in facelets)

Comment by Ed Burns [ 24/Nov/09 ]

Prepare to delete "spec" subcomponent.

Comment by Manfred Riem [ 01/Aug/14 ]

Closing resolved issue out

Generated at Sat Oct 29 00:29:25 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.