Deprecate use of taglibs

Description

I think that there are multiple threads here and I welcome feedback.

  • Add @deprecate to all classes in net.shibboleth.idp.ui.taglib (4.1)

  • review our use of taglibs

    • index.jsp uses the spring taglib support

    • x509-prompt uses spring taglib support and our taglib support

  • Given the above. Can we add a deprecation warning to the log? 

Environment

None

Activity

Show:

Rod Widdowson June 21, 2023 at 10:11 AM

Added an atRiskOnce() to the taglib classes.

Not closing this since it may bounce back.

Scott Cantor June 20, 2023 at 3:03 PM

That seems appropriate for now.

Rod Widdowson June 20, 2023 at 3:02 PM

Shall I just slam an “at risk” warning into it and call this case done?

Scott Cantor June 17, 2023 at 4:14 PM

We can’t get rid of JSP, but it may be plausible to get rid of the actual taglib we built. But I don’t know that it really buys us much either.

Rod Widdowson June 17, 2023 at 10:14 AM

Is this going to happen? If so, what is this? It seems that we cannot get away from jsp and that for of requires taglibs, both the spring ones and our IdPUI one

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Created March 5, 2021 at 4:44 PM
Updated August 26, 2023 at 3:26 PM
Resolved June 21, 2023 at 10:11 AM