I’m not totally sold on the Wizard idea (it doesn’t mean its not a good idea, I just mean personally)… wrapping the JSTL tags with wizards seems to automatically imply wrapping all other TAGS, since its not much of a stretch… when then makes me thing “would I ever use it”, no, because it would probably slow me down.
I understand your comment about normalizing across a team, but you are dealing with standardized APIs… weather we offer a template that sticks a “description” into the tag or not when its created, the user can still go in and clear it out or muck it up and its still valid according to the JSTL specs.
As far as the ‘better autocomplete’, I’m ALWAYS sold on that suggestion 🙂
Did you have any particular autocomplete in mind? One thing I have suggested to the team (we haven’t talked in depth yet) is autocomplete based on jsp:useBean and bean:define in JSP pages (of course not just the name, but honoring the types specified and including the method calls).
Also seeing completion in the struts name and property tags depending on the type of bean you are referering would be good. NetBeans has this now with std JSP tags. (3.6 beta 1)
Was there any other suggestions you had in mind?