Every Wicket component in Java has a partner element in HTML, joined by its wicket:id. Any Java IDE edits both files, but it does not know they belong together. A Wicket plugin does: it takes you from a component to its markup and back, and completes wicket:id values while you type. The plugins are written and maintained by their own teams, not by the Wicket project, so report a problem with a plugin in its own issue tracker.
IntelliJ IDEA: WicketForge
WicketForge adds code completion, inspections and navigation for Wicket to IntelliJ IDEA.
- Open Settings, Plugins, and the Marketplace tab.
- Search for WicketForge and choose Install.
- Restart the IDE when it asks.
With the plugin installed you can:
- switch between a page or panel class and its HTML file;
- go from a component in Java to its
wicket:idin the markup, and from awicket:idto the component that renders it; - complete
wicket:idvalues in Java and in HTML; - create a page or panel together with its markup file;
- complete and extract keys in the component’s properties files.
The WicketForge wiki describes each feature and its shortcut. Report problems in the WicketForge issues.
Shorter lambda models: WicketLambdaFold
WicketLambdaFold folds the getter and setter references of a lambda model in the editor, so a line like LambdaModel.of(model, Person::getName, Person::setName) reads as the property it binds. It changes only how the code is shown, not the code itself. Install it from the Marketplace tab the same way.
Eclipse: QWickie
QWickie adds Wicket navigation and code assist to Eclipse. It needs the HTML editor of the Eclipse Web Tools Platform, which the Eclipse IDE for Enterprise Java and Web Developers already contains.
- Choose Help, Eclipse Marketplace.
- Search for qwickie and choose Install.
- Restart Eclipse when it asks.
Without the Marketplace client, choose Help, Install New Software, and add the update site https://raw.githubusercontent.com/count-negative/qwickie/master/qwickie.updatesite/site.xml.
With the plugin installed you can:
- jump from a
wicket:idin Java to the element in the HTML file, and see that HTML fragment when you hover over the component; - jump from a
wicket:messagekey to its properties file; - complete
wicket:idvalues in Java with Ctrl+1; - rename the HTML and properties files along with a page or panel class;
- create a new page with a wizard.
Report problems in the QWickie issues.
NetBeans and VS Code
There is no maintained Wicket plugin for NetBeans or VS Code. Wicket does not need one: a page is a Java class and an HTML file, and the Java support of either IDE handles both. Keep the HTML file next to its class, as the quickstart project does, and the IDE shows the pair together in the project tree.