Hi Andrei, I would be curious to understand a bit regarding the use case(s). Is it going to be driven by presence of some headers fe? Or something else? Like f.e. each message is inspected, and depending on some criteria, the different filter chains are being constructed? Could you share a couple of examples?
Thank you. Best Regards, Andriy Redko AS> Hi, AS> Currently JAX-RS filters are bound to exchange endpoint in ClientProviderFactory and ServerProviderFactory and AS> filter chain is always the same for all processing messages. AS> In some use cases (security) it would be useful to activate filters dynamically on message level, that different requests could have own filter chains. AS> I am going to extend JAXRSInInterceptor, JAXRSOutInterceptor, ClientRequestFilterInterceptor and AS> ClientResponseFilterInterceptor with option to add and execute filters dynamically, additionally to ClientProviderFactory and ServerProviderFactory. AS> Any objections, thoughts regarding that? AS> Regards, AS> Andrei. AS> As a recipient of an email from Talend, your contact personal data will be on our systems. Please see our contacts AS> privacy notice at Talend, Inc. <https://www.talend.com/contacts-privacy-policy/>
