jlink has a "sticky screen" feature that makes it automatically remember the screen context of a portal page, thus if your portlet is called in the "Customize" context, using a simple jlink will keep you in Customize context unless you explicitely specify another screen.
The same portlet used in portal context (ie Home screen) will keep you in this context and thus trigger buildNormalContext(). > -----Message d'origine----- > De : Chay Weei Jye [mailto:[EMAIL PROTECTED]] > Envoy� : lundi 2 septembre 2002 02:49 > � : Jetspeed Users List > Objet : jlink > > > Hi, > > I am using .vm templates with Jetspeed. I find that using > "jlink" in a <a > href> or <form action> tag at the configure template will render: > "/portal/jetspeed/Customize". This will cause Jetspeed to call > *buildConfigureContext* method in the action class if the > link is clicked. > > However, I can't find any documentation on this. Is this a > permanent feature? > > Thanks. > > > > -- > 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]>
