Andrew,
I think you ought to read the portlet spec in order to properly
understand what goes on in the action and render phases.  I know it
helped me a great deal when I started programming with portlets.  It
is especially helpful if you are used to developing with servlets.

The short answers are:
1. start using the portlet session heavily instead of request attributes.
2. the "query" needs to occur in portlet B's render phase or you need
to store the results in the session following the invocation of
portlet B's action phase.

-aaron

On 1/10/07, Andrew F Hall <[EMAIL PROTECTED]> wrote:
What are the best practices for maintaining the initial set of request
parameters across all portlets within a page for each form submission?

Scenario:

1.  I have a page that has two portlets:  PortletA.java and
PortletB.java
2.  The page is initially requested via GET with a url
http://www.foo.com/page.psml?foo=bar
3.  The page is returned, each Portlet renders a snippet of html that
has a form and a hidden variable: <input type="hidden" name="foo"
value="bar">
4.  The User submits a form to PortletA
5.  PortletA's processAction is driven.  It has access to the hidden
variable.  It performs its action and returns the html.  Everything is
ok.
6.  PortletB, however, processAction isn't driven and doesn't have
access to the form variable.  Consequently, it can't perform it's query.

So what are best practices so that PortletB can render itself under this
scenario?  Thanks in advance.

Andrew Hall
CircleUp
5120 West Goldleaf Circle, St 140
Los Angeles, CA 90056
voice    800.871.2314 x706
fax       310.399.1249
email:  [EMAIL PROTECTED]



> -----Original Message-----
> From: Stefano Bianchi [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 10, 2007 7:38 AM
> To: Jetspeed Users List
> Subject: Re: Moving J1.6 db from MySQL 3.1 to MySQL 5.0
>
> Dear all,
> I partially fixed it by running MySQL in strict mode and
> setting jdbcCompliantTruncation to false.
> Any comment anyway?
> Thanks
> S
>
> ----- Original Message -----
> From: "Stefano Bianchi" <[EMAIL PROTECTED]>
> To: "JETSPEED Users List" <[email protected]>
> Sent: Wednesday, January 10, 2007 1:10 PM
> Subject: Moving J1.6 db from MySQL 3.1 to MySQL 5.0
>
>
> > Dear ALL,
> > I am trying to move an old J1.6 installation to a new host and I am
> > getting problems with db.
> > After exporting and reimporting with SQLYog the jetspeed db
> from MySQL 3.1
> > to MySQL 5.0 I get something like:
> >
> > There has been an error!
> >    org.apache.jetspeed.services.security.UserException:
> Failed to save
> > user object : Data truncation: Data too long for column
> 'OBJECTDATA' at
> > row 1
> >
> > and also
> >
> > org.apache.jetspeed.services.security.UserException: Failed
> to retrieve
> > user 'euoexp1': Cannot convert value '0000-00-00 00:00:00'
> from column 9
> > to TIMESTAMP
> >
> > I have checked and the contents in the db tables look
> different, e.g.
> > OBJECDATA changes and timestamp are stored differently...
> >
> > Maybe it is just a MySQL issue (sorry), but has anyone
> successfully moved
> > db between such different MySQL version?
> > Any suggestion?
> >
> > And as I am going to work on a new project, would a blank
> new installation
> > for J1.6 work on MySQL 5.0?
> >
> > Thanks
> > S
> >
> >
> > Ing. Stefano Bianchi
> > Softeco Sismat S.p.A. - www.softeco.it
> > Via De Marini 1, WTC Tower
> > 16149 GENOA (ITALY)
> > Tel. +39 010 6026 368
> > Fax +39 010 6026 350
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > 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]
>
>

---------------------------------------------------------------------
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