I'm porting an application to Spring that includes a number of ugly JSPs. By "ugly" I mean that the JSPs are not simply presentation devices, they contain a large amount of java code in scriptlets that implement data access and business logic.
I realize I will eventually want to replace these sad JSPs for a more modern, proper view technology but for now I just want them ported quickly.
I need to be able to easily access the ApplicationContext from these JSPs. My thought is to use the custom tag feature that allows me to expose a scripting variable which is the applicationcontext. Then in the JSPs I just include the custom tag and voila -- I can do applicationContext.getBean().
Am I reinventing the wheel? I looked at Spring's taglib and it does not have what I need. Help me not bark up the wrong tree!