cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bert Van Kets <b...@vankets.com>
Subject RE: authentication frustration
Date Thu, 31 Oct 2002 11:21:00 GMT
The problem is caused by the bug described below.
A workaround is to add the user data to a session attribute and use that 
one when the data is needed.  The context data is only used by the 
authentication actions :-(

I have a site running with authentication by mySQL database for a member 
section.  On top of this I'm running the portal with xml file 
authentication.  The coplets in the portal give access to the content of 
the different files of the site.  It's actually used as a CMS.  The CMS is 
used by only a handful of people and only one person can access a certain 
part at the same time.  So there is not need for file locking and such and 
the SourceWritingTransfomer can safely be used.

Bert


At 06:02 31/10/2002 -0500, you wrote:
>Sir,
>I understand your frustration.  We have been trying to get authentication
>using that sunRise stuff for over a month now.  One goes down the primrose
>path only to find absolutely nothing - that is called frustration.
>
>Actually, I believe that there is something that we have set incorrectly.
>But, we do not have enough of visibility into the process to determine where
>we have gone astray.  We are still digging, but we are continuing to get
>more of nothing.  And you know how that feels.
>
>Ray
>
> > -----Original Message-----
> > From: Bert Van Kets [mailto:bert@vankets.com]
> > Sent: Wednesday, October 30, 2002 8:45 AM
> > To: cocoon-users@xml.apache.org
> > Subject: Re: authentication frustration
> >
> >
> > Carsten,
> > Any idea when this will be solved?
> >
> > Bert
> >
> > At 14:16 30/10/2002 +0100, you wrote:
> > >apparently it does :(
> > >Any solution around this?
> > >
> > >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:     <cocoon-users-unsubscribe@xml.apache.org>
> > >> > For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>
> > >> >
> > >>
> > >>
> > >>---------------------------------------------------------------------
> > >>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:     <cocoon-users-unsubscribe@xml.apache.org>
> > >>For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>
> > >
> > >
> > >---------------------------------------------------------------------
> > >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:     <cocoon-users-unsubscribe@xml.apache.org>
> > >For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>
> >
> >
> > ---------------------------------------------------------------------
> > 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:     <cocoon-users-unsubscribe@xml.apache.org>
> > For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>
> >
> >
>
>
>
>---------------------------------------------------------------------
>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:     <cocoon-users-unsubscribe@xml.apache.org>
>For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


---------------------------------------------------------------------
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:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message