Wicket Markup Parser Customization

A MarkupFactory for Apache Wicket that allows customization of the created MarkupParser using customizations loaded using the service loader.

If you need to customize the markup parser for component types (or based on any other state of the MarkupResourceStream) using standard Wicket, you have to add the customizations to a custom MarkupFactory individually. Every time you want to use another component that requires customization, you have to modify your factory again.

This library provides a MarkupFactory that loads customizations using the Java service loader. Simply adding a dependency on a component type, will ensure the markup parser customizations for that component type will be applied to the markup parser.

There are 2 ways to enable the customizations, depending on whether you are currently already using a custom MarkupFactory or not:

• Using the standard MarkupFactory: change the markup settings of your application to use MarkupParserCustomizingFactory: getMarkupSettings().setMarkupFactory(new MarkupParserCustomizingFactory());
• Using a custom MarkupFactory: apply the customizations from newMarkupParser(MarkupResourceStream) of the custom factory: MarkupParserCustomization.customize(resource, parser);

Using Wicket Markup Parser Customization

API Documentation

The API documentation of all versions of Wicket Markup Parser Customization is available online.

Dependency

Add Wicket Markup Parser Customization to your project by adding a repository and declaring a dependency.

Repository

You have to add the Zybber artifact repository to the list of repositories. See the documentation of the releases at the Zybber artifacts for instructions.

Dependency Declaration

Add the dependency for Wicket Markup Parser Customization. See below for instructions for specific build systems.

Gradle

Using Kotlin scripts:

implementation("com.zybber:zybber-wicket-markup-parser-customization:1")

Using Groovy scripts:

implementation 'com.zybber:zybber-wicket-markup-parser-customization:1'

Where needed, use a version catalog, and an appropriate dependency configuration.

Maven

<dependency>
    <groupId>com.zybber</groupId>
    <artifactId>zybber-wicket-markup-parser-customization</artifactId>
    <version>1</version>
</dependency>

Where needed, use dependency management, and an appropriate scope.

Versioning Scheme

Wicket Markup Parser Customization is a small and very simple library, so uses a very simple versioning scheme: a single number. Whenever there is a release, the number is incremented by 1. No distinction is made between minor features, fixes and vulnerability fixes.

If the need arises to break the API, the code will be moved to another package, and another artifact name will be used. For example: package com.zybber.wicket.markup_parser_customization2 and artifact zybber-wicket-markup-parser-customization2-1.jar