> I have nothing against it. But...
> It will create confusion. I hate confusion.
> Some tags will allow @ejb:xyz name="123" or @ejb:xyz 123
Let's see how Microsoft handles it :-)
.Net has something like doclet, it's called attributes, they are also
supported in CLR level, not just in source code. You declare it like
this:
[MyAttribute(false, OptionalParameter = "optional data")]
MyAttribute is like @MyAttribute, the rest are parameters. The first
param is a mandatory one, you can put it there without specifying param
name. OptionalParameter is optional, you have to specify the name. The
first one is like our positional params, the second like our current
name-value format.
Thoughts:
- The (,,) format is interesting, but I personally like our
space-separated name="" format. It doesn't look like a function call.
- I don't know about you but I personally get confused with the first
param, what it is really? You don't know, or you can't remember, the
param name is not specified.
- They do not support positional param for all of them, just for
mandatory params. It's debatable whether we should support positional
params for mandatory tags.
Now, an interesting case:
> Think about the jboss:container-configuration
> @jboss:container-configuration Standard CMP Bean
> or
> @jboss:container-configuration name="Standard CMP Bean"
> If this need a second parameter we have to deprecate the first option
else
> confusion. Or make the hypothese that the first string is the first
> parameter and the rest is for configuration name. Beurk.
> Then 2 different possibilities for @ejb:permission, only one for
> jboss:container-configuration.
> Confusion...
> I propose to accept the non-named attribute tag only for ONE attribute
> tag.
> As soon as a tag has 2 or more attributes, we must use the named
attribute
> way only.
Yes, it's a bit confusing, so what about putting a "" around the value?
I mean this one is legal: @jboss:container-configuration "Standard CMP
Bean" but not without the "".
I think supporting the space-separated format, plus the "" around param
value, is a good idea for single param items, but not for multi-params.
Seeing ejb:permission "admin,tech" is as descriptive as ejb:permission
role-names="admin,tech", but this is not true for ejb:env-entry which
has multiple param and you may confuse the order.
Thoughts? We should find the optimum syntax.
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|