If we all agree on using name, then I will go ahead an rollback my changes to "set" and:
* add name to "url" and deprecated "id" * add className to "bean" and deprecate "name" and (we will have to wait until next version to use name for what id is today) does that sound good? musachy On 6/14/07, David Durham, Jr. <[EMAIL PROTECTED]> wrote:
On 6/13/07, Rene Gielen <[EMAIL PROTECTED]> wrote: > I personally personally find the combination of > <s:set name="foo" value="..." /> > <s:textfield name="foo" /> > a veeery common usecase. That said, I would be quite confused to have to > write > <s:set id="foo" value="..." /> > <s:textfield name="foo" /> > instead in future. > > Anyway, thanks for setting the ticket on hold for now - maybe we manage to > get some more opinions in to bring any possible decision on that topic to > a broad base. Adding another user perspective, I agree with Rene that 'id' should be used in the XML sense of id and should be unique within a document. As I see things, an id should refer to the document element itself within it's original context. Isn't this the reason for a styleId attribute in struts 1? -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "Hey you! Would you help me to carry the stone?" Pink Floyd
