Like most of you, there are plenty of places in my backend beans where I grab an identifying value from the request and use it to get an object/resultSet from the ORM/JDBC. I prefer to put this code in a Converter but I just can't see how to do this when a user navigates from one view to another (user clicks on an item in a list of Customers, goes to a form for just that Customer).
Usually Converters are "marketed" as a part of the "Apply Request Values" phase. Perhaps there is something wrong w/ my eyes, but I don't see why they cannot be created in the backing bean as well. After all, there are some use cases where validation and messaging are more convenient from the backing bean.
Do any of you see any risks w/ this approach? before I start doing it all over my project ;-)
Dennis Byrne
- Instantiating Conveters in Backing Beans Dennis_Byrne
- Re: Instantiating Conveters in Backing Beans Craig McClanahan
- Re: Instantiating Conveters in Backing Beans Dennis_Byrne
