I should also mentioned that I added logging for javax.faces, but no new logs were produced by the NumberConverter.
I understand the correlation vs. causation issue, so I know that just because the NumberConverter's present when the pageflow fails doesn't mean it is causing it to fail. Still, I am baffled as to what the issue might be.
I am just about at my wit's end. Any insight is truly appreciated.
Well, it may be that it is an issue of NumberConverter not working with BigDecimal, which is the type of the amount property shown above.
Has anyone else run into issues with this?
I tested that when I change the component value from BigDecimal to merely double, everything works. At least I now know what the issue is.
I am now creating my own converter, which is a fairly simple matter. However, I am having trouble finding any literature on a very simple thing--passing parameters to my custom converter.
So while I can do this:
<f:convertNumber minFractionDigits="2" maxFractionDigits="2"/>
I can't do something like this:
<f:converter converterId="bigDecimalCurrencyConverter"> <f:param name="minFractionDigits" value="2"/> <f:param name="maxFractionDigits" value="2"/> </f:converter>
I know at this point this has become a JSF question. (Then again, I think the failure of the standard converter causing the pageflow to stall might be interesting to some.) But I am hoping the JSF experts here know this one since it seems fairly trivial, which makes the lack of resources on the topic so surprising.