Thanks. Am already aware of overrides. In this case I do not know the specific field names. I want to map property types to custom edit blocks. And I am already past beaneditform and beaneditor. I want to create a component around propertyeditor directly...
I perhaps could do something cludgy with overrides (will check) but already have customisations around beanblocksource, hence the request.
I can probably hack around this by appending my property types with some custom string like *SEARCHMODE* and then checking for this in my beanblockoverridesource, but setting a specific beanblocksource on propertyeditor would be much more elegant
Perhaps I should have raised this on the mailing list first. If I have followed the wrong protocol please let me know, but I saw this as a relatively simple and clear cut wishlist request. Regards.