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.


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 !

Right now, here's the process I go through to add a portlet to a pane.

1. Click on the customize button of a pane.
2. Click on the 'Add Portlet' button.
3. Choose a portlet or two.
4. Click 'Apply.'
5. Click 'Save and Apply.'

I'd like to turn that into this process:

1. Click on the 'add content' button of a pane.
2. Choose a portlet or two.
3. Click 'Save and Apply.'

I tried fiddling with the url I'm sent to after clicking the add button
and going there directly after logging in, but I seem to have to go
through the intermediate step (when I try to go directly, I'm just
returned to the home page).  Perhaps the information that the add
action needs is not present.



Here's an example that works for me (but you can try it on any jetspeed install):

1. Login on the sample jetspeed site:  http://www.bluesunrise.com/jetspeed/
2. Once logged in, type the following URL:
http://www.bluesunrise.com/jetspeed/portal/template/Customize/mode/add?action=controls.Customize

Note: this screen will not return directly into the "main" page unless you modify the range of buttons,
ie you need to copy the "Save and Apply" button and logic from the main layout customization screen.


--
Rapha�l Luta - [EMAIL PROTECTED]
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to