Simplify input route implementation

[pjuza]

Simplify and offer more productivity for often and common task when input route is implemented.

Focus on the most often use cases during input routes implementation:

• direct/spring-ws URI
• one route = one message
• 0-N validators for input routes
• optional: object ID, funnel value
• garanteed order
• throttling

[pjuza]

Try to use declarative approach with annotations:

@Async
public class CreateCustomerAccountRoute {

    public URI getOutURI() {
        return BillingAccountRoutes.URI_CREATE_CUSTOMER_ACCOUNT;
    }

   @Validator
   public Processor validateMandatoryFields() {
   }
}

@Async(operationName="CreateSazkaCustomer", guaranteedOrder=true)
public class CreateCustomerAccountRoute {

    @OutUri
    public String getOutURI() {
        return BillingAccountRoutes.URI_CREATE_CUSTOMER_ACCOUNT;
    }

    @Validator
    public Processor validateMandatoryFields() {
    }

    @FunnelValue
    public Expression getFunnelExpression() {
    }   

    @ObjectId
    public Expression getFunnelExpression() {
    }       
}

Main prerequisites:

• support most often scenarious, not all cases. (analogy to Spring Security configuration)
• use convention-over-configuration principle

Benefits:

• focus on implementing important parts of integration, not needed to solve boiler-code
• less error-prone
• support for unit tests
• not tighly dependant to specific protocol/service (JMS, WS, HTTP)

[pjuza]

Spring has support for reading metadat about classes and annotations:

org.springframework.core.type.classreading.SimpleMetadataReaderFactory -> org.springframework.core.type.classreading.MetadataReader
org.springframework.context.annotation.ConfigurationClassUtils#isLiteConfigurationCandidate
org.springframework.beans.factory.config.BeanFactoryPostProcessor - cteni route bean
org.springframework.beans.factory.BeanClassLoaderAware

[pjuza]

Original issues: CLVBUS-160