Migration from Java EE to Jakarta EE #13
Description
Activity
- Two things: 1) You probably want to report this issue under ESAPI/esapi-java-legacy and not here. 2) Please try more specific in your "ask". All the ClickjackFilter references are standard javax.servlet INTERFACES. If Jakarta EE changed those to (say) jakarta.servlet, they will have broken a lot more than just the ClickjackFilter, but most of ESAPI. And not *just* ESAPI, but most JavaEE web applications.On Fri, Jul 23, 2021, 8:43 AM stefanuzz86 ***@***.***> wrote: The filters class cannot be use after the migration to jakarta EE because class as org.owasp.filters.ClickjackFilter still referer to javax.* instead of jakarta.* — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAO6PG553VELLTQQJPOD47DTZFPXVANCNFSM5A3563YA> .-kevin
The filters class cannot be use after the migration to jakarta EE because class as org.owasp.filters.ClickjackFilter still referer to javax.* instead of jakarta.*