I'll check it out.
If it doesn't work I'll open the link in a new window as a temporary sollution. This way I can skip the aggregation and the pipeline nesting.
Bert
At 15:28 30/10/2002 +0200, you wrote:
On Wed, 30 Oct 2002, Bert Van Kets wrote:
> apparently it does :(
> Any solution around this?
Maybe. This was my workaround before the <xsp-session:getxml/> arrived.
http://www.mail-archive.com/cocoon-users@;xml.apache.org/msg18314.html
I'm still using it, although it's not very flexible. Try it out.
-Tuomo
>
> How can I call the data in the session context in a pipeline that's called
> from another pipeline???
>
> I'm about to throw my PC out the window!
>
> Bert
>
> At 14:44 30/10/2002 +0200, you wrote:
> >Could this happen due to this bug:
> >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12293 ?
> >
> >Just a guess...
> >
> >-Tuomo
> >
> >On Wed, 30 Oct 2002, Bert Van Kets wrote:
> >
> > > I'm trying to create a form that gives the authenticated user access to his
> > > data in the database.
> > > I'm using the sunRise authentication in a CVS build form 14 May 2002 with
> > > tomcat 4.0.1 and jDK 1.3.1_2 on win2K.
> > >
> > > A pipeline aggregates all the necessary data to present the page. One part
> > > of this aggregation is a call to a pipeline that generates the xhtm form
> > > containing the user data.
> > >
> > > When I call the pipeline that generates the xhtml form directly I get the
> > > correct content. When I call the full page, I get a nullpointer error on
> > > the above pipeline.
> > > very strange. Commenting out the form pipeline gives me the page without
> > > errors, but with no actual content. When I replace the call to the
> > > pipeline with a call to a file I created by saving the output from calling
> > > the form creation pipeline directly, I get a correct full page.
> > >
> > > The pipeline that generates the user data xhtml form uses the
> > > xsp-session:getxml tag (the latest version) to get the user ID from the
> > > session context. Replacing this tag with the ID itself gives me a correct
> > > page. So my guess is that the error is somehow related to that tag.
> > >
> > > Here's some data:
> > > the pipelines:
> > >
> > > <map:match pattern="members/memberdata.xml">
> > > <map:generate type="serverpages"
> > src="system/members/getmemberdata.xsp"/>
> > > <map:transform src="test/memberpresentation.xsl"/>
> > > <map:serialize type="xml"/>
> > > </map:match>
> > >
> > > <map:match pattern="members/memberdata.html">
> > > <map:aggregate element="fullpage">
> > > <map:part src="cocoon:/members/top-memberdata"/>
> > > <map:part src="cocoon:/members/menu-memberdata.xml"/>
> > > <map:part src="cocoon:/loginform"/>
> > > <map:part src="cocoon:/members/memberdata.xml"/>
> > > </map:aggregate>
> > > <map:transform src="stylesheets/members/fullpage.xsl"/>
> > > <map:serialize type="html"/>
> > > </map:match>
> > >
> > > The part from the xsp page that generates the user data:
> > >
> > > <esql:connection>
> > > <esql:pool>bvar</esql:pool>
> > > <esql:execute-query>
> > > <esql:query>SELECT * FROM members WHERE ID=<esql:parameter
> > > type="int"><xsp:expr>Integer.parseInt(<xsp-session:getxml
> > > context="authentication" path="/authentication/ID"
> > > as="string"/>)</xsp:expr></esql:parameter></esql:query>
> > > <esql:results>
> > > <esql:row-results>
> > > <esql:get-columns/>
> > > </esql:row-results>
> > > </esql:results>
> > > </esql:execute-query>
> > > </esql:connection>
> > >
> > > I'm almost banging my head on the wall with frustration. What is the
> > > difference between calling a pipeline directly and calling the pipeline
> > > from the sitemap that can cause a nullpointer error???
> > >
> > > The logs show nothing useful. I've been going through them for about an
> > > hour now.
> > >
> > > Please help me, I'm on a deadline and really need this functionality;
> > >
> > > Bert
> > >
> > >
> > > This mail is written in 100% recycled electrons.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > Please check that your question has not already been answered in the
> > > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
> > >
> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > > For additional commands, e-mail: <[EMAIL PROTECTED]>
> > >
> >
> >
> >---------------------------------------------------------------------
> >Please check that your question has not already been answered in the
> >FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
> >
> >To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> >For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
