My advice is to check out how the customizer actions work
like:

org.apache.jetspeed.modules.actions
       .controllers.MultiColumnControllerAction

and also in the dev mailling-list archive:

http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]
che.org&msgId=506924

Finally use the StateManager to pass objects around your different
Action events.

--
Rapha�l Luta - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/

> -----Message d'origine-----
> De : Pierre Henry [mailto:[EMAIL PROTECTED]]
> Envoy� : jeudi 30 janvier 2003 08:38
> � : Jetspeed Users List
> Objet : RE: portlet object in doUpdate()
> 
> 
> I would say it is ok without action. If you want 
> buildNormalContext to be
> called after doUpdate, you still can call it explicitely from there...
> 
> > -----Original Message-----
> > From: Wei Guan [mailto:[EMAIL PROTECTED]]
> > Sent: mercredi, 29. janvier 2003 08:00
> > To: Jetspeed Users List
> > Subject: Re: portlet object in doUpdate()
> > 
> > 
> > Pierre:
> > 
> > I tested your workaround. I used velocity. I used POST. Here is the
> > behavior.
> > if I removed "action", I could get "portlet" in doUpdate(), however,
> > buildNormalContext is never got called.
> > if I keep the "action", the "portlet" is null in doUpdate(),
> > buildNormalContext is called after doUpdate().
> > 
> > Is it a bug?
> > 
> > Thanks.
> > 
> > ----- Original Message -----
> > From: "Pierre Henry" <[EMAIL PROTECTED]>
> > To: "Michael Rothrock" <[EMAIL PROTECTED]>
> > Cc: "Jetspeed User List (E-mail)" <[EMAIL PROTECTED]>
> > Sent: Tuesday, January 28, 2003 2:26 AM
> > Subject: RE: portlet object in doUpdate()
> > 
> > 
> > > I got them to work with GET, but it only works with 
> > Internet Explorer, It
> > > doesn't work with Mozilla, the buildNormalContext action is 
> > called, not
> > the
> > > actions... (I tried MSIE 5 and 6 and Mozilla 1.2)
> > >
> > > Pierre
> > >
> > > > -----Original Message-----
> > > > From: Michael Rothrock [mailto:[EMAIL PROTECTED]]
> > > > Sent: lundi, 27. janvier 2003 19:21
> > > > To: Jetspeed Users List; Pierre Henry
> > > > Subject: Re: portlet object in doUpdate()
> > > >
> > > >
> > > > Since I'm about to be working on this, let me ask a related
> > > > question: has
> > > > anyone gotten JSP actions to work with GET?
> > > >
> > > > Thanks!
> > > >
> > > > -- Michael
> > > >
> > > > On 1/27/03 1:09 AM, "Pierre Henry" <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi Wei,
> > > > >
> > > > > I had the same problem last week (see my mail with title
> > > > "Tricky behavior
> > > > > with JSP portlet and forms").
> > > > >
> > > > > what I found out :
> > > > >
> > > > >> - the form in the JSP doesn't need any action attribute
> > > > >>
> > > > >> - the ony needed hidden field is js_peid which contains the
> > > > >> portlet's ID.
> > > > >>
> > > > >>
> > > > >> When I put a hidden field for the action :
> > > > >> <INPUT TYPE="hidden" name="action"
> > > > >> value="CustomizableXsqlPortlet1Action">
> > > > >> the right method was called  but the portlet argument of the
> > > > >> doUpdatefilter
> > > > >> method was null, so the action class couldn't do much.
> > > > >
> > > > > So try to remove the action field...
> > > > >
> > > > > I hope it helps !
> > > > >
> > > > > Pierre
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Wei Guan [mailto:[EMAIL PROTECTED]]
> > > > >> Sent: lundi, 27. janvier 2003 07:49
> > > > >> To: [EMAIL PROTECTED]
> > > > >> Subject: portlet object in doUpdate()
> > > > >>
> > > > >>
> > > > >> I have a doUpdate in an VelocityAction class:
> > > > >>
> > > > >> VelocityPortlet portlet = (VelocityPortlet) 
> > context.get("portlet");
> > > > >>
> > > > >> the portlet is null.
> > > > >>
> > > > >> Is this a bug?
> > > > >>
> > > > >> Wei
> > > > >>
> > > > >
> > > >
> > >
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > 
> 

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

Reply via email to