Hi,

In 4.0, I'm very confused because of default-binding. I always have to check 
the parameter's default-binding attribute or explicitly use a binding prefix.
Wouldn't it be better:
- if there is no binding prefix then it would be treated as "ognl" (if someone 
wants then the appropriate custom binding prefix could be used)
- default-binding would go away

I think default-binding corrupts the consistency of the clean component 
specifications!
For example if I look at the specification part

            <component ....>
                   <binding name="something" value="property" />
            </component>

then I don't know if "property" is a JavaBean property or it is the name of an 
asset or a component. To know this, I have to check the default-binding of the 
parameter.
So it makes the specification very hard to read.

What do you think?

Br,
Norbi

Reply via email to