FacesManagedBeansRemoved for Faces 4.0 recipe updates

[evie-lau]

Faces 4.0 recipe - FacesManagedBeansRemoved - needs additions

I found a few things the org.openrewrite.java.migrate.jakarta.FacesManagedBeansRemoved recipe is missing.

Reference documents

• Previous Jakarta Faces 3.0 docs shows replacements needed. Most are currently covered
• Additional docs on migration to Faces 4.0 for EE10: https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/8.0/html/migration_guide/application-migration-from-jakarta-ee-8-to-ee-10_default#faces-managed-beans_default

Missing fixes

1. CustomScoped

• java.faces.bean.CustomScoped and jakarta.faces.bean.CustomScoped seem to need a custom recipe to use CDI custom scopes and jakarta.enterprise.context.spi.Context. Unsure of recipe scope, and if feasible.

Migration case with build error:

[ERROR] ... package jakarta.faces.bean does not exist
[ERROR] ... cannot find symbol
[ERROR]   symbol: class CustomScoped

Additional analysis: #1025 (comment)

Problem: jakarta.faces.bean.CustomScoped was removed in Faces 4.0 with no direct replacement. The CDI equivalent involves defining a custom scope annotation with @NormalScope or @Scope, plus registering a Context implementation — this is NOT a simple ChangeType.

Status: This would require a custom Java recipe and the migration path isn't mechanical (the issue author also notes "unsure of recipe scope, and if feasible"). Skipping for now.

✅ 2. ManagedProperty name - fixed in #1025/#1027

Faces 3.0 ManagedProperty doc
Faces 4.0 ManagedProperty doc

• name was an optional element in Faces 3.0, and removed in Faces 4.0. Possibly remove entirely unless there is another migration path to maintain functionality.

Migration case with build error:

[ERROR] ... cannot find symbol
[ERROR]   symbol:   method name()
[ERROR]   location: @interface jakarta.faces.annotation.ManagedProperty

[salaheddinemchich]

Hi, I'd like to work on this issue. Is it still available and are there any specific guidelines I should follow?

[timtebeek]

Thanks for the offer to help @salaheddinemchich ; this issue has already been partially addressed, and what's left is a bit unclear as there no clear on to one replacement. Perhaps not the best issue to be taking on at the moment.

Might I suggest you look over any of the issues tagged "good first issue" instead?

[salaheddinemchich]

Thanks for the offer to help @salaheddinemchich ; this issue has already been partially addressed, and what's left is a bit unclear as there no clear on to one replacement. Perhaps not the best issue to be taking on at the moment.

Might I suggest you look over any of the issues tagged "good first issue" instead?

Hi @timtebeek,

Thanks for the clarification, I really appreciate it. That makes sense

I’ll take your advice and look into some of the "good first issue" tickets instead.
Thanks again for pointing me in the right direction!