Hmm, ok, could you please repost your flowscript and the exception with stacktrace you get?
Thanks Carsten > -----Original Message----- > From: Andrew MacDonald [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 07, 2004 5:05 PM > To: [EMAIL PROTECTED] > Subject: RE: Changing the portal layout dynamically > > Thanks for the suggestion Carsten. I tried auth-protecting > both the call to the flow, and the regular pipeline, but > unfortunately it didn't seem to make a difference... I'm > still receiving the same errors. > Here's the relevant sitemap code: > > <map:match pattern=""> > <map:act type="auth-protect"> > <map:parameter name="handler" > value="portal-handler"/> > <map:parameter name="application" > value="portal"/> > <map:call function="flow"/> > </map:act> > </map:match> > > <map:match pattern="*.xf"> > <map:act type="auth-protect"> > <map:parameter name="handler" > value="portal-handler"/> > <map:parameter name="application" > value="portal"/> > > <map:generate type="jx" > src="templates/{../1}.xml"/> > <map:transform type="session"/> > <map:transform > src="context://portal/resources/xforms/xforms2html.xsl"/> > <map:serialize type="xhtml"/> > </map:act> > </map:match> > > Any other suggestions? > > -Andrew > > >I think that you have to "initialize" the context on each request > >before you can use it. > >Usually you can do this by calling the > "auth->protect" action in > >the sitemap with the handler and the application parameter > before you > >call your flow. > > > >HTH > >Carsten > > > > > _______________________________ > Do you Yahoo!? > Declare Yourself - Register online to vote today! > http://vote.yahoo.com > > --------------------------------------------------------------------- > 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]
