The library jaulp.wicket is a collection of Apache Wicket components and utilities.
The components are loosely coupled and can be easily integrated into an existing Apache Wicket application.
The components are also designed to be customised so the user can provide they own components over factory methods.
The source code comes under the liberal Apache License V2.0, making jaulp.wicket great for all types of wicket applications.
Add the following maven dependency to your project pom.xml
if you want to import components:
<dependency>
<groupId>de.alpharogroup</groupId>
<artifactId>jaulp.wicket.components</artifactId>
<version>6.18.0</version>
</dependency>
Add the following maven dependency to your project pom.xml
if you want to import base stuff like base application, panel, pages etc.:
<dependency>
<groupId>de.alpharogroup</groupId>
<artifactId>jaulp.wicket.base</artifactId>
<version>6.18.0</version>
</dependency>
Add the following maven dependency to your project pom.xml
if you want to import behaviors etc.:
<dependency>
<groupId>de.alpharogroup</groupId>
<artifactId>jaulp.wicket.behaviors</artifactId>
<version>6.18.0</version>
</dependency>
Check out sonatype repository for latest snapshots and releases.
Example projects are moved to the wicket-examples project.
You can run every example project by doing following steps. For instance if you want to start the examples for the project jaulp.wicket.components you do this:
First change to the directory and build the project:
cd jaulp.wicket.components.examples
mvn clean install
Running the example:
mvn jetty:run
Call then http://localhost:8080/
Another way is to start the example application programmaticly with jetty. In every example project there exists a start class with a main method that have the prefix Start**** and the suffix ****Examples.
The source code of jaulp.wicket are on GitHub. Please feel free to fork and send pull requests!
Create your own fork of astrapi69/jaulp.wicket/fork
To share your changes, submit a pull request.
Don't forget to add new units tests on your changes.
Do not hesitate to contact the jaulp.wicket developers with your questions, concerns, comments, bug reports, or feature requests.
- Feature requests, questions and bug reports can be reported at the issues page.