Niclas Hedhman wrote:
> On Tuesday 03 August 2004 06:00, Alexis Agahi wrote:
>> /**
>> * @avalon.interceptor.type=org.tx.TxManagerComponent
>> * @avalon.interceptor.parameter=TRANSACTION_REQUIRED
>> * @avalon.interceptor.parameter=100
>
> Negative :o)
> Since it wouldn't be possible to have multiple interceptors.
Yeah agree
> First step in better direction;
>
> * @avalon.interceptor type=org.tx.TxManagerComponent
> * parameter=TRANSACTION_REQUIRED
> * parameter=100
>
> The parser will be able to make the proper grouping, compare with many
> other tags, that has multiple attributes.
You're right ;)
so I drives us to:
<type>
...
��<interceptors>
����<interceptor�method="doSomething">
<type name="org.tx.TxManagerComponent">
���� ���<parameter>TRANSACTION_REQUIRED</parameter>
��� ����<parameter>100</parameter>
</type>
����</interceptor>
��</interceptors>
...
</type>
?
> But then, how are 'parameters' distinguished by the component, really?
>
> Maybe,
> * @avalon.interceptor type=org.tx.TxManagerComponent
> * parameter=TRANSACTION_REQUIRED,true
> * parameter=MaxPoolSize,100
>
> I am not totally sure, but seems like a reasonable solution.
I'm not sure this is should be required. It helps to understand when
reading, but all in all, method's parameter are only distingushed by
position.
I was more thinking on data typing. But again, this is not really a big
issue.
--
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
