• Added support for Java 22.
• Added support for WebJars when running with the embedded Jetty or Tomcat servlet container.
  When deployed as a WAR, WebJars were already supported.
• Added rife.feed package to make it easy to generate content syndication feeds.
• Fix to template parsing to support tags inside angled brackets without adjacent spaces.
  For instance: <{{v value1/}}></{{v value2/}}>
• Template improvements when being processed through web engine.
  The Context parameters are now used for the param: filtered value tags instead of request parameters.
• Fix to ensure that templates going through the web engine Context always get the context added as a template attribute before printing the template.
• Added ability to set custom attributes in CookieBuilder.
• Fixed issue where MySQL TINYINT(1) columns wouldn't be converted to boolean types in the database layer.
• Improvements to tests.
• Updated to latest bld.
• Updated RIFE2 IDEA plugin.
• Updated to latest dependencies.

https://example.com/news/2023/09/11

to

https://example.com/search?year=2023&month=09&day=11

You can easily convert the path info into parameters, by doing something like:

public class ExampleSite extends Site {
    //...
    private void redirectMoved(Context c, String url) {
        c.setStatus(301);
        c.addHeader("Location", url);
    }

    private void setRedirects() {
        //.. 
        get("/news", PathInfoHandling.MAP(
                        m -> m.p("year"),
                        m -> m.p("year").s().p("month"),
                        m -> m.p("year").s().p("month").s().p("day")),
                c -> redirectMoved(c, c.urlFor(searchUrl).params(c.parameters()).toString()));
    }

    @Override
    public void setup() {
        //..
        setRedirects();
    }
}

It's ready to run, package and deploy ... and for you to have fun developing in a very iterative, intuitive and rewarding way.

I also recorded a tutorial video with a primer on the template engine and some deployment strategies:
https://www.youtube.com/watch?v=AZWzYwAHDIE

• Provides file templates for Element, Router and Site class creation.
• Provides Java live templates for common routing idioms.
• Provides template engine live templates for tag creation and surrounding.
• Supports HTML, JSON, SVG, TXT and XML template language highlighting with fallback to original languages.
• Filtered value tags auto-completion to all template types.
• Syntax highlighting color settings configuration panel.
• Auto-tag closing characters addition when typing { or <!.

The source code is here:
https://github.com/gbevin/rife2-idea

Or use IDEA's built-in plugin system:
Settings/Preferences > Plugins > Marketplace > Search for "RIFE2" > Install Plugin

In order to try this out, please download the latest GraalVM JDK 19 distribution, and follow the steps to install native-image on your machine. https://www.graalvm.org/dev/reference-manual/native-image/

Once that is done, package your application as an UberJar and create a single native executable using the following command:

native-image --no-fallback --enable-preview -jar your-uber.jar

You'll be able to launch it with:

./your-uber

The RIFE2 bootstrap project is fully setup for AOT compilation, so you start there.

Below is a screenshot and with statistics of a micro-benchmark I did on my AMD Ryzen 9 5950X 16 Core 128GB dedicated Linux server.

Key points:

• application startup in 3ms
• standalone native executable size is 38MB
• using siege locally with a concurrency of 10 x 2000 requests, gives ~33898 trans/sec
• after the test, used up 281.7MB RES and 24.8MB SHR memory, account for 0.2% of memory

In comparison, launching the Uber jar with the JVM:

• application startup in 177ms
• uber jar size is 4.7MB but requires a separate JVM installation
• using siege locally with a concurrency of 10 x 2000 requests, gives ~44444 trans/sec
• after the test, used up 1.7GB RES and 39.7MB SHR memory, account for 1.3% of memory

NOTE: RIFE2 support for GraalVM native-image is still in preliminary stages. There's no solution yet to replace the features of the RIFE2 Java agent, and it's only been tested in a limited context. When expanding the code of the project, you most likely will have to update the native-image configuration files located in app/src/main/resources/META-INF/native-image.
More information about that can be found in the GraalVM manual.