not an issue
not an issue
Last edited by mayank76; Nov 20th, 2007 at 05:14 PM. Reason: Not an Issue
I do not really understand your questions. The idea of PropertyEditors is to convert a value to string and back. If your record fields are only of default types you don't need to do anything with them. It might be different for the drop-down since you might need to convert a record to a string directly, not only one of its fields. In this case you can use a PropertyEditor.
Joerg
This post can contain insufficient information.
Mayank,
Can you please explain in detail. You can mention them in points perhaps and we can eventually understand your concept.![]()
This is a very common use case. You have a form-backing object which holds a list of your records. In the JSP (or template language of your choice) you iterate over the list and create the rows in the table.
Of course. You register your CustomCountryEditor for type Country.class or something like this and it works.
Joerg
This post can contain insufficient information.
I wonder if you really custom editor. What's actually the command object? commandForm or command? I'm confused by your code. Also consider using more advanced Spring's form taglib. This would reduce your code to 1 line.
Interceptor might work. The easiest solution is probably to use a lazy-initialized collection though.
Joerg
This post can contain insufficient information.