跳至主要内容

Rewrite or migrate a legacy Java application: how to decide

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

Somewhere in your company there is a Java app that runs the business. It works, the rules inside it took years to get right, and the people who wrote most of it have moved on. Now it needs to reach the browser, and the meeting keeps circling back to one question. Do we start over, or do we move what we have?

This page is for the architect who has to recommend an answer and the budget holder who has to sign it. Whether to rewrite or migrate a legacy Java application is mostly a question of risk, and a rewrite carries the most of it. Our case is simple: keep your Java app running, and move it to the web one screen at a time, with your own Java team.

Parallel run migration: prove each new Java screen with a test

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

You have moved the first screen of an old Java app to the web, and it looks right. The next question is harder. Does it still behave the way the old screen did, and will it still behave that way after the next ten screens land? Nobody wants a user to be the one who finds out.

In a parallel run migration the old and the new version run side by side, and the old one is the reference you compare against. For a Java desktop app, Webswing keeps the existing app running in the browser while webforJ builds the replacement screens next to it in the same tab, so the old behavior is still there to check each new screen against. This guide gives every new webforJ screen a TestBed test, a plain JUnit test with no browser, that pins the behavior your users rely on. Each screen passes its tests before the next one starts.

Big bang migration vs phased: how to cut over a Java app

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

The decision to leave the desktop is made. The app runs orders, claims or payroll every day, the budget is approved, and now someone has to say how the switch happens: one date when every user flips to the new system, or a long series of small moves. That choice, big bang migration vs phased, shapes the risk of the project more than the target framework does.

For a Java desktop app the phased path has a concrete shape. Webswing runs the existing app in the browser, webforJ screens replace it one at a time inside the same tab, and every replaced screen can keep a way back to the old one until you decide to delete it.

From 207,000 to 937: community size no longer measures a framework

· 一分钟阅读
Hyyan Abo Fakher
Lead Software Architect

cover image

Every team that evaluates a framework asks some version of the same question: if we get stuck, will we find an answer? For twenty years the honest shortcut was to look at the crowd. A big community meant many forum threads and many people who had already hit your problem. A small one meant risk.

That shortcut is still how most comparisons work, and it's still how AI assistants rank frameworks when you ask them. The numbers say it stopped working. Community size was only ever a proxy for one thing, knowledge reaching you when you need it, and the engine behind that proxy has stopped running for large and small frameworks alike.

A different question takes its place: do the people who build the framework publish what's true for the version you run, in a form your AI assistant can read and test?

JSF to Angular migration: what the rewrite really adds

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

Your team runs a JSF app that does real work. The screens are dated, the component library is getting harder to upgrade, and someone has been asked for a plan. Most of the advice you find points to Angular or to React.

This post is for the team about to start a JSF to Angular migration, or a JSF to React migration. It lists what that rewrite adds to a Java team, when it is the right call, and a third option: rebuild the UI in Java with webforJ and keep the Java backend and the Java team you already have.

The Business Case for a Java UI Framework: What Your Boss Will Ask

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

You have looked at webforJ and you like what you see. Now somebody with a budget or a veto wants to know why the team should adopt it, and "the developers prefer it" isn't an answer that survives a meeting.

This post is the business case for a Java UI framework, written as the questions a decision-maker asks, with a plain answer to each. webforJ is the full-stack Java framework for business web apps: you build the whole app, screens included, in Java. Each answer below links the page you can hand to your manager. If the framework is meant to replace an old Java app, the post also works as a legacy system risk assessment: the risks of staying, the risks of moving, and how a phased path reduces each one.

webforJ JavaScript Integration: Use the Libraries You Already Have

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

A Java framework that builds the whole screen in Java raises a fair worry for anyone choosing it: what happens the day you need a charting library, a date picker or a widget your team already owns, and it's written in JavaScript? Do you wait for the framework to ship its own version?

You don't. This post covers webforJ JavaScript integration: the documented ways to bring the JavaScript ecosystem into a webforJ app, and which one fits which job. webforJ is the full-stack Java framework for business web apps: you build the whole app, screens included, in Java. The standard app needs no JavaScript at all, and when you want some, there are four clear routes in.

Java applet replacement: your options after JDK 25

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

Somewhere in your company an applet still does real work. Maybe it's the order entry screen a branch office opens in an old browser profile, or a planning tool that lives inside a locked-down virtual desktop because nothing else will start it. It kept running because nobody touched it. That grace period is over, and finding a Java applet replacement is no longer a job you can push to next year.

JDK 25 is the last Java release that ships the Applet API. JDK 26 removed it. This post sets out the dates, what the removal breaks, and the options you can stand behind: keep the applet reachable in a browser through Webswing while you plan, or rebuild its screens as a webforJ app in Java, with the Java team you already have.

Who Uses webforJ? Customer Stories From Real Projects

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

A team that is about to pick a framework wants to know who already runs it. Logos on a landing page don't help much. What helps is knowing which companies built what, how big the team was, and how long it took.

So, who uses webforJ? Two full customer stories are published, one about Prodin and one about b+p, and both name webforJ as the framework behind the project. Prodin is Prodin Business Solutions, a Dutch software provider for enterprise resource planning (ERP). b+p is an HR consulting firm in Southwest Germany. Here is what each team built, how many people it took, and how long it took.

Why webforJ? Straight Answers to Questions Java Teams Ask

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

Your Java team has a new business web app to build, and the shortlist of frameworks keeps growing. Every option promises productivity, so the useful question is the one developers keep asking in public: why webforJ, and what do you get that you would not get elsewhere?

Here are straight answers. webforJ is the full-stack Java framework for business web apps: you build the whole app, screens included, in Java. The rest of this post shows what that means in practice, why we built it, and how it fits the backend, the tools, and the components you already have.

Cursor Spring Boot UI: Let the Assistant Write Your Screens in Java

· 一分钟阅读
Eric Handtke
Software Developer

cover image

You have a Spring Boot backend with services that work, and now it needs screens. Asking an AI assistant to write them is tempting, but a plain prompt in Cursor leaves the assistant guessing at your front end. For a Cursor Spring Boot UI that holds up, give the assistant the real webforJ API and let it write the views in Java. The webforJ AI plugin does that, and a short test confirms the result.

The webforJ ecosystem: what a Java framework needs in the AI era

· 一分钟阅读
webforJ
Do it all in Java. The full-stack Java framework for business web apps.

cover image

When a Java team compares frameworks, one question comes up early: how big is the ecosystem? It used to be a fair proxy for safety. More add-ons, more examples and more forum answers meant less code to write yourself and fewer dead ends.

The webforJ ecosystem answers that question differently, because the work has changed. Your team now writes much of its code with an AI assistant, so what counts is whether the parts you need are maintained for the version you run, and whether your assistant writes current, correct code for it.