Modernization Toolkit
Automate up to 80% of your legacy Java code migration, preserving functionality
while dramatically reducing time, cost, and errors.
Swing
public VoyageView() {
String[] locations = new String[]{"Bayonne", "Berlin", "Bern", "Bilbao", "Birmingham", "Bremen", "Brussels"};
JList<String> departingCity = new JList<<String>();
departingCity.setListData(locations);
JList<String> arrivingCity = new JList<<String>();
arrivingCity.setListData(locations);
this.setLayout(new BorderLayout());
JButton searchButton = new JButton("Search");
JButton cancelButton = new JButton("Cancel");
JPanel citySelection = new JPanel(new GridLayout(0,2));
citySelection.add(departingCity);
citySelection.add(arrivingCity);
JPanel buttonBar = new JPanel();
buttonBar.setLayout(new BoxLayout(buttonBar, BoxLayout.Y_AXIS));
buttonBar.add(searchButton);
buttonBar.add(cancelButton);
this.add(buttonBar, BorderLayout.WEST);
this.add(citySelection, BorderLayout.CENTER);
departingCity.addListSelectionListener(new ListSelectionListener() {
@Override
public void valueChanged(ListSelectionEvent e) {
if (arrivingCity.getSelectedValue() == null) return;
if (arrivingCity.getSelectedValue().equals(departingCity.getSelectedValue())) {
arrivingCity.clearSelection();
}
}
});
}
Vaadin
public VoyageView() {
String[] locations = new String[]{"Bayonne", "Berlin", "Bern", "Bilbao", "Birmingham", "Bremen", "Brussels"};
ListBox<String> departingCity = new ListBox<String>();
departingCity.setItems(locations);
ListBox<String> arrivingCity = new ListBox<String>();
arrivingCity.setItems(locations);
this.setLayout(new BorderLayout());
FButton searchButton = new FButton("Search");
FButton cancelButton = new FButton("Cancel");
Panel citySelection = new Panel(new GridLayout(0,2));
citySelection.add(departingCity);
citySelection.add(arrivingCity);
Panel buttonBar = new Panel();
buttonBar.setLayout(new BoxLayout(buttonBar, BoxLayout.VERTICAL));
buttonBar.add(searchButton);
buttonBar.add(cancelButton);
this.add(buttonBar, BorderLayout.WEST);
this.add(citySelection, BorderLayout.CENTER);
departingCity.addValueChangeListener(new HasValue.ValueChangeListener<HasValue.ValueChangeEvent<String>() {
@Override
public void valueChanged(HasValue.ValueChangeEvent<String> e) {
if (arrivingCity.getValue() == null) return;
if (arrivingCity.getValue().equals(departingCity.getValue())) {
arrivingCity.setValue(null);
}
}
});
}
Ready to kill the tail on legacy dependencies and bring your Java Swing application to the future?
Download our white paper, ‘Modernizing Java Swing Applications: A Five-Step Blueprint for Decision-Makers,’ to learn how to automate your Swing-to-Web migration with the Vaadin Modernization Toolkit.
Get the job done with automation
Many conventional Java modernization projects adopting a phased approach can take years to complete, and developers often lack the motivation to finish. The automation provided by the Vaadin Modernization Toolkit can refactor the bulk of your Java code so you can quickly kill the tail of legacy dependencies and move forward with an architecturally coherent new application.
Fully customizable transformations
The Vaadin Modernization Toolkit includes a default set of transformation capabilities, enabling the most common features found in legacy frameworks. These can be extended with the APIs used in your application or customized if your application has tailored the legacy technology with non-standard behavior.
Trusted by award-winning companies to create award-winning software
From the list of the most influential FinTechs to the Best SaaS from the Cloud Awards, companies rely on Vaadin to create cutting-edge applications that make a big impact. The Vaadin Modernization Toolkit gives you a boost to accelerate your Java migration to modern web apps.
Java migration, not emulation
The Vaadin Modernization Toolkit helps migrate Java applications to Vaadin Flow, Vaadin’s open-source framework for building web applications with Java. After the migration, there will be no remaining dependencies on old frameworks such as Swing, SWT, or JavaFX. The Toolkit supplies useful features familiar to developers from old frameworks in a Feature Pack, but it does not emulate technologies like Swing.
Code readability built-in
We built the Modernization Toolkit to produce code that humans can read and maintain. Your transformed application sources retain the original structure, naming conventions, comments, and whitespace. Changes made by the transpiler are almost always applied within the same line of code, meaning your developers can confidently take ownership.
Fine-tuning: Reach your target automation with a fixed-price guarantee
The engineers at Vaadin offer a fixed-price Fine-tuning service to improve the Standard Rules, Custom Rules, and Feature Pack to reach a higher degree of automation for your application. The transpiler can also be iteratively improved to automate a higher percentage of the work.
