dd #2
Open
dd #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- allows usage of TCP or UDP graphite reporter from metrics lib
…_scanning_hibernate_bundle Added support for multiple packages in Scanning Hibernate Bundle
Allow selection of `TCP` or `UDP` for Graphite Reporter
add example for Configured Bundles docs
Deal correctly with nested JAR resources
…tion-groups-v2 Allow Validated to annotate non-entity objects
Cannot stop then start appender after upgrading logback beyond 1.1.5.
* Upgrade to the latest Jackson version that correctly handle subtyping * Remove JDK7 module, because it has been merged to jackson-databind * Upgrade deprecated API * Fix the test for printing a detailed YAML parsing error See the discussion the previous update attempt in issue dropwizard#1449.
This is a bugfix release. The Release notes are here: https://github.com/eclipse/jetty.project/blob/jetty-9.3.x/VERSION.txt
Upgrade to Jackson 2.7.3
The HTTP link returns 301, which breaks maven-deploy plugin.
Use SVG badge for Travis CI
…ut providing them
…izable-httpclientbuilder Allow HttpClientBuilder subclasses to customize the underlying builder
…ine-ifs-in-taskservlet dropwizard-servlets: Combine unnecessarily nested if blocks in TaskServlet
While the improvements to TLS configuration of HTTP clients in 1.0.0 (maybe prior) are awesome, as part of that process the ability to set a custom HostnameVerifier easily on the HTTP client has been lost. You used to be able to do e.g. as: JerseyClientConfiguration myJerseyClientConfiguration = <some configuration>; HostnameVerifier verifier = new MyCustomHostnameVerifier(); JerseyClientBuilder clientBuilder = new JerseyClientBuilder(env); clientBuilder.using(myJerseyClientConfiguration).using(verifier); Client httpClient = clientBuilder.build(); Same is true for HttpClientBuilder too. You can still do it by creating a custom Apache Registry<ConnectionSocketFactory> but you need to set up socket factories for every scheme. This change restores the ability to set a custom HostnameVerifier for clients. [Fixes dropwizard#1663] (cherry picked from commit 160502f)
…ropwizard#1677) ObjectMapper-customization logic is moved from YamlConfigurationFactory to DefaultConfigurationFactoryFactory, making it easier to modify with a custom ConfigurationFactoryFactory implementation. There are some (uncommon) use cases where it's beneficial to update an application without modifying the configuration, which may fail if the application configuration has removed a configuration property. A protected configureObjectMapper method is added to DefaultConfigurationFactoryFactory to allow the configuration factory to be extended to apply (or remove) deserialization features.
…or-provider-shutdown Gracefully shut down default ExecutorService used by JerseyClientBuilder
…ng/logback-attr-map-race-condition Fix request attribute-related race condition in Logback request logging
Add ResourceCollection support ServletEnvironment
This in particular makes it possible to configure loggers (whose names frequently contain periods) with config overrides. Close dropwizard#1599
A good practice is to avoid manipulating arrays in favour of Java collections, because arrays are relatively dangerous to operate and provide a less convenient API. See Effective Java Item 25: Prefer lists to arrays.
…rray Use a List instead an array in YamlConfigurationFactory
Instead of listing supported cipher suites, protocols, etc of the default SSLContext algorithm, log what Jetty's will actually use, which as of this commit is a "TLS" SSLContext. This will also future proof the logging if this property ever becomes configurable in Dropwizard.
Document that only TLSv1.2 is enabled by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is