Hi!
>> What if we create a FrameworkAdapterFilter to setup the stuff required
>> for the FrameworkAdapter itself. It makes things cleaner, no?
>> Though, then we have yet another configuration option ... :-(
>> Maybe we can call the FrameworkAdapterFilter from the
>> OrchestraServletFilter so that one has to configure the
>> FrameworkAdapterFilter only in special cases.
>>
>> What do you think?
>>     
>
> So you mean create a separate FrameworkAdapterFilter, then in
> OrchestraServletFilter, have
>
>   private FrameworkAdapterFilter subfilter = 
>     new FrameworkAdapterFilter();
>   
Exactly! ... committed :-)


Ciao,
Mario

Reply via email to