RE: Portal - Coplets / Sunlet
-Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 9:02 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet which error log? the one thats on the browser? here it is Exactly! Ok, I can see by the log that the xmlizer does not detect that the resource you request is html. I guess this is currently not implemented. I will take care of it as soon as I get some time for it. Thanks 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portal - Coplets / Sunlet
thanks. - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 4:40 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 9:02 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet which error log? the one thats on the browser? here it is Exactly! Ok, I can see by the log that the xmlizer does not detect that the resource you request is html. I guess this is currently not implemented. I will take care of it as soon as I get some time for it. Thanks 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: [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]
RE: Portal - Coplets / Sunlet
Hi Richard, with the latest HEAD CVS your problem is solved. You have to set the mime-type parameter as explained below: data xmlns:cinclude=http://apache.org/cocoon/include/1.0; cinclude:includexml cinclude:srchttp://www.google.com/cinclude:src cinclude:configuration cinclude:parameter cinclude:namemime-type/cinclude:name cinclude:valuetext/html/cinclude:value /cinclude:parameter /cinclude:configuration /cinclude:includexml /data This is a little bit verbose, but it does the trick. What do you think about a deal? I helped you in fixing the problem and you can now enhance the cocoon docs about this new feature in the cinclude transformer. (You don't have to if you don't want). Carsten -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:42 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet thanks. - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 4:40 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 9:02 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet which error log? the one thats on the browser? here it is Exactly! Ok, I can see by the log that the xmlizer does not detect that the resource you request is html. I guess this is currently not implemented. I will take care of it as soon as I get some time for it. Thanks 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: [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]
RE: Portal - Coplets / Sunlet
-Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 8:28 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Hi Carsten,, this is the google.xml, ?xml version=1.0? data xmlns:cinclude=http://apache.org/cocoon/include/1.0; cinclude:includexml cinclude:srchttp://www.google.com/cinclude:src /cinclude:includexml /data and this is the sitemap... map:match pattern=sppasunlet-onlinesundn.xml !-- map:generate src=http://www.s-und-n.de/aktuelles/news.xml/ map:transform src=styles/sunLet_sundnNews.xsl/ -- map:generate src=resources/auth/google.xml/ map:transform type=cinclude/ map:serialize type=xml/ /map:match I have no idea what did i do wrong. I'm soory but what is an xmlizer? xml serializer? How do i configure the xmlizer? It looks OK to me as well...could you provide the error log to see the exception stack trace? The xmlizer is an internal cocoon component that converts for example html to xhtml etc. It is configured in the cocoon.xconf. Search for xmlizer. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portal - Coplets / Sunlet
) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo keNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe linesNode.java:143) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess or.java:317) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess or.java:299) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNod e.java:134) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo keNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invok e(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo keNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel ineNode.java:153) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo keNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe linesNode.java:143) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess or.java:317) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess or.java:299) at org.apache.cocoon.Cocoon.process(Cocoon.java:600) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1104) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:479)=== === - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 3:38 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 8:28 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Hi Carsten,, this is the google.xml, ?xml version=1.0? data xmlns:cinclude=http://apache.org/cocoon
Re: Portal - Coplets / Sunlet
Hi Carsten, I have tried using the cinclude transformer and i got the error below The element type meta must be terminated by the matching end-tag . any ideas? i have checked the google source and it has a tag like this meta http-equiv=content-type content=text/html; charset=UTF-8any workaround? thanks again - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 7:36 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). Yes, exactly. And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? Ah, yes - sorry, I forgot that :) - the cinclude transformer automatically transforms html to xhtml, so you have at the end xml that can easily be included. 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: [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]
RE: Portal - Coplets / Sunlet
There are several possible causes for this problem: - google does not send the correct mime-type (text/html). I can't believe that this is happening, but I'm adding it here for completeness - The xmlizer for text/html is not configured correctly - The xmlizer is not used. For any of the last two problems, it would be helpfull if you could provide the xml document, you used for including and the stacktrace. Carsten -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 9:18 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Hi Carsten, I have tried using the cinclude transformer and i got the error below The element type meta must be terminated by the matching end-tag . any ideas? i have checked the google source and it has a tag like this meta http-equiv=content-type content=text/html; charset=UTF-8any workaround? thanks again - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 7:36 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). Yes, exactly. And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? Ah, yes - sorry, I forgot that :) - the cinclude transformer automatically transforms html to xhtml, so you have at the end xml that can easily be included. 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: [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]
Re: Portal - Coplets / Sunlet
this is the google.xml ?xml version=1.0? data xmlns:cinclude=http://apache.org/cocoon/include/1.0; cinclude:includexml cinclude:srchttp://localhost:8080/cocoon/tsi/home.html/cinclude:src /cinclude:includexml /data and this is the sitemap... map:match pattern=sppasunlet-onlinesundn.xml !-- map:generate src=http://www.s-und-n.de/aktuelles/news.xml/ map:transform src=styles/sunLet_sundnNews.xsl/ -- map:generate src=resources/auth/google.xml/ map:transform type=cinclude/ map:serialize type=xml/ /map:match i have no idea what did i do wrong. thanks richard - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 4:44 PM Subject: RE: Portal - Coplets / Sunlet There are several possible causes for this problem: - google does not send the correct mime-type (text/html). I can't believe that this is happening, but I'm adding it here for completeness - The xmlizer for text/html is not configured correctly - The xmlizer is not used. For any of the last two problems, it would be helpfull if you could provide the xml document, you used for including and the stacktrace. Carsten -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 9:18 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Hi Carsten, I have tried using the cinclude transformer and i got the error below The element type meta must be terminated by the matching end-tag . any ideas? i have checked the google source and it has a tag like this meta http-equiv=content-type content=text/html; charset=UTF-8any workaround? thanks again - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 7:36 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). Yes, exactly. And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? Ah, yes - sorry, I forgot that :) - the cinclude transformer automatically transforms html to xhtml, so you have at the end xml that can easily be included. 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: [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]
RE: Portal - Coplets / Sunlet
this is the google.xml
Richard,
just what exactly is this supposed to show? From what I see you want to
cinclude an html file that is accessed through Cocoon. Correct?
Is /tsi/home.html a pipeline in the sitemap? What does that one do?
Matthew
-
?xml version=1.0?
data xmlns:cinclude=http://apache.org/cocoon/include/1.0;
cinclude:includexml
cinclude:srchttp://localhost:8080/cocoon/tsi/home.html/cinclude:src
/cinclude:includexml
/data
and this is the sitemap...
map:match pattern=sppasunlet-onlinesundn.xml
!--
map:generate src=http://www.s-und-n.de/aktuelles/news.xml/
map:transform src=styles/sunLet_sundnNews.xsl/
--
map:generate src=resources/auth/google.xml/
map:transform type=cinclude/
map:serialize type=xml/
/map:match
--
Open Source Group Cocoon { Consulting, Training, Projects }
=
Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de
-
Cocoon book:
http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20
Weblogs:
http://radio.weblogs.com/0103021/
http://www.oreillynet.com/weblogs/author/1014
=
-Original Message-
From: Richard Reyes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 10:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Portal - Coplets / Sunlet
this is the google.xml
?xml version=1.0?
data xmlns:cinclude=http://apache.org/cocoon/include/1.0;
cinclude:includexml
cinclude:srchttp://localhost:8080/cocoon/tsi/home.html/cinclude:src
/cinclude:includexml
/data
and this is the sitemap...
map:match pattern=sppasunlet-onlinesundn.xml
!--
map:generate src=http://www.s-und-n.de/aktuelles/news.xml/
map:transform src=styles/sunLet_sundnNews.xsl/
--
map:generate src=resources/auth/google.xml/
map:transform type=cinclude/
map:serialize type=xml/
/map:match
i have no idea what did i do wrong.
thanks
richard
- Original Message -
From: Carsten Ziegeler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 28, 2003 4:44 PM
Subject: RE: Portal - Coplets / Sunlet
There are several possible causes for this problem:
- google does not send the correct mime-type (text/html). I can't
believe that this is happening, but I'm adding it here for completeness
- The xmlizer for text/html is not configured correctly
- The xmlizer is not used.
For any of the last two problems, it would be helpfull if you could
provide the xml document, you used for including and the stacktrace.
Carsten
-Original Message-
From: Richard Reyes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 9:18 AM
To: [EMAIL PROTECTED]
Subject: Re: Portal - Coplets / Sunlet
Hi Carsten,
I have tried using the cinclude transformer and i got the error
below
The element type meta must be terminated by the matching end-tag .
any ideas?
i have checked the google source and it has a tag like this
meta http-equiv=content-type content=text/html; charset=UTF-8any
workaround?
thanks again
- Original Message -
From: Carsten Ziegeler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 27, 2003 7:36 PM
Subject: RE: Portal - Coplets / Sunlet
-Original Message-
From: Richard Reyes [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 9:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Portal - Coplets / Sunlet
Thanks for the respond, Carsten.
If I understand it correctly, you were just discussing the links
that'll be
contained in the site that i'll include ( as a coplet ).
Yes, exactly.
And it really sound very complex to me. Anyway, I dont understand
how would the portal draw the coplet if the link that im giving is
giving htmls while the portal require xml streams?
Ah, yes - sorry, I forgot that :) - the cinclude transformer
automatically transforms html to xhtml, so you have at the end xml
that can easily be included.
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: [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
RE: Portal - Coplets / Sunlet
Ok, and where is the problem? Matthew -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 10:52 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet - Original Message - From: Matthew Langham [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 5:42 PM Subject: RE: Portal - Coplets / Sunlet this is the google.xml Richard, just what exactly is this supposed to show? From what I see you want to cinclude an html file that is accessed through Cocoon. Correct? Richard: Yes... Is /tsi/home.html a pipeline in the sitemap? What does that one do? Richard: Yes, it has a corresponding map:match in the sitemap it contains an xmlform that can be independently browsed into a browser. Thanks Matthew... - 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]
Re: Portal - Coplets / Sunlet
I am having this error... The element type meta must be terminated by the matching end-tag . i have checked the html source and it has a tag like this meta http-equiv=content-type content=text/html; charset=UTF-8 - Original Message - From: Matthew Langham [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 5:58 PM Subject: RE: Portal - Coplets / Sunlet Ok, and where is the problem? Matthew -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 10:52 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet - Original Message - From: Matthew Langham [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 5:42 PM Subject: RE: Portal - Coplets / Sunlet this is the google.xml Richard, just what exactly is this supposed to show? From what I see you want to cinclude an html file that is accessed through Cocoon. Correct? Richard: Yes... Is /tsi/home.html a pipeline in the sitemap? What does that one do? Richard: Yes, it has a corresponding map:match in the sitemap it contains an xmlform that can be independently browsed into a browser. Thanks Matthew... - 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]
Re: Portal - Coplets / Sunlet
Hi Carsten,, this is the google.xml, ?xml version=1.0? data xmlns:cinclude=http://apache.org/cocoon/include/1.0; cinclude:includexml cinclude:srchttp://www.google.com/cinclude:src /cinclude:includexml /data and this is the sitemap... map:match pattern=sppasunlet-onlinesundn.xml !-- map:generate src=http://www.s-und-n.de/aktuelles/news.xml/ map:transform src=styles/sunLet_sundnNews.xsl/ -- map:generate src=resources/auth/google.xml/ map:transform type=cinclude/ map:serialize type=xml/ /map:match I have no idea what did i do wrong. I'm soory but what is an xmlizer? xml serializer? How do i configure the xmlizer? thanks richard - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 4:44 PM Subject: RE: Portal - Coplets / Sunlet There are several possible causes for this problem: - google does not send the correct mime-type (text/html). I can't believe that this is happening, but I'm adding it here for completeness - The xmlizer for text/html is not configured correctly - The xmlizer is not used. For any of the last two problems, it would be helpfull if you could provide the xml document, you used for including and the stacktrace. Carsten -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 9:18 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Hi Carsten, I have tried using the cinclude transformer and i got the error below The element type meta must be terminated by the matching end-tag . any ideas? i have checked the google source and it has a tag like this meta http-equiv=content-type content=text/html; charset=UTF-8any workaround? thanks again - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 7:36 PM Subject: RE: Portal - Coplets / Sunlet -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). Yes, exactly. And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? Ah, yes - sorry, I forgot that :) - the cinclude transformer automatically transforms html to xhtml, so you have at the end xml that can easily be included. 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: [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]
RE: Portal - Coplets / Sunlet
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:srchttp://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:srcURI_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, SN AG -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 6:31 AM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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: [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]
Re: Portal - Coplets / Sunlet
Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? thanks again richard == - Original Message - From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 4:32 PM Subject: RE: Portal - Coplets / Sunlet 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:srchttp://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:srcURI_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, SN AG -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 6:31 AM To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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: [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
RE: Portal - Coplets / Sunlet
-Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Portal - Coplets / Sunlet Thanks for the respond, Carsten. If I understand it correctly, you were just discussing the links that'll be contained in the site that i'll include ( as a coplet ). Yes, exactly. And it really sound very complex to me. Anyway, I dont understand how would the portal draw the coplet if the link that im giving is giving htmls while the portal require xml streams? Ah, yes - sorry, I forgot that :) - the cinclude transformer automatically transforms html to xhtml, so you have at the end xml that can easily be included. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Carsten Ziegeler Open Source Group, SN AG -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 7:39 AM To: cocoon-users Subject: Portal - Coplets / Sunlet Hi Guys, Will it be possible for a coplet to contain an external resource (for example is http://www.google.com )? And this resource that will need no more transformations and can be very independent like its in a another frame? Thanks in advance Richard - 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]
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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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 Carsten Ziegeler Open Source Group, SN AG -Original Message- From: Richard Reyes [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 7:39 AM To: cocoon-users Subject: Portal - Coplets / Sunlet Hi Guys, Will it be possible for a coplet to contain an external resource (for example is http://www.google.com )? And this resource that will need no more transformations and can be very independent like its in a another frame? Thanks in advance Richard - 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]
Re: Portal - Coplets / Sunlet
Hi Guys, Can I also use a separate cocoon application for my coplet where all its transformation is in a separate sitemap? For example... I have cocoon\myportal as my portal application and i would use a independent cocoon application like cocoon\webapp1 as one of my coplet? Is this possible...please help. Thanks - Original Message - From: Richard Reyes To: cocoon-users Sent: Friday, January 24, 2003 2:39 PM Subject: Portal - Coplets / Sunlet Hi Guys, Will it be possible for a coplet to contain an external resource (for example is http://www.google.com)? And this resource that will need no more transformations and can be very independent like its in a another frame? Thanks in advance Richard
