<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spring on A Curious Coder</title>
    <link>http://acuriouscoder.net/tag/spring/</link>
    <description>Recent content in Spring on A Curious Coder</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 May 2018 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://acuriouscoder.net/tag/spring/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Spring Webflux Functional Based</title>
      <link>http://acuriouscoder.net/spring-webflux-functional-based/</link>
      <pubDate>Tue, 29 May 2018 00:00:00 +0000</pubDate>
      
      <guid>http://acuriouscoder.net/spring-webflux-functional-based/</guid>
      <description>In my previous blog about WebFlux &amp;lsquo;Spring WebFlux annotation based&amp;rsquo;, I discussed the annotation based reactive programming model for Spring WebFlux. In this blog I will use the example project introduced then and adapt it to the functional programming model.
The example project we have serves the names of planets in our solar system, optionally applying a filter, in plain text. Using curl on the running application gives:
$ curl http://localhost:8080/planets Mercury Venus Earth Mars Jupiter Saturn Uranus Neptune$ curl http://localhost:8080/planets/e Mercury Venus Earth Jupiter Neptune The Spring WebFlux annotation based controller we are adapting looks like this:</description>
    </item>
    
    <item>
      <title>Kubernetes &amp; Logging</title>
      <link>http://acuriouscoder.net/kubernetes-logging/</link>
      <pubDate>Wed, 04 Apr 2018 00:00:00 +0000</pubDate>
      
      <guid>http://acuriouscoder.net/kubernetes-logging/</guid>
      <description>When you are running services in a Kubernetes cluster they are probably writing log statements that contain all sorts of useful information you need to have look at now and then. Being the good developer you behaved and made sure all logging statements are written to the console. This gives you the possibility to use kubectl logs -f &amp;lt;pod-name&amp;gt; -c &amp;lt;container&amp;gt; to tail the logs of a specific pod and container.</description>
    </item>
    
    <item>
      <title>Optional Path Variables in Spring Mvc</title>
      <link>http://acuriouscoder.net/optional-path-variables-in-spring-mvc/</link>
      <pubDate>Thu, 28 Dec 2017 00:00:00 +0000</pubDate>
      
      <guid>http://acuriouscoder.net/optional-path-variables-in-spring-mvc/</guid>
      <description>Sometimes you run into something that makes you think twice. While programming a Spring MVC controller I wanted to have an optional path parameter. It is possible just not as obvious as you would expect.
Let&amp;rsquo;s assume we have a controller that serves persons based on a substring and all persons if you specify no substring at all. A straightforward way of implementing the controller could be something like:
@RestController @AllArgsConstructor public class PersonController { private PersonRepository personRepository; @RequestMapping(path = &amp;#34;/persons/{substring}&amp;#34;) public List&amp;lt;Person&amp;gt; getMatchingPersons(@PathVariable(name = &amp;#34;substring&amp;#34;) String substring) { return personRepository.</description>
    </item>
    
    <item>
      <title>Spring WebFlux Annotation Based</title>
      <link>http://acuriouscoder.net/spring-webflux-annotation-based/</link>
      <pubDate>Wed, 10 May 2017 00:00:00 +0000</pubDate>
      
      <guid>http://acuriouscoder.net/spring-webflux-annotation-based/</guid>
      <description>The release of Spring Framework version 5 is just around the corner and it contains a lot of new features. One of those is the WebFlux framework. It adds support for reactive web programming on client and server side. Spring WebFlux uses Reactor to make it all possible. The server side supports two programming models:
 Annotation based, using @Controller annotations. Functional, using Java 8 lambdas for routing and request handling.</description>
    </item>
    
  </channel>
</rss>