cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Portal - Coplets / Sunlet
Date Mon, 27 Jan 2003 08:32:53 GMT
Sorry Richard,

I totally forgot to reply...

Including a simple remote source is simple using the cinclude transformer:


<data xmlns:cinclude="http://apache.org/cocoon/include/1.0">
<cinclude:includexml>
    <cinclude:src>http://itsunshine/tamino/blah</cinclude:src>
</cinclude:includexml>
</data>


But, as I understand you right, you want to "embed" a full site in a coplet,
so, you have to maintain the state (= the web page the user currently wants
to see of the embedded site). Which means, you have to store the correct
uri somewhere in the session and do a:

<data xmlns:cinclude="http://apache.org/cocoon/include/1.0">
<cinclude:includexml>
    <cinclude:src>URI_FROM_SESSION</cinclude:src>
</cinclude:includexml>
</data>

You can get and set this URI, e.g. using the session transformer and
the getxml/setxml commands.

However, after you include the external source, you have to rewrite
all links contained in this resource so that they go first to cocoon
because the portal (or precisly the coplet) needs to know which link
the user has clicked in order to include the correct page the
next time the portal is redrawn.
I have not thought abouth how to do this, but I think there were
several people here on the list a while ago who did exactly this
step. Perhaps they can help you more?

HTH
Carsten

Carsten Ziegeler
Open Source Group, S&N AG

> -----Original Message-----
> From: Richard Reyes [mailto:seyer_drahcir@hotmail.com]
> Sent: Monday, January 27, 2003 6:31 AM
> To: cocoon-users@xml.apache.org
> Subject: Re: Portal - Coplets / Sunlet
>
>
>
> Hi Carsten,
>
> Hope you could spare some time to explain on the solution 2 you have
> suggested...
>
> Thanks again
>
>     ================================================
>     ----- Original Message -----
>     From: "Richard Reyes" <seyer_drahcir@hotmail.com>
>     To: <cocoon-users@xml.apache.org>
>     Sent: Friday, January 24, 2003 4:20 PM
>     Subject: Re: Portal - Coplets / Sunlet
>
>
>     > Hi Carsten,
>     >
>     > I am more interested in the second solution, since im planning to
> include
>     > xmlforms as one of coplets
>     > and they would not be delivering xml streams but formatted xhtml's.
> Assuming
>     > these xmlform can run independently on a separate browser.
> Will it be
>     > possible for you to please elaborate on the second solution
> as I am a
>     > beginner in cocoon and I cannot even visualized the idea.
>     >
>     > Thanks a lot.
>     > RICHARD
>     >
>     > ================================================
>     > ----- Original Message -----
>     > From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
>     > To: <cocoon-users@xml.apache.org>
>     > Sent: Friday, January 24, 2003 4:05 PM
>     > Subject: RE: Portal - Coplets / Sunlet
>     >
>     >
>     > > Hi,
>     > >
>     > > yes, this is possible. You can either say that the
> source/content of
> your
>     > > coplet is a remote resource or you can use a local resource that
> includes
>     > > a remote resource.
>     > > First solution: instead of using the cocoon-protocol to
> specify the
> source
>     > > of your coplet, you can say http://..... as long as this remote
> resource
>     > > delivers xml.
>     > > Second solution: you define a local pipeline, using the
> cocoon-protocol
>     > > and either read via the generator the remote resource or use the
>     > > cinclude transformer. With the cinclude transformer you
> can include
>     > > complete sites, like your www.google.com, as they were
> running in a
> frame.
>     > > There will be some minor problems to solve, but it's possible :)
>     > >
>     > > Carsten
>     > >
>
> ---------------------------------------------------------------------
> 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