Hi @aemninja!
It's hard to say without knowledge of your implementation approach.
But please let me repeat and raise this again: giving the content authors the possibility to author any kind of programming language (be it JSTL, HTML, JavaScript or whatever) is a highly discouraged practice. I would definitely look for another solution to your requirements. As you are already aware that even the technology is no longer state of the art, you may want to reevaluate and probably think about migrating your utilities to something more up-to-date.
You have provided little context here, but other approaches that come to mind here could be:
- Giving your content authors a list of functionality to choose from and integrating the according JSTL functionality from templates that have been developed and tested through your regular development cycle.
- If you just need to fill in certain values, you could use a dedicated syntax in your editor, e.g. similar to Expression Language like "This product is available in ${country} only." and replace according placeholders at render time.
The requirement for at least some kind of "free HTML" component comes up in nearly every project at a certain point in time. I understand the business use case behind such requirements but from a technical point of view I still object and recommend to not have something like this. Taking this from HTML to JSTL feels even worse to me. If your really, really need to follow this approach, please add as many guard rails as possible and restrict the usage of such a component as much as possible (probably only to a very limited set of tech-savvy super users).
