> From: Ruth, Thomas {PDBI~Basel} [mailto:[EMAIL PROTECTED]]
>
> Thanks Vadim
> yes you are right. It this cookie handling of Cocoon I don't know what
to do.
> Any additional tips?
Nothing to add - you have to extend URLSource implementation. It does
not have cookie management functionality like browsers have.
If you don't want to implement this by yourself, take a look at
different HTTP client libraries out there. May be (just guessing)
commons-httpclient library will help. Right now URLSource is implemented
on top of java.net.URL.
Vadim
> Thanks
> Thomas
>
>
>
> > From: Luca Morandini [mailto:[EMAIL PROTECTED]]
> >
> > Thomas,
> >
> > I know this will sound rather naive but... did you look into the
> cookie
> > logicsheet ?
>
> Unfortunately, this won't help him. He wants to act Cocoon as a client
> to Livelink and manage cookies sent by Livelink on Cocoon side (like
> usual browser does).
>
> I would say that this requires patching of URLSource which is
> responsible for handling external HTTP sources, and adding cookie
> management capabilities to in.
>
>
> Vadim
>
> --
> Resistance is futile.
>
>
> > Best regards,
> >
> > ---------------------------------------------
> > Luca Morandini
> > GIS Consultant
> > [EMAIL PROTECTED]
> > http://utenti.tripod.it/lmorandini/index.html
> > ---------------------------------------------
> >
> >
> -----Original Message-----
> From: Ruth, Thomas {PDBI~Basel}
> Sent: Saturday, May 04, 2002 6:10 PM
> To: '[EMAIL PROTECTED]'
> Subject: Cocoon and cokies
>
>
> Hi all
> we have introduced a new Intranet portal framework in our organization
(very
> successful for around 3000+ users). This portal framework is based on
two
> components. Cocoon2 and Livelink (a CMS from Opentext). We use
Livelink as the
> data entry tool for users. Livelink is already well known in the
organization
> so we reuse this tool. As Livelink offers a function to export
metadata to XML
> we use this and publish the relevant data to the Cocoon2 environment.
This is
> a real publishing process, content managers maintain data and at one
point in
> time they publish. So we publish the data on demand and present on the
portal
> whatever we do with the data using XSLT (and other features from
Cocoon).
> The export of the data can be triggered by using http request from any
> browser. Something like:
> http://livelink/id=12345&objaction=xmlexport&scope=sub&attributeinfo.
This
> generates a XML file (if already logged in). If I am not logged into
Livelink,
> I get a prompt and can provide my username/password. Livelink uses
cockie to
> handle the session and priviliges.
> I can also provide username/password in the URI
> http://livelink/func=ll.login&username=XXX&password=YYY. This works
from a
> browser. Livelink is recognizing the request does a login, sets the
cockie at
> the client browser by sending a page using the meta tag redirect.
> As we have such a great success in using this framework (Thanks to all
of you
> who have participated in building Cocoon2!!!) we now want to go a step
further
> and generate the XML file on request by the portal user.
> So the sitemap shall have an entry like
> <map:aggregate element="live">
> <map:part
>
src="http://livelink/livelink.exe?func=ll.login&username=xxx&pas
sword=
> yyy"/>
> <map:part
>
src="http://livelink/livelink.exe?func=ll&objAction=XMLExport&ob
jId=61
> 52797&attributeinfo&scope=one"/>
> </map:aggregate>
>
> This is working when sending these two http requests from an browser,
with the
> first request setting the cookie, so the second request gets
'through'.
>
> I have no idea on how we would do this in using Cocoon2. Any idea? How
can
> Cocoon handle cookies? Does anyone know?
>
> Thanks for any help
> Thomas Ruth
> [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.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/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
