Status Update on Jakarta EE Support for SmartClient

[npatil]

We are currently in the process of migrating our project to the latest Spring Framework, which uses Jakarta EE. We're using SmartClient Pro version 12.1-p20221022, which still uses the javax namespace.
I noticed in a previous forum post (https://forums.smartclient.com/forum...ge3#post273950) that Isomorphic mentioned plans to migrate from javax to jakarta namespace in version 14.0. However, we've observed that even version 14.0 still uses the javax namespace and hasn't been migrated to Jakarta EE yet.
Could you please provide:

1. An updated timeline for Jakarta EE support, given that version 14.0 still uses javax
2. Which future version will include the Jakarta migration
3. Any interim solutions or workarounds for projects that need to use Jakarta EE with SmartClient
4. Migration guide or documentation that will be available for transitioning existing applications
5. Any known blockers or challenges that delayed the Jakarta migration in version 14.0

This information would greatly help us plan our migration strategy, as Jakarta support is becoming increasingly critical for modern Java enterprise applications. Many framework dependencies (Spring, etc.) have moved to Jakarta, making it challenging to maintain applications with mixed namespace dependencies.

[Isomorphic]

The plan is still for 14.0 to offer Jakarta support. It's not released yet.

Overall, however, it looks like you're looking for a high level of support for your transition. That's available, but not for free. Please see smartclient.com/services for a list of available service packages you might want to purchase.