|
From: Seth L. <set...@gm...> - 2004-07-19 18:28:30
|
> I'm a bit unsure how copying macro definitions to app resource locations > works in practice: presumably we can only do this once to avoid > overwriting customizations made by the user? How would we manage updates > made to the macros inside spring.jar in future releases? It just sounds a > bit kludgy to me, but I'm probably missing an obvious benefit. > > In my experience, the standard macros briefly outlined would be more > useful - I guess if a user really wanted to completely customize the > macro set, s/he could manually take a copy from the Spring source and do > so, but I'm definitely open to opinions here. Some guidance here would be helpful. I'm also unsure how this is supposed to work. I agree with Darren that if the user needs something unconventional, it should be easy to generate their own tags. These convenience tags are so simple and so straight forward that they should work for most people (especially if they allow XHTML or HTML rendering). Now that the nestedPath tag exists, I can submit our JSP 2.0 tagfiles for the form elements. I will also try to submit tag classes, for those not using JSP 2.0. Again, since the BindTag still exists, we're not forcing people to use these tags just to get at variables. Seth |