Contact person: Upgrade Java Project to WildFly

Phone:Show

Email:Show

Location: Kanpur, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"My production system still runs on Java 1.5 inside WebLogic 10.0.0. I now need the entire application lifted to Java 1.8 and deployed on WildFly 26.1.

Key points you should know before jumping in:
• The codebase relies on Hibernate (an older 3-series release). I want to replace that dependency with a modern, fully-supported version—or an alternative you recommend that plays nicely with Java 1.8 and WildFly’s built-in JPA provider.
• I am replacing, not merely upgrading, any other outdated libraries you uncover during the migration. Feel free to suggest the cleanest stack that keeps future upgrades painless.
• I don’t have pinned version numbers; I’m looking for your recommendations on stable, long-term-support releases that align with WildFly 26.1.

Scope of work
1. Update the source to compile and run under Java 1.8.
2. Re-configure and package the application (currently an EAR) so it deploys cleanly on WildFly 26.1, including all necessary datasource, JMS, and security settings.
3. Swap out the legacy Hibernate layer for the recommended replacement, adjusting configuration, annotations, and build scripts accordingly.
4. Deliver a repeatable build (Ant build ) plus a brief migration guide that explains steps, version choices, and any code changes.

Acceptance criteria
– Source builds without warnings on Java 1.8.
– Application deploys and all existing functional tests pass on WildFly 26.1.
– No references to deprecated or removed Java EE APIs remain.
– Documentation covers setup, build, and any manual migration notes.

If you’ve handled similar legacy jumps before, tell me about them and outline your approach. I’m happy to answer domain-specific questions once you see the code." (client-provided description)