--- Raphaël Luta <[EMAIL PROTECTED]> wrote: > Dan Moore wrote: > > >Hi Raphael, > > > >--- Raphaël Luta <[EMAIL PROTECTED]> wrote: > ><snip> > > > > > > > >>You'll be better off copying the Action class or whatever class you > > >>customize and register your modified class in the Registry > >>in A MyCustomizeSetPortlet and update the properties file to use > this > >>one instead of the original one. > >>This way your changes won't be messed if you upgrade to a new > version > >>of > >>jetspeed. > >> > >> > > > >I subclassed the MultiColumnControllerAction and overrode the > relevant > >methods. I changed the value in controllers.xreg--is that the > registry > >you're talking about (I also looked in registry.xml and didn't see > >anything that looked relevant)? > > > > > > > registry.xml is something you should not be concerned about unless > you > need to extend the > registry schema (deep customization). > Instead of modifying the entry in conrollers.xreg, I would probably > have > cloned it into a local-controllers.xreg > and renamed the controller names somewhat differently (ie > MyTwoColumns > instead of TwoColumns). > Then change the default controller used by Jetspeed in my.properties: > > services.PortalToolkit.default.controller=MyTwoColumns > > and update the existing PSML files with explicit controllers to > MyTwoColumns instead > of TwoColumns. > > > That way, you preserve all your environment even when you update the > controllers.xreg next time you upgrade > Jetspeed.
Thanks for the advice. > >Unfortunately, I had to put my subclass in the same package as > >MultiColumnControllerAction; it wasn't found otherwise. Jetspeed > >seemed to ignore the modules.packages property I added to > >TurbineResources.properties. > > > > > It should work, otherwise this is a major bug that needs to be fixed > ! Oops. I had a portlet that wasn't correctly configured, and I misdiagnosed the behavior of jetspeed after that. <snip> Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
