Interface JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder

  • All Superinterfaces:
    org.apache.camel.builder.EndpointConsumerBuilder, org.apache.camel.EndpointConsumerResolver
    Enclosing interface:
    JettyHttpEndpointBuilderFactory

    public static interface JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder
    extends org.apache.camel.builder.EndpointConsumerBuilder
    Advanced builder for endpoint for the Jetty component.
    • Method Detail

      • eagerCheckContentAvailable

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder eagerCheckContentAvailable​(boolean eagerCheckContentAvailable)
        Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data. The option is a: boolean type. Default: false Group: consumer (advanced)
      • eagerCheckContentAvailable

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder eagerCheckContentAvailable​(String eagerCheckContentAvailable)
        Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data. The option will be converted to a boolean type. Default: false Group: consumer (advanced)
      • exceptionHandler

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder exceptionHandler​(org.apache.camel.spi.ExceptionHandler exceptionHandler)
        To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. The option is a: org.apache.camel.spi.ExceptionHandler type. Group: consumer (advanced)
      • exceptionHandler

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder exceptionHandler​(String exceptionHandler)
        To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. The option will be converted to a org.apache.camel.spi.ExceptionHandler type. Group: consumer (advanced)
      • filterInitParameters

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder filterInitParameters​(String key,
                                                                                                      Object value)
        Configuration of the filter init parameters. These parameters will be applied to the filter list before starting the jetty server. The option is a: java.util.Map<java.lang.String, java.lang.String> type. The option is multivalued, and you can use the filterInitParameters(String, Object) method to add a value (call the method multiple times to set more values). Group: consumer (advanced)
      • filterInitParameters

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder filterInitParameters​(Map values)
        Configuration of the filter init parameters. These parameters will be applied to the filter list before starting the jetty server. The option is a: java.util.Map<java.lang.String, java.lang.String> type. The option is multivalued, and you can use the filterInitParameters(String, Object) method to add a value (call the method multiple times to set more values). Group: consumer (advanced)
      • filters

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder filters​(String filters)
        Allows using a custom filters which is putted into a list and can be find in the Registry. Multiple values can be separated by comma. The option will be converted to a java.util.List<javax.servlet.Filter> type. Group: consumer (advanced)
      • handlers

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder handlers​(List<Object> handlers)
        Specifies a comma-delimited set of Handler instances to lookup in your Registry. These handlers are added to the Jetty servlet context (for example, to add security). Important: You can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. The option is a: java.util.List<org.eclipse.jetty.server.Handler> type. Group: consumer (advanced)
      • handlers

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder handlers​(String handlers)
        Specifies a comma-delimited set of Handler instances to lookup in your Registry. These handlers are added to the Jetty servlet context (for example, to add security). Important: You can not use different handlers with different Jetty endpoints using the same port number. The handlers is associated to the port number. If you need different handlers, then use different port numbers. The option will be converted to a java.util.List<org.eclipse.jetty.server.Handler> type. Group: consumer (advanced)
      • mapHttpMessageBody

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageBody​(boolean mapHttpMessageBody)
        If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping. The option is a: boolean type. Default: true Group: advanced
      • mapHttpMessageBody

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageBody​(String mapHttpMessageBody)
        If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping. The option will be converted to a boolean type. Default: true Group: advanced
      • mapHttpMessageFormUrlEncodedBody

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageFormUrlEncodedBody​(boolean mapHttpMessageFormUrlEncodedBody)
        If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping. The option is a: boolean type. Default: true Group: advanced
      • mapHttpMessageFormUrlEncodedBody

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageFormUrlEncodedBody​(String mapHttpMessageFormUrlEncodedBody)
        If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping. The option will be converted to a boolean type. Default: true Group: advanced
      • mapHttpMessageHeaders

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageHeaders​(boolean mapHttpMessageHeaders)
        If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping. The option is a: boolean type. Default: true Group: advanced
      • mapHttpMessageHeaders

        default JettyHttpEndpointBuilderFactory.AdvancedJettyHttpEndpointBuilder mapHttpMessageHeaders​(String mapHttpMessageHeaders)
        If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping. The option will be converted to a boolean type. Default: true Group: advanced