Using a CustomizerVelocity portlet... in 1.3a2...
I can select the customizing template in my VelocityPortletAction's
buildConfigureContext(). When that template makes a form and the user
presses the "eventSubmit_doUpdate" button, the action's doUpdate() is
called.
After this, the page is re-drawn, and neither buildNormalContext() nor
buildConfigureContext() is called. It appears to use the original template,
not the customizer one, and the context is not setup for it.
Also, when I press the customize button to start all this, the portlet is
maximized. It stays maximized after.
What was the intent here?
Are the doUpdate() and the like responsible for setting the context, just as
the buildNormalContext and buildConfigure Context are, or should one of
these have been called and there's a bug? If doUpdate() is responsible, why
is it not passed the portlet parameter as the build's are?
If the portlet gets maximized at the start of configuration, how is the
action code to indicate that it is done, and the normal page should now be
displayed, portlet no longer in configure mode and maximized? I tried this
code takes from CustomizeAction .java's doCancle():
rundata.getSession().removeAttribute("parameters");
((JetspeedRunData)rundata).setCustomized(null);
if (((JetspeedRunData)rundata).getCustomized()==null)
{
rundata.setScreenTemplate("Home");
}
in my doUpdate(), and the code is called, but it had not effect!
CustomizeAction (i.e. a portlet customized without special customization
behavior defined) seems to do what I want mine to do!
What am I missing?
Thanks!
- Glenn
--------------------------------------------
Glenn R. Golden, Systems Research Programmer
University of Michigan School of Information
[EMAIL PROTECTED] 734-615-1419
http://www-personal.si.umich.edu/~ggolden/
--------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
