Overview
The Java technology ecosystem is transitioning from Java EE (javax) to Jakarta EE (jakarta). As a result, continued support for current and future Java technology versions requires applications and customizations that rely on Java EE to migrate to Jakarta EE.
For Planon customers with Tailor-Made Software (TMS), this means that affected TMS must be made Jakarta-compatible to maintain compatibility with future Planon releases. This transition is driven by the broader Java technology ecosystem and is necessary to maintain security, supportability, and access to future technology updates.
As part of this transition, Apache Wicket will also be upgraded from version 9 to version 10, as Wicket 9 is not compatible with Jakarta EE. Wicket is the web framework used within Planon, which means TMS and private apps that include a user interface may also require updates.
Solutions known to require updates include:
- JAX-RS services
- TSI Actions
- Webpages
- Stepviews
- Mobile modules/cards
To provide sufficient preparation time, Planon will make Jakarta-compatible releases available beginning 1 November 2026 (L135), allowing you to proactively upgrade lower environments, assess your TMS, complete any required remediation, and begin testing before the applicable production upgrade.
For customers without an Upgrade Control license:
- Lower environments will be automatically upgraded to L137 on 18 February 2027
- Production environments will be upgraded to L137 on 18 March 2027
Customers are strongly encouraged to begin planning early to allow sufficient time for assessment, remediation, and testing prior to production upgrades.
How Planon Can Support You
Customers with a TMS SLA
Customers an active TMS SLA may submit a support ticket requesting a review of their Tailor-Made Software for Jakarta compatibility upon the upgrade of a lower environment to L135 or higher.
Planon Support will:
- Assess impacted TMS components for Jakarta compatibility
- Apply required compatibility updates where covered by the TMS SLA
- Return the updated solution for customer validation
While Planon will perform the required updates, customers remain responsible for conducting thorough business and user acceptance testing to verify that all custom processes continue to operate as expected.
Customers without a TMS SLA
Customers without a TMS SLA are responsible for ensuring their Tailor-Made Software is compatible with Jakarta.
We strongly recommend engaging Planon Services as early as possible to:
- Assess potential impacts
- Estimate required remediation work
- Implement necessary updates
- Allow adequate time for testing before production upgrades
As mandatory upgrade dates approach, services demand may increase. Early engagement will help ensure adequate time for assessment, remediation, and testing activities.
Resources for Developers
Beginning with L135, Planon will provide a Jakarta migration skill for GitHub Copilot as part of AppBuilder. This capability is designed to help developers automate portions of the migration of private apps to Jakarta and simplify the remediation process.
What You Should Do Now
The timeline below outlines the recommended steps to prepare for the Jakarta transition, from early assessment and planning through testing and production readiness. We encourage you to connect with your Planon representative early to begin reviewing your TMS and planning your approach early so we can help determine the best path forward for your organization.
