Spring’s FreeMarker macro’s are pretty useful, but there are a couple of things I need from the showErrors macro that simply aren’t there:
- Show errors without a HTML tag around them – if you don’t specify a classOrStyle, the showErrors macro will wrap your error message in a <b> tag. If you do, it’ll wrap it in a <span> (understandably)
- Pick the tag that surrounds each message – As explained in the first point, you can see we only get the choice of <b> or <span>. What if I wanted to use an <li>? …use the separator? – no good, because unless I write an <#if> statement to check the number of error messages before I call showErrors I’ll end up with redundant <ul>/<ol> and <li>’s in my markup if there aren’t any errors:
e.g. <ul><li><@spring.showErrors “</li><li>”/></li></ul>
Which leads me nicely onto the next point: - Show errors in an ordered/unordered list, automatically detecting zero messages and not outputting markup if this is the case
- Show errors for multiple bind paths – Spring’s showErrors only shows errors for the currently bound field. However I’ve found that I’ve needed to show errors for 2 or more fields together. This is particularly true of a DOB field where the day/month and year are separate <select>’s
- Finally, show errors for multiple bind paths, in an unordered/ordered list
You can download my Spring extensions here: springx.ftl. Inevitably I’ll find more bits and pieces to add and will update them accordingly.
We ran “near me” keyword tests and saw strong lift in our local marketing in san jose strategy. san jose local marketing agency
Useful info on daycare injury claims. Parent resources at accident attorneys .
Peer assistance can make all the difference in recovery journeys. Check out the community resources readily available at addiction treatment Gahanna .
It’s incredible how much better life ends up being after finishing an alcohol detox program! alcohol detox recreateohio.com