With our first deployment of Jetspeed 1.4, we decided to use JSP primarily for new portlet development. We've found portlet development to be quite straight forward, when/if dealing with only single portlets per pane. We are now getting into having multiple portlets per pane, and most of our custom JSP portlets interact with themselves via form posts. We've recently gone back to rework our portets to use the action, eventSubmit_Action framework, however, I now have questions on how to best utilize database access. Prior to Jetspeed, we had developed using the traditional JSP/Servelet model, where the classes would be initialized once during runtime, thus allowing us to make use of the JSPInit, and Init methods to grab references to our JDBC connection pool data sources defined in our server.xml. With the initial release of our Jetspeed 1.4 portal, the JSP pages all work nicely using the JSPInit method to grab those datasource references from the default context. Now that we're trying to move to a jsp form action handler framework, questions have arisen as to where those variables should be initialized. It is my understanding that the logic, and data processing should be largely handled on the PortletAction class, but there does not appear to be a way to define the class thus that it only initializes once. Does anyone have any best practices for where the database logic should be defined, and how to do so with the least amount of overall overhead.
Thanks, -Art --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
