In one project we use many generic components and use the parameters of
type class alot - currenty I find there is no "good way" of passing a
class as parameter. The best I know is delegate to a method on the
component which look like:
<binding name="name" value="fooClass"/>
getFooClass() { return Foo.class };
because this is "refactoring-safe"...
but the application is full of such bindings, and its really
intimidating...
Cheers,
Ron
Howard Lewis Ship wrote:
> Interesting idea with the caveat that it can not be fully validated at
> compile time (all of the extra attributes will need to have default values
> ... oh and for primtives, its very hard to distinguish a default value
> for a
> provided value).
>
> On 12/19/06, Ron Piterman <[EMAIL PROTECTED]> wrote:
>>
>> Continueing the @Bindings annotation discussion above,
>> it just accured to me: a real profit of a
>> @Binding annotation could be something like:
>>
>> @Binding(name="name",number=5)
>>
>> or
>>
>> @Binding(name="name",bool=true)
>>
>> or
>>
>> @Binding(name="name",type=Object.class)
>>
>> or
>>
>> @Binding(name="name",string="some string")
>>
>> or finally,
>>
>> @Binding(name="name",expression="listener:somelistener")
>>
>> where only expression is evaluated as bindings values are evaluate
>> nowadays.
>>
>> Cheers,
>> Ron
>>
>>
>> ---------------------------------------------------------------------
>> 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]
