We are migrating our application to be available via the Portal engine in SAP, and was curious if others have crossed this bridge.
Now I need to access the ApplicationContext from the portal runtime too. I believe it must use the same instance of the ApplicationContext as the app deployed on the J2EE container, mainly because we have toplink doing the O-R, and want to share the same object cache.
So now I am looking for the best way to make the ApplicationContext available within the Portal code.
A little more background, because we are still in the process of migrating the existing code to spring, i have employed a singleton to represent the bean factory, until i retrofit the servlets to access it via the servlet context.
My thought was I would put the applicationcontext in the jndi tree, and get it from the portlet code...does that sound good? Any suggestions?