You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Ivelin Ivanov <iv...@apache.org> on 2002/07/04 23:35:09 UTC
[Announcement] Embedding One Web Site in Another with Cocoon (new Component)
+=====================================================+
| |
| New Cocoon Generator |
| |
| allows integration of content and behavior |
| |
between remote web sites. |
| |
+=====================================================+
For quite some time web sites are exchanging news feeds and other one way
content via RSS. Some portals are even outsourcing and co-branding web
applications.
As appealing and feasible as this may seem, most of today's implementations
are quite rugged.
Let's follow a typical scenario:
User logs in to a familiar portal and happily browses around.
At some point the user clicks on a link which leads to a strange page.
It has the portal logo, might even show the user login id but looks very
different and unfamiliar... After some time and frustration the user gets
used to switching back and forth between the two faces of the portal...
while looking for another provider which offers both services in a coherent
graphical interface.
This story is not uncommon and is an inherent problem with the traditional
HTML based publishing.
Outsourcing interactive components to a third party site, while preserving
the look & feel of the original portal is still possible when done right.
Cocoon has a solution.
The new Web Service Proxy component is built to help with this very problem.
Once plugged in the sitemap, it transparently pipes browser requests to a
remote web app and returns the response back to the sitemap.
WebServiceProxyGenerator is available in Cocoon 2.1-dev HEAD.
To try the demo, build the latest CVS HEAD code and point to:
http://localhost:8080/cocoon/samples/webserviceproxy/
More for the component (from the demo page):
-----------------------------------------------
WebServiceProxyGenerator combined with the XMLForm framework and XSLT,
allows vendors to share interactive content with little effort.
The Web Service Proxy takes advantage of the fact that a Cocoon web
application produces XML content which is later translated into multiple
presentation formats, like HTML or WML.
The demo embeds the Cocoon Feedback Wizard application, which produces an
XML view containing both static data and interactive forms. Having a client
independent content format, allows this view to be pulled to the embedding
web site (this demo) and styled with XSLT in the Look & Feel of the site.
Ok, styling presentation is easy to understand, but how is a form submitted
to the original site?
Since the form markup in the XML content of an embedded page uses relative
URL address for the target, once the end user submits, the form data is sent
to the containing site, which captures the form data and the relative URL.
The Web Service Proxy then takes this information and re-submits it to the
original site. It then reads the XML response and makes it available to the
sitemap for styling again.
Hm, but the Feedback Wizard example maintains a session while going through
multiple pages. So, how is the containing site propagating the end user
session to the to the embedded site?
The answer is simple. The Web Service Proxy simply hooks to the end user
session, and automatically starts its own session with the remote site. If
the remote site does not require authentication, then everything is
transparent to the developer of the containing web site. Otherwise the
WebServiceProxyGenerator has to be extended to override the procedure for
imitating session with the remote site.
What transport protocols are supported?
HTTP 1.0, HTTP 1.1, HTTPS.
Have more questions? Look at the code, it is really simple. If you need
advise, search through the Cocoon mailing lists archives. If you can't find
the answer, email your question to the Cocoon mailing lists. Finally, if you
need to contact me, send email to Ivelin Ivanov, ivelin@apache.org.
If you like this component, please help with documentation. Write an FAQ,
HOW-TO or User Guide.
------------- End of overview ------------
I am hoping to see this component used in Ugo's CocoBlog app and possibly
Carsten and Matthew's portal apps.
I also feel that it provides solution to some of the problems we were
recently addressing with Cocoon Blocks.
Stay tuned for more exciting news ... ;)
Enjoy,
Ivelin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Feature of esql:get-xml?
Posted by Michael Wechner <mi...@wyona.org>.
Diana Shannon wrote:
>
> On Friday, July 5, 2002, at 07:04 AM, Christian Haul wrote:
>
>>> ok, I started to write a little docu on the usage of hsqldb and esql:
>>> http://194.191.122.220:8080/wyona-cms/docs/xdocs/hsqldb.html
>>>
>>> Maybe people from Cocoon can use certain parts of it if they want
>>>
>
> Thanks! Just let us know when you think it's more or less finished, and
> we'll add it to the Cocoon documentation. Submit a patch via Bugzilla.
> Check the How-Tos if you don't know how. Post to the list if you have
> any problems submitting.
ok, I will do that. If people have some input with regard to content,
just let me know.
Michael
>
> Thanks.
>
> Diana
>
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Feature of esql:get-xml?
Posted by Diana Shannon <sh...@apache.org>.
On Friday, July 5, 2002, at 07:04 AM, Christian Haul wrote:
>> ok, I started to write a little docu on the usage of hsqldb and esql:
>> http://194.191.122.220:8080/wyona-cms/docs/xdocs/hsqldb.html
>>
>> Maybe people from Cocoon can use certain parts of it if they want
>>
Thanks! Just let us know when you think it's more or less finished, and
we'll add it to the Cocoon documentation. Submit a patch via Bugzilla.
Check the How-Tos if you don't know how. Post to the list if you have
any problems submitting.
Thanks.
Diana
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Feature of esql:get-xml?
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 05.Jul.2002 -- 11:13 AM, Michael Wechner wrote:
> Christian Haul wrote:
> >On 05.Jul.2002 -- 02:40 AM, Michael Wechner wrote:
> >It needs to be well-formed XML. But you can add a root element:
> >
> ><esql:get-xml column="name" root="root"/>
> >
>
> Thanks a lot for your help. I actually saw something similar on the
> mailing list, but I was too stupid to understand it.
>
> >Please follow up summarizing your problem and which suggested solution
>
> ok, I started to write a little docu on the usage of hsqldb and esql:
> http://194.191.122.220:8080/wyona-cms/docs/xdocs/hsqldb.html
>
> Maybe people from Cocoon can use certain parts of it if they want
Great!
One more thing: If the snippet in the database uses namespaces, it is
not sufficiant to declare them in the XSP. Reason: The database
content is parsed by a different XML parser which does not inherit
namespace declarations from the XSP itself.
Solution: Namespaces need to be declared in the snippet as well. A
solution could be to hack esql.xsl to automatically include all
namespaces from the XSP, but that is not completely desirable because
of the NS of taglibs.
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Feature of esql:get-xml?
Posted by Michael Wechner <mi...@wyona.org>.
Christian Haul wrote:
> On 05.Jul.2002 -- 02:40 AM, Michael Wechner wrote:
>
>>Dear Group
>>
>>I am starting to use hsqldb for some parts of Wyona.
>>
>>I had problems returning XML/XHTML from a table field,
>>for instance
>>
>>DESCRIPTION : 'Cocoon is <emphasize>great</emphasize>'
>>
>>when I used esql:get-xml then I just received nothing, resp.
>><description/>
>>
>>but when I embed the "mixed content" within some XML tag:
>>
>>DESCRIPTION: '<para>Cocoon is <emphasize>great</emphasize></para>'
>>
>>then everything is fine.
>>
>>Is this a feature or did I miss something in the documentation?
>>
>
> It needs to be well-formed XML. But you can add a root element:
>
> <esql:get-xml root="root"/>
>
> And suddenly you're OK :-)
>
> Chris.
Thanks a lot for your help. I actually saw something similar on the
mailing list, but I was too stupid to understand it.
>
> Please follow up summarizing your problem and which suggested solution
> / information worked for you when you consider your problem
> solved. Add "SUMMARY: " to the subject line. This will make FAQ
> generation and searching the list easier. In addition, it makes
> helping you more fun. Thank you.
ok, I started to write a little docu on the usage of hsqldb and esql:
http://194.191.122.220:8080/wyona-cms/docs/xdocs/hsqldb.html
Maybe people from Cocoon can use certain parts of it if they want
Thanks
Michael
>
>
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Feature of esql:get-xml?
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 05.Jul.2002 -- 02:40 AM, Michael Wechner wrote:
> Dear Group
>
> I am starting to use hsqldb for some parts of Wyona.
>
> I had problems returning XML/XHTML from a table field,
> for instance
>
> DESCRIPTION : 'Cocoon is <emphasize>great</emphasize>'
>
> when I used esql:get-xml then I just received nothing, resp.
> <description/>
>
> but when I embed the "mixed content" within some XML tag:
>
> DESCRIPTION: '<para>Cocoon is <emphasize>great</emphasize></para>'
>
> then everything is fine.
>
> Is this a feature or did I miss something in the documentation?
It needs to be well-formed XML. But you can add a root element:
<esql:get-xml root="root"/>
And suddenly you're OK :-)
Chris.
Please follow up summarizing your problem and which suggested solution
/ information worked for you when you consider your problem
solved. Add "SUMMARY: " to the subject line. This will make FAQ
generation and searching the list easier. In addition, it makes
helping you more fun. Thank you.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Feature of esql:get-xml?
Posted by Michael Wechner <mi...@wyona.org>.
Dear Group
I am starting to use hsqldb for some parts of Wyona.
I had problems returning XML/XHTML from a table field,
for instance
DESCRIPTION : 'Cocoon is <emphasize>great</emphasize>'
when I used esql:get-xml then I just received nothing, resp.
<description/>
but when I embed the "mixed content" within some XML tag:
DESCRIPTION: '<para>Cocoon is <emphasize>great</emphasize></para>'
then everything is fine.
Is this a feature or did I miss something in the documentation?
You can find a more complete example here (CocoBlog with "para" and all
the others without "para"):
http://194.191.122.220:8080/wyona-cms/wyona.org/related-projects/list.xml
http://194.191.122.220:8080/wyona-cms/wyona.org/related-projects/index.html
Thanks
Michael
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: [Announcement] Embedding One Web Site in Another with Cocoon (new Component)
Posted by Ivelin Ivanov <iv...@apache.org>.
I haven't had time to implement the Amazon xsl.
I could use some help with it.
Any takers?
Ivelin
----- Original Message -----
From: "Christopher Watson" <c....@zen.co.uk>
To: <co...@xml.apache.org>
Sent: Friday, July 05, 2002 4:20 AM
Subject: RE: [Announcement] Embedding One Web Site in Another with Cocoon
(new Component)
> Ivelin
>
> Impressive !
>
> In your readme.txt you mention some xsl files ...
> amazonform2html.xsl
> AmazonForm2html.xsl
>
> Thanks for including AmazonForm.xml in the text of the readme.
> Could you include or email the .xsl files named above
>
> Thanks
>
> Christopher
>
>
> > -----Original Message-----
> > From: Ivelin Ivanov [mailto:ivelin@apache.org]
> > Sent: 04 July 2002 22:35
> > To: cocoon-dev@xml.apache.org
> > Cc: cocoon-users@xml.apache.org
> > Subject: [Announcement] Embedding One Web Site in Another with Cocoon
> > (new Component)
> >
> >
> > +=====================================================+
> > | |
> > | New Cocoon Generator |
> > | |
> > | allows integration of content and behavior |
> > | |
> > between remote web sites. |
> > | |
> > +=====================================================+
> >
> >
> > For quite some time web sites are exchanging news feeds and other one
way
> > content via RSS. Some portals are even outsourcing and co-branding web
> > applications.
> > As appealing and feasible as this may seem, most of today's
> > implementations
> > are quite rugged.
> >
> > Let's follow a typical scenario:
> > User logs in to a familiar portal and happily browses around.
> > At some point the user clicks on a link which leads to a strange page.
> > It has the portal logo, might even show the user login id but looks very
> > different and unfamiliar... After some time and frustration the user
gets
> > used to switching back and forth between the two faces of the portal...
> > while looking for another provider which offers both services in
> > a coherent
> > graphical interface.
> >
> > This story is not uncommon and is an inherent problem with the
traditional
> > HTML based publishing.
> >
> > Outsourcing interactive components to a third party site, while
preserving
> > the look & feel of the original portal is still possible when done
right.
> > Cocoon has a solution.
> >
> > The new Web Service Proxy component is built to help with this
> > very problem.
> > Once plugged in the sitemap, it transparently pipes browser requests to
a
> > remote web app and returns the response back to the sitemap.
> >
> > WebServiceProxyGenerator is available in Cocoon 2.1-dev HEAD.
> > To try the demo, build the latest CVS HEAD code and point to:
> >
> > http://localhost:8080/cocoon/samples/webserviceproxy/
> >
> >
> > More for the component (from the demo page):
> > -----------------------------------------------
> >
> > WebServiceProxyGenerator combined with the XMLForm framework and XSLT,
> > allows vendors to share interactive content with little effort.
> > The Web Service Proxy takes advantage of the fact that a Cocoon web
> > application produces XML content which is later translated into multiple
> > presentation formats, like HTML or WML.
> >
> > The demo embeds the Cocoon Feedback Wizard application, which produces
an
> > XML view containing both static data and interactive forms.
> > Having a client
> > independent content format, allows this view to be pulled to the
embedding
> > web site (this demo) and styled with XSLT in the Look & Feel of the
site.
> >
> > Ok, styling presentation is easy to understand, but how is a form
> > submitted
> > to the original site?
> > Since the form markup in the XML content of an embedded page uses
relative
> > URL address for the target, once the end user submits, the form
> > data is sent
> > to the containing site, which captures the form data and the relative
URL.
> > The Web Service Proxy then takes this information and re-submits it to
the
> > original site. It then reads the XML response and makes it
> > available to the
> > sitemap for styling again.
> >
> > Hm, but the Feedback Wizard example maintains a session while
> > going through
> > multiple pages. So, how is the containing site propagating the end user
> > session to the to the embedded site?
> > The answer is simple. The Web Service Proxy simply hooks to the end user
> > session, and automatically starts its own session with the remote site.
If
> > the remote site does not require authentication, then everything is
> > transparent to the developer of the containing web site. Otherwise the
> > WebServiceProxyGenerator has to be extended to override the procedure
for
> > imitating session with the remote site.
> >
> > What transport protocols are supported?
> > HTTP 1.0, HTTP 1.1, HTTPS.
> >
> > Have more questions? Look at the code, it is really simple. If you need
> > advise, search through the Cocoon mailing lists archives. If you
> > can't find
> > the answer, email your question to the Cocoon mailing lists.
> > Finally, if you
> > need to contact me, send email to Ivelin Ivanov, ivelin@apache.org.
> >
> > If you like this component, please help with documentation. Write an
FAQ,
> > HOW-TO or User Guide.
> >
> >
> >
> > ------------- End of overview ------------
> >
> >
> >
> > I am hoping to see this component used in Ugo's CocoBlog app and
possibly
> > Carsten and Matthew's portal apps.
> >
> > I also feel that it provides solution to some of the problems we were
> > recently addressing with Cocoon Blocks.
> >
> >
> >
> > Stay tuned for more exciting news ... ;)
> >
> >
> >
> > Enjoy,
> >
> > Ivelin
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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: <co...@xml.apache.org>
> > For additional commands, e-mail: <co...@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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: [Announcement] Embedding One Web Site in Another with Cocoon (new Component)
Posted by Ivelin Ivanov <iv...@apache.org>.
I haven't had time to implement the Amazon xsl.
I could use some help with it.
Any takers?
Ivelin
----- Original Message -----
From: "Christopher Watson" <c....@zen.co.uk>
To: <co...@xml.apache.org>
Sent: Friday, July 05, 2002 4:20 AM
Subject: RE: [Announcement] Embedding One Web Site in Another with Cocoon
(new Component)
> Ivelin
>
> Impressive !
>
> In your readme.txt you mention some xsl files ...
> amazonform2html.xsl
> AmazonForm2html.xsl
>
> Thanks for including AmazonForm.xml in the text of the readme.
> Could you include or email the .xsl files named above
>
> Thanks
>
> Christopher
>
>
> > -----Original Message-----
> > From: Ivelin Ivanov [mailto:ivelin@apache.org]
> > Sent: 04 July 2002 22:35
> > To: cocoon-dev@xml.apache.org
> > Cc: cocoon-users@xml.apache.org
> > Subject: [Announcement] Embedding One Web Site in Another with Cocoon
> > (new Component)
> >
> >
> > +=====================================================+
> > | |
> > | New Cocoon Generator |
> > | |
> > | allows integration of content and behavior |
> > | |
> > between remote web sites. |
> > | |
> > +=====================================================+
> >
> >
> > For quite some time web sites are exchanging news feeds and other one
way
> > content via RSS. Some portals are even outsourcing and co-branding web
> > applications.
> > As appealing and feasible as this may seem, most of today's
> > implementations
> > are quite rugged.
> >
> > Let's follow a typical scenario:
> > User logs in to a familiar portal and happily browses around.
> > At some point the user clicks on a link which leads to a strange page.
> > It has the portal logo, might even show the user login id but looks very
> > different and unfamiliar... After some time and frustration the user
gets
> > used to switching back and forth between the two faces of the portal...
> > while looking for another provider which offers both services in
> > a coherent
> > graphical interface.
> >
> > This story is not uncommon and is an inherent problem with the
traditional
> > HTML based publishing.
> >
> > Outsourcing interactive components to a third party site, while
preserving
> > the look & feel of the original portal is still possible when done
right.
> > Cocoon has a solution.
> >
> > The new Web Service Proxy component is built to help with this
> > very problem.
> > Once plugged in the sitemap, it transparently pipes browser requests to
a
> > remote web app and returns the response back to the sitemap.
> >
> > WebServiceProxyGenerator is available in Cocoon 2.1-dev HEAD.
> > To try the demo, build the latest CVS HEAD code and point to:
> >
> > http://localhost:8080/cocoon/samples/webserviceproxy/
> >
> >
> > More for the component (from the demo page):
> > -----------------------------------------------
> >
> > WebServiceProxyGenerator combined with the XMLForm framework and XSLT,
> > allows vendors to share interactive content with little effort.
> > The Web Service Proxy takes advantage of the fact that a Cocoon web
> > application produces XML content which is later translated into multiple
> > presentation formats, like HTML or WML.
> >
> > The demo embeds the Cocoon Feedback Wizard application, which produces
an
> > XML view containing both static data and interactive forms.
> > Having a client
> > independent content format, allows this view to be pulled to the
embedding
> > web site (this demo) and styled with XSLT in the Look & Feel of the
site.
> >
> > Ok, styling presentation is easy to understand, but how is a form
> > submitted
> > to the original site?
> > Since the form markup in the XML content of an embedded page uses
relative
> > URL address for the target, once the end user submits, the form
> > data is sent
> > to the containing site, which captures the form data and the relative
URL.
> > The Web Service Proxy then takes this information and re-submits it to
the
> > original site. It then reads the XML response and makes it
> > available to the
> > sitemap for styling again.
> >
> > Hm, but the Feedback Wizard example maintains a session while
> > going through
> > multiple pages. So, how is the containing site propagating the end user
> > session to the to the embedded site?
> > The answer is simple. The Web Service Proxy simply hooks to the end user
> > session, and automatically starts its own session with the remote site.
If
> > the remote site does not require authentication, then everything is
> > transparent to the developer of the containing web site. Otherwise the
> > WebServiceProxyGenerator has to be extended to override the procedure
for
> > imitating session with the remote site.
> >
> > What transport protocols are supported?
> > HTTP 1.0, HTTP 1.1, HTTPS.
> >
> > Have more questions? Look at the code, it is really simple. If you need
> > advise, search through the Cocoon mailing lists archives. If you
> > can't find
> > the answer, email your question to the Cocoon mailing lists.
> > Finally, if you
> > need to contact me, send email to Ivelin Ivanov, ivelin@apache.org.
> >
> > If you like this component, please help with documentation. Write an
FAQ,
> > HOW-TO or User Guide.
> >
> >
> >
> > ------------- End of overview ------------
> >
> >
> >
> > I am hoping to see this component used in Ugo's CocoBlog app and
possibly
> > Carsten and Matthew's portal apps.
> >
> > I also feel that it provides solution to some of the problems we were
> > recently addressing with Cocoon Blocks.
> >
> >
> >
> > Stay tuned for more exciting news ... ;)
> >
> >
> >
> > Enjoy,
> >
> > Ivelin
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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: <co...@xml.apache.org>
> > For additional commands, e-mail: <co...@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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [Announcement] Embedding One Web Site in Another with Cocoon (new Component)
Posted by Christopher Watson <c....@zen.co.uk>.
Ivelin
Impressive !
In your readme.txt you mention some xsl files ...
amazonform2html.xsl
AmazonForm2html.xsl
Thanks for including AmazonForm.xml in the text of the readme.
Could you include or email the .xsl files named above
Thanks
Christopher
> -----Original Message-----
> From: Ivelin Ivanov [mailto:ivelin@apache.org]
> Sent: 04 July 2002 22:35
> To: cocoon-dev@xml.apache.org
> Cc: cocoon-users@xml.apache.org
> Subject: [Announcement] Embedding One Web Site in Another with Cocoon
> (new Component)
>
>
> +=====================================================+
> | |
> | New Cocoon Generator |
> | |
> | allows integration of content and behavior |
> | |
> between remote web sites. |
> | |
> +=====================================================+
>
>
> For quite some time web sites are exchanging news feeds and other one way
> content via RSS. Some portals are even outsourcing and co-branding web
> applications.
> As appealing and feasible as this may seem, most of today's
> implementations
> are quite rugged.
>
> Let's follow a typical scenario:
> User logs in to a familiar portal and happily browses around.
> At some point the user clicks on a link which leads to a strange page.
> It has the portal logo, might even show the user login id but looks very
> different and unfamiliar... After some time and frustration the user gets
> used to switching back and forth between the two faces of the portal...
> while looking for another provider which offers both services in
> a coherent
> graphical interface.
>
> This story is not uncommon and is an inherent problem with the traditional
> HTML based publishing.
>
> Outsourcing interactive components to a third party site, while preserving
> the look & feel of the original portal is still possible when done right.
> Cocoon has a solution.
>
> The new Web Service Proxy component is built to help with this
> very problem.
> Once plugged in the sitemap, it transparently pipes browser requests to a
> remote web app and returns the response back to the sitemap.
>
> WebServiceProxyGenerator is available in Cocoon 2.1-dev HEAD.
> To try the demo, build the latest CVS HEAD code and point to:
>
> http://localhost:8080/cocoon/samples/webserviceproxy/
>
>
> More for the component (from the demo page):
> -----------------------------------------------
>
> WebServiceProxyGenerator combined with the XMLForm framework and XSLT,
> allows vendors to share interactive content with little effort.
> The Web Service Proxy takes advantage of the fact that a Cocoon web
> application produces XML content which is later translated into multiple
> presentation formats, like HTML or WML.
>
> The demo embeds the Cocoon Feedback Wizard application, which produces an
> XML view containing both static data and interactive forms.
> Having a client
> independent content format, allows this view to be pulled to the embedding
> web site (this demo) and styled with XSLT in the Look & Feel of the site.
>
> Ok, styling presentation is easy to understand, but how is a form
> submitted
> to the original site?
> Since the form markup in the XML content of an embedded page uses relative
> URL address for the target, once the end user submits, the form
> data is sent
> to the containing site, which captures the form data and the relative URL.
> The Web Service Proxy then takes this information and re-submits it to the
> original site. It then reads the XML response and makes it
> available to the
> sitemap for styling again.
>
> Hm, but the Feedback Wizard example maintains a session while
> going through
> multiple pages. So, how is the containing site propagating the end user
> session to the to the embedded site?
> The answer is simple. The Web Service Proxy simply hooks to the end user
> session, and automatically starts its own session with the remote site. If
> the remote site does not require authentication, then everything is
> transparent to the developer of the containing web site. Otherwise the
> WebServiceProxyGenerator has to be extended to override the procedure for
> imitating session with the remote site.
>
> What transport protocols are supported?
> HTTP 1.0, HTTP 1.1, HTTPS.
>
> Have more questions? Look at the code, it is really simple. If you need
> advise, search through the Cocoon mailing lists archives. If you
> can't find
> the answer, email your question to the Cocoon mailing lists.
> Finally, if you
> need to contact me, send email to Ivelin Ivanov, ivelin@apache.org.
>
> If you like this component, please help with documentation. Write an FAQ,
> HOW-TO or User Guide.
>
>
>
> ------------- End of overview ------------
>
>
>
> I am hoping to see this component used in Ugo's CocoBlog app and possibly
> Carsten and Matthew's portal apps.
>
> I also feel that it provides solution to some of the problems we were
> recently addressing with Cocoon Blocks.
>
>
>
> Stay tuned for more exciting news ... ;)
>
>
>
> Enjoy,
>
> Ivelin
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>