There's no major difference between the two except that OneColumn based on the MultiColumnController and thus uses a coordinate based constraints system, whereas ColumnController uses a position based constraint sets.
This has only a noticeable effect when you change the layout to multiple columns: with OneColumn -> all the portlets defined stay on the first column and the others start empty with ColumnController -> the protlets are equally spread between the different columns. In short, +1 to change the default controller and make ColumnController hidden. > -----Message d'origine----- > De : David Sean Taylor [mailto:[EMAIL PROTECTED]] > Envoy� : jeudi 21 novembre 2002 01:22 > � : Jetspeed Developers List > Objet : default controller > > > Looking at the ColumnController entry: > > <portlet-controller-entry name="ColumnController"> > > <classname>org.apache.jetspeed.portal.controllers.VelocityPort > letController< > /classname> > <parameter name="template" value="column.vm" /> > <parameter name="action" > value="controllers.RowColumnControllerAction" > /> > <media-type ref="html"/> > <media-type ref="wml"/> > <meta-info> > <title>Single column (Do not use)</title> > <description>This controller is being retired. Use OneColumn > instead.</description> > </meta-info> > </portlet-controller-entry> > > It says the controller is being retired, and to use OneColumn instead. > Why is it still used as the default controller ? > > services.PortalToolkit.default.controller=ColumnController > > anyone mind if I change the JRP to > > services.PortalToolkit.default.controller=OneColumn > > ? > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
