Updated BasicToolVO to match the current Tool object, and added an interface to BasicToolVO. Now the call in lLamsToolService which allows a tool to access its own record in the lams_tool table refers to an interface (IToolVO) rather than a POJO. The code still passes a BasicToolVO to any calling tools, but it is better to refer only to interfaces in a service definition, rather than a concrete class.
repeated the same process done for q/a for mcq: switched to JSP 2.0 / Servlet 2.4 / JSTL 1.1 organized q/a's web.xml based on lams central web.xml made sure web.xml is valid and Eclipse has no formatting warnings added GPL license notices to files tested and made some modifications to jsps in relation to JSTL upgrade
same things done for q/a project: Switched to JSP 2.0 / Servlet 2.4 / JSTL 1.1 Organized q/a's web.xml based on lams central web.xml Made sure web.xml is valid and Eclipse has no formatting warnings Added GPL license notices to files
Service bean transaction definition was missing some of the ToolContentManager and ToolSessionManager methods, so these methods were not forming part of transactions.
authoring module fix for populating the correct map data for the revisiting authorscalling public static void assignStaterMapsToCurrentMaps(HttpServletRequest request)
authoring module fix for populating the correct map data for the revisiting authorsadded the method: public static void assignStaterMapsToCurrentMaps(HttpServletRequest request)
All the changes are to accomodate better integration between different modules. In this state all the modules seem to work properly and according to their specs. May requite lttle updates but expecting no major changes.Some work needs on bug fixing authoring module.