Converters are for "bound" properties - you read and write them back. The example you've given needs no converter.
Converters are for "bound" properties - you read and write them back. The example you've given needs no converter. All you've got to do is write in your SeasonHome bean a method: public String getSeasonDescription() { return "Season " + id + "/" + new Integer(id + 1).toString().
Substring(2); } and then use it in your XHTML: ...
We have also built some custom converters. And we found that they can be called quite nicely if you add another simple format() method to the converter like this. @Name("myConverter") @Converter(forClass = XXX.
Class) @BypassInterceptors public class MyConverter implements javax.faces.convert. Converter { /* standard asObject/asString methods skipped */ public String format(XXX value) { return this. GetAsString(null, null, value); } Then we call this converter by it's bean name to format a value: I don't know if you need the FacesContext in your converter, but it shouldn't be a problem to get the instance when you need it.
Best regards, Alexander.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.