Internship at Imas NV

Internship case

Summary

For Imas NV, my employer, I worked on the modernisation of the Fenics ERP application. I helped connect existing Swing/RMI and WildFly functionality to REST-based Quarkus services while supporting local development, debugging and validation.

Company: Imas NV / Van Genechten Packaging Group
Role: Software Development Intern
Period: 2025 — 2026

RMI to RESTWildFly to QuarkusLegacy modernisationPodmanValidation

Built / Changed

Analysed existing RMI methods, management beans and backend communication flows.
Adapted selected WildFly management beans so Swing client calls could be forwarded to Quarkus REST services.
Applied the migration pattern within Masterdata and RawMaterials based on an existing HR reference module.
Handled technical concerns such as Java compatibility, request structures, JSON serialization and REST error handling.
Created a Podman-based setup to support local Quarkus development, debugging and validation.
Explored temporary UI test automation for the Swing client through a Jemmy proof of concept.
Documented reusable migration steps, technical guidelines and examples for future Fenics migrations.

Technical Background

Fenics is a long-standing Java EE ERP application with a Swing client, WildFly backend and RMI-based communication.
Imas is gradually moving selected functionality towards REST-based Quarkus services and a more cloud-oriented architecture.
The migration had to happen in phases because the existing Swing client still needed to remain operational during the transition.

Documents

Project Plan

Initial project document defining the internship context, modernization goals, scope, planning, business case and follow-up approach.

Open document

Realization Document

Technical realization document describing the implemented RMI-to-REST migration pattern, transition architecture, validation approach and supporting developer tooling.

Open document

Reflection

Reflection document evaluating the project outcomes, technical challenges, personal growth, collaboration and lessons learned during the internship.

Open document

Internship Report

Chronological internship log with bi-weekly progress updates, documenting daily work, technical findings, decisions and follow-up throughout the internship.

Open document