此内容没有您所选择的语言版本。

17.5. Create a Custom Auditor

Prerequisities

CDI Runtime

Annotate your auditor implementations with @Named in order to have Camel recognize them.

Note

The Camel Exchange Bus looks for bean definitions with the @Audit annotation.

Here is code that shows what a very simple auditor would look like:

                
@Audit
@Named("custom auditor")
public class SimpleAuditor implements Auditor {
 
    @Override
    public void beforeCall(Processors processor, Exchange exchange) {
        System.out.println("Before " + processor.name());
    }
 
    @Override
    public void afterCall(Processors processor, Exchange exchange) {
        System.out.println("After " + processor.name());
    }
 
}

                
@Audit
@Named("custom auditor")
public class SimpleAuditor implements Auditor {
 
    @Override
    public void beforeCall(Processors processor, Exchange exchange) {
        System.out.println("Before " + processor.name());
    }
 
    @Override
    public void afterCall(Processors processor, Exchange exchange) {
        System.out.println("After " + processor.name());
    }
 
}

Copy to Clipboard

Toggle word wrap

Important

Be aware that the afterCall method is not called if the step it surrounds throws an exception. If this happens, afterCall will be skipped.

Result

You can see many statements like 'Before DOMAIN_HANDLERS' and 'Before ADDRESSING' appearing in the server console. This is because every step of mediation is surrounded by this SimpleAuditor class.

返回顶部

此内容没有您所选择的语言版本。

17.5. Create a Custom Auditor

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links