soapui VS Lombok

Let's first try the service manually. We will use the SoapUI testing tool. After importing the WSDL, test requests are automatically created. There are two versions of the "SOAP binding" imported from the WSDL. We will use the newer one, SOAP 1.2. We just need to substitute the input number in the place of a question mark and we can invoke the web service:

SoapUI

There are plenty of tools for stress testing, read RapidAPI, paw, SoapUI, Postman, rest-assured, JMeter and so on! I'm sure they are amazing, however that's all big and heavy, slow, sometimes paid tools!

SoapUI: https://www.soapui.org/

SoapUI from SmartBear is a popular tool that gives you a great graphical UI for navigating through a WSDL. Popping open any operation gives you a sample request that you can fill in and execute from within their app:

I found SoapUI when I had to develop some SOAP services, but these days it also does REST etc just fine.

For someone like me who just does this occasionally I found it rather useful.

[1]: https://www.soapui.org

Eclipse IDE (IntelliJ when I have to depending on the team) (oh and I use the Eclipse package download site, not the installer) Bash shell (WSL on Windows) Gnu CLI commands Dbeaver (although I tend to use the version in the repos) MySQL Workbench (although I tend to use the version in the repos) Meld (like it better than any other comparison tool for ad hoc visual file compares) Apache JMeter (performance testing) (I tend to download and run manually instead of the one in the repos) GIMP Wireshark (great for figuring out why someone's fancy REST client isn't passing JSON correctly) SoapUI (or Postman depending on the team, I prefer SoapUI - which does REST)

SOAP

The above class maps the json data to a java object we can work with. We use Lombok to generate constructors, getters and setters for our code and the Jackson Project to handle serialization and deserialization of json to pojo . We know the response is an array of objects representing the coffee and so above data structure is fit for this.

Almost a decade ago, I started reducing my boilerplate (and saving time with Lombok. It made my life much easier, simple as that. Ever since I've been looking into finding the smoothest solutions for saving time rather than handling all of it myself.

Lombok is a widely used library that simplifies Java code. The @NonNull annotation helps enforce non-null parameters, generating appropriate null checks:

Project Lombok

I gotta agree with /u/rzwitserloot I don't see anything in the lombok repo that indicates they have their "own compiler". I see the "reaching into javac internals" but that's it.

i looked into that and found this: https://github.com/projectlombok/lombok/issues/2310

Funny enough; /u/rzwitserloot is the author of Lombok, one of the most widely used Java libraries in the world. So it's not really some kind of random-ass Redditor they're having a discussion with either.

This removes the need to add the 'Project Lombok' library (and going through a phase of installing it in your Eclipse IDE; old school devs know what I am talking about) and speeds up development time. Java 14 added a new feature of 'Records' which allows you to do the same, but it doesn't offer a 'copy' method to ease your object creation and also enforces the 'final' keyword for variables making them immutable.

I get the main criticisms of Java, i.e. its verbosity and the requirement for a lot of boilerplate code, and understand why some people switched to Kotlin. But by using libraries such as lombok you can get rid of most of it and suddenly the incentives for switching aren't that big anymore. And in the end it's all JVM bytecode anyways.

I usually use this... https://projectlombok.org/