Is JAIN SLEE obsolete?▾
Not as a service model. JAIN SLEE 1.1 is defined by JSR-240 and has been stable since 2008. It remains a good fit for event-driven telecom services. The real question is whether the runtime you operate can meet your current Java, security, support and deployment requirements.
How should we evaluate a newer open-source fork?▾
A changed Java compile target is one part of the review. Check the release and patch process, dependency inventory, supported adaptors, operational tooling and who accepts responsibility for defects. Test the services and runtime extensions you operate; repository activity alone does not establish that they will behave correctly in production.
What licence is it under, and why does that matter?▾
The community container is AGPL-3.0, and so are the newer forks. If you extended the container and you run it as a network service, your own service logic is part of that licensing question. OVOO JSLEE is licensed commercially, with no copyleft reach into your code. Your legal team will want to look at this before your engineers do.
Do we have to rewrite our SBBs and resource adaptors?▾
The migration is designed to preserve the SBB, RA, profile, activity and timer model. How much reuse you get depends on your descriptors, vendor extensions, management integrations and custom adaptors, so we confirm compatibility service by service rather than promising it up front.
Does this require new CAPEX or a risky application rewrite?▾
The model is designed to maintain business continuity without a rewrite: proven service logic is preserved and change is staged per service. Project-specific infrastructure and integration scope is confirmed in the compatibility review before any work begins.
How does a Mobicents or RestComm migration start?▾
With the exact version and build you operate, then an inventory of SBBs, resource adaptors, descriptors, Java dependencies and runtime-specific extensions. That evidence picks the first service, defines any shim we need, and sets the tests it has to pass in your lab.
How does a Rhino migration start?▾
The same evidence-first approach. We map the service model, deployment descriptors, management dependencies and adaptor behaviour. The output is a compatibility matrix and a staged plan, not a blanket promise of binary compatibility.
What does the move to Java 21 LTS mean for our service dependencies?▾
Java 21 LTS is the target runtime. Include custom libraries, drivers and resource-adaptor dependencies in the compatibility inventory, then exercise them with the first service in the lab. The Java version and the application dependencies are assessed together before cutover.
Does NIS2 prohibit a particular Java version or open-source software?▾
No. NIS2 names no language, product or version. Article 21 requires risk-management measures, including security in acquisition, development and maintenance, and vulnerability handling. A maintained Java 11 distribution still receives security updates. The practical risk is not a version number: it is a platform with no support path, no dependency visibility and no accountable vulnerability management, which is what an auditor will ask you to evidence.
What happens when a service uses runtime-specific extensions?▾
Separate standard JSR-240 behaviour from the vendor-specific calls, descriptors and management dependencies used by that service. The compatibility review identifies the targeted shim or code change needed for each extension. Those changes are tested against the current service behaviour before the service moves.
What should we bring to scope a Diameter integration?▾
Bring the Diameter application interfaces and application-specific extensions used by your services, together with the existing adaptor configuration and relevant call flows. The OVOO adaptor is based on RFC 6733; the review confirms the application behaviour needed on that base protocol.
How do you reduce cutover risk?▾
The first service is proven in your lab against your own tests before anything moves. Production then changes one service at a time, using canary or blue-green rollout, service-level guardrails, written rollback criteria and an operator runbook, rather than a single irreversible switch.