On your first point; I'm not sure how you see url and set differing, from what I can see url is just a set that constructs the value in a specific way, so imho the two should be consistent, and so one of them needs to change.
On your second point; if name is deprecated it will still be available, it just won't be the best practice. It could be deprecated in 2.x, and removed in 3.x or whatever the next major version is, that way all documnetation referring to S2 is still valid, and if S3 ever happens it can remove the backwards compatibility baggage in favour of a consistant approach. -----Original Message----- From: Rene Gielen [mailto:[EMAIL PROTECTED] Sent: 13 June 2007 07:58 To: Struts Developers List Subject: Re: name inconsistency -1 for that from my point of view: - id in html page context refers the unique identifier on a page, whereas name lets you bind to a named target, not necessarily having to be unique on the page. set clearly references a name from that understanding (set the named property). I would find id quite misleading. - TONS of documentation resources, including third party, reference the set tag (as a WW2 / S2 / even WW1 tag). It is one of the most used tags. Once we deprecate this, this docs will have to be changed or will confuse users. Regards, Rene Musachy Barroso schrieb: > This is a really minor thing, but it gets me all the time, the set tag > uses the "name" attribute for the variable name, while the url, and > bean tags use "id", anybody against deprecating the "name" attribute > in set and using "id" > instead? > > regards > musachy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
