Java Spring Boot Web Scraping for Beginners

Web Scraping Dynamic Websites with Java and Selenium

Get the starter code for this tutorial:

Finance Finance and Investing Java Java For Finance Spring Boot

Getting Stock Data with Java & Spring Boot | Java For Finance

Get the code to start the project here:

Java Spring Boot

Setting Up Cucumber on Spring Boot Java Projects

Get the start files here:

Java Javascript

Learn Server Sent Events (SSE) with Java, Spring Boot & WebFlux

In this tutorial, we are going to explore and learn server sent events (SSE) with Java, Spring Boot and Javascript.

The Spring dependencies we will use for this project are Spring starter web, Spring starter webflux and Spring starter thymeleaf.

In order to follow along with this Spring Boot Server Sent Events tutorial, you will need to download the start files below. The reason for this is that there is no point adding some of the boilerplate code such as the index.html file to this tutorial. We’re better off just focusing on the our Java Spring Boot implementation of Server Sent events.

Download the start point files for this project here:

What are server sent events?

Server sent events are way of communicating with clients over HTTP. As the name suggests, this form of communication derives from the server doing the the sending of information. This is in contrast to a typical REST request/response implementation where the client would send a request to a server for information and the server would upon receiving this request would return the information requested: for example this very webpage was served to you in this way. You requested the webpage from the server and the server then returned it you. Once you have got the webpage back from the server, that’s it. It’s loaded. With server sent events however the server can still send updates, which can then be processed in your web browser leading to you seeing live updates on the page. The reason this can work is because there is a persistent connection between the client and the server.

SSE are commonly compared with Websockets, which are a two-way communication protocol. SSE however, are only one-way.

Why use server sent events?

Server sent events are an excellent choice when you have the requirement to have live updates from the server, but your client doesn’t need to return any information to the server. For example, a web app like Google Finance, would make a good use case for server sent events because the users want to get constant updates of the latest stock and financial prices that the server has, but they are not updating any of that information themselves.

Consider another example, a stock trading web app, this arguably would be better suited to a communication technology like websockets, because the users want live updating of information about financial instruments, but they also want to send information about their orders to the server. There is a two-way communication between the client and the server, which makes server sent events not the most suitable choice for this application. If server sent events was chosen for this application, then it would have to paired with something else, like standard request/response endpoints for the submitting of orders in order to get the two-way communication that the trading app requires.

The Code


import org.springframework.http.MediaType;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import reactor.core.publisher.Flux;

import java.time.Duration;
import java.util.Collections;

public class Controller
   @GetMapping(value = "/stream", produces = MediaType.TEXT_EVENT_STREAM_VALUE)
    public Flux<Point> stream()
       return Flux.interval(Duration.ofMillis(500))
               .map(interval -> Collections.singletonList(new Point()))
               .flatMapIterable(x -> x);

All this class is doing is allowing us to create random points that have latitude and longitude values within the UK.


import com.fasterxml.jackson.annotation.JsonAutoDetect;

import java.util.concurrent.ThreadLocalRandom;

@JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.ANY)
public class Point
    private static final Double MIN_LAT = 50.10319;
    private static final Double MAX_LAT = 60.15456;
    private static final Double MIN_LONG = 0.0;
    private static final Double MAX_LONG = 7.64133;

    private final Double latitude;
    private final Double longitude;

    public Point()
        this.latitude = ThreadLocalRandom.current().nextDouble(MIN_LAT, MAX_LAT);
        this.longitude = ThreadLocalRandom.current().nextDouble(MIN_LONG, MAX_LONG) * -1.0;


let mymap

class Stream {
    constructor(endpoint) {
        this.endpoint = endpoint
        this.source = null

    start() {

        this.source = new EventSource(this.endpoint)

        this.source.addEventListener('message', handleEvent)

        this.source.onerror = () => {


    end() {

const handleEvent = (event) => {
    const point = JSON.parse(

const stream = new Stream('/stream')

window.onload = () => {
window.onbeforeunload = () => {

const addMap = () => {
  const mapdiv = document.createElement('div') = 'mapid'
  mapdiv.setAttribute("style", "height: 1000px")

const createMap = () => {
    mymap ='mapid').setView([53.3811, 1.4701], 6)

    L.tileLayer('https://{s}{z}/{x}/{y}.png', {
        attribution: '&copy <a href="">OpenStreetMap</a> contributors'


const addPoint = (point) => {
    const marker = L.marker([point.latitude, point.longitude])

How to Create a Chat App with WebSockets, Java & Spring Boot

Download the static files required to follow along with this tutorial:


Easy Fix – Error: Java: invalid target release: 11 – IntelliJ IDEA

In the above video, you will learn how to fix the IntelliJ error stemming from having the wrong version of Java configured.

Error: Java: invalid target release: 11 – IntelliJ IDEA

Depending on the version of Java you want to run, you may also see this error:

Error: java: error: release version 8 not supported.

The reason that this is such an annoying error to fix is because there is not just a single place to change the current Java version.

There are many!

One of the first things you should try is updating your version of IntelliJ to ensure that you have at least IntelliJ IDEA 2018.x or higher. This is because older releases of Intellij IDEA don’t support Java 11.

The first place you need to set the version of Java is in the preferences. (CMD + ,) for Mac Users.

In the preferences pane, go to Build, Execution, Deployment > Compiler > Java compiler. Then click on the target bytecode version, and make sure that is set to the version of Java which you want to use.

Next, you need to go to the project settings in IntelliJ (CMD + ; ) for Mac users and set the Project SDK version to the version you would like to use. If you can’t find the version of Java which you require, then look at the video around 1:09, to see how to fix this issue.

Underneath the Project SDK setting, there is a ‘Project Language setting level’ is set to your desired Java version.

Then, whilst still in the project settings, go to Modules, then click dependencies, and again make sure that this is set to the version of Java which you want to use.

Finally, again whilst still in the project settings, click on the ‘sources’ tab and select the version you want from the language level dropdown.