There were a lot of changes since Spark 2.5.0, so we're doing a release candidate this time. Please try it out, build your projects, test some of the new functionality, and report any bugs. Please use the 馃憤 emoji at the bottom of this post if you've tested and you didn't experience any trouble.
<dependency>
<groupId>com.sparkjava</groupId>
<artifactId>spark-core</artifactId>
<version>2.6.0.RC0</version>
</dependency>
Changes:
path() method for grouping routesafterAfter() filter (a finally-filter that runs after everything else)initExceptionHandler() for overriding default behavior if Sparks fails to startinternalServerError(), notFound() and add() (general)queryParamsOrDefault() method to RequestExceptionMappersExceptionMappers are now cleared on stop()OutOfMemoryError due to caching of chunked datacookie(), and a bug where cookies couldn't be deleted was fixedactiveThreadCount() to expose number of active threadsport() method to get current portX-Forwarded-For support in request.ip()Spark.halt() now returns HaltException instead of voidQueryParamsMap.hasKey()Unfortunately, #812 is still not resolved.
I will do more tests later :-)
Thank you for your job!
tested it out on 2 small apps, as well as one on google app engine java 8 alpha runtime. so far so good.
Updated one of my apps and everything works well.
Recently started testing against 2.6.0.RC0. Everything seems to work so far, I'll keep you posted as my testing progresses.
I am having this weird issue where my controller method gets called twice, once with the message body, and once with an empty body. As my controller then fails on the empty body the entire request handling fails. It seems something is not quite right with this release after all, but I am not sure what exactly triggers the second invocation on the request handler. I suppose its introduced in the afterAfter feature, but even if I disable the afterAfter filter that I've added, the issue still occurs. I'll keep debugging the issue but unfortunately I have to rollback too.
I'll keep debugging the issue but unfortunately I have to rollback too.
Well, that's what release candidates are for, I guess.
Please let us know when you find out.
LGTM
Did you delete the experimental Routeoverview?
Did you delete the experimental Routeoverview?
Yes.