RE: FW: i18n problem with i18n:attr : ArrayIndexOutOfBoundsException
thx joerg, I tried again to get this work, putting the xalan and xerces jars in jre/lib/endorsed, in tomcats common/endorsed, trying the lates xalan etc. - no way. finally switched to j2sdk 1.4.1_01 and all works ok now. regards, tom -Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Sonntag, 26. Jänner 2003 03:52 To: [EMAIL PROTECTED] Subject: Re: FW: i18n problem with i18n:attr : ArrayIndexOutOfBoundsException Hello Thomas, once upon the time there was a buggy Xerces version having problem with I18n attributes. We had this problem in the Cocoon 2.0.3 release with (I think) Xerces 2.0. After we upgraded the Xerces version everything works ok again. Lines like org.xml.sax.helpers.AttributesImpl.removeAttribute(Attributes Impl.java:439) in your stacktrace let me assume, that it is the same problem you have. Regards, Joerg - 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]
FW: i18n problem with i18n:attr : ArrayIndexOutOfBoundsException
another try to get feedback for my problem: -Original Message- From: Thomas Haselberger Sent: Dienstag, 21. Jänner 2003 10:52 To: Cocoon-Users (E-mail) Subject: i18n problem with i18n:attr : ArrayIndexOutOfBoundsException I use cocoon 2.0.4 in tomcat 4.1.18 with j2sdk1.4.0_03. the i18n samples that use i18n:attr work ok, but my i18n transformation throws an ArrayIndexOutOfBoundsException. this is my source xml: = ?xml version=1.0 encoding=UTF-8? wml xmlns:i18n=http://apache.org/cocoon/i18n/2.0; card i18n:attr=title title=ol id=main p mode=nowrap emi18n:textol/i18n:text/em br/a href=new/1/i18n:textnew/i18n:text/a /p /card /wml = this is my sitemap matcher entry: = !-- i18n test -- map:match pattern=**i18ntest** map:generate src=content/wml_for_i18n.xml/ map:transform type=i18n label=rmns/ map:serialize type=xml/ /map:match = and that's the error log entry generated: = ERROR (2003-01-21) 10:50.44:761 [sitemap] (/idc/i18ntest/bla) Thread-15/sitemap_xmap: Sitemap org.apache.cocoon.ProcessingException: Exception during processing of file:/D:/java/jakarta-tomcat-4.1.18/webapps/idc/content/wml_for_i18n.xml: java.lang.ArrayIndexOutOfBoundsException at org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:214) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:143) at org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java:250) at org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:395) at org.apache.cocoon.www.sitemap_xmap.matchN400126(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1345) at org.apache.cocoon.www.sitemap_xmap.process(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1185) at org.apache.cocoon.www.sitemap_xmap.process(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1128) at org.apache.cocoon.sitemap.Handler.process(Handler.java:227) at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:173) at org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:152) at org.apache.cocoon.Cocoon.process(Cocoon.java:579) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext
i18n problem with i18n:attr : ArrayIndexOutOfBoundsException
) at org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java:250) at org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:395) at org.apache.cocoon.www.sitemap_xmap.matchN400126(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1345) at org.apache.cocoon.www.sitemap_xmap.process(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1185) at org.apache.cocoon.www.sitemap_xmap.process(D:\java\jakarta-tomcat-4.1.18\work\Standalone\localhost\idc\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:1128) at org.apache.cocoon.sitemap.Handler.process(Handler.java:227) at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:173) at org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:152) at org.apache.cocoon.Cocoon.process(Cocoon.java:579) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(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.processConnection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) = any ideas ? thx, tom -- thomas haselberger - 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]
set user agent with request parameter or path element
I'm using the browser selector to display different content depending on the user agent. Now I'd like to set the user agent with a request parameter or path element. eg. url?user_agent=nokia7110 then the user agent should be set to nokia7110 to be used in the browser selector. any hints how to manage that ? thx, tom haselberger - 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: set user agent with request parameter or path element
-Original Message- From: Jörg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 15. Oktober 2002 12:01 To: [EMAIL PROTECTED] Subject: Re: set user agent with request parameter or path element AFAIK the best then is to use is parameter selector, not the browser selector. But so you want the request parameter? Response time because of selecting on every request? Why don't you use a nested selecting: first parameter, if it's not there use browser selector. But if this is really faster? The idea behind that is that my browser selector list will get really long, and I don't want to duplicate that list in a parameter selector. I want to be able to select the content for the pretended user agent but still set the display xslt according to the real user agent. lg, tom - 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: set user agent with request parameter or path element
-Original Message- From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 15. Oktober 2002 15:17 Subject: Re: set user agent with request parameter or path element And why not simply always the browser selector?? let me explain: a user should be able to select a friends user agent in a list and browse the user agent specific content in order to send one item of this content to the friend. but the wml xslt templates should be used for the *real* user agent of the user. so i have 2 transformations: 1. transform the content according to the real user agent OR the faked user agent to filter the user agent specific content. in both cases i want to match against the browser selector map, that contains eg. browser name=content_one useragent=Nokia/ browser name=content_two useragent=Nokia/ browser name=content_two useragent=Ericsson/ 2. transform it according to the real user agent into wml, matching against different entries in the browser selector map: browser name=nokia_wap useragent=Nokia/ browser name=ericsson_wap useragent=Ericsson/ but how can I supply the browser selector with a different user agent ? thx, tom - 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: [newbie] wml serializer
Zein, hope you have a statement like that in the serializer section of your sitemap. then the wml type serialization should work ... - map:serializer logger=sitemap.serializer.wml mime-type=text/vnd.wap.wml name=wml src=org.apache.cocoon.serialization.XMLSerializer - If I put the same file into ~/webapps/cocoon/test/ and write the follwing lines into the sitemap, I receive an empty document map:match pattern=test/test.wml map:generate src=test/test.wml/ map:serialize type=wml/ /map:match If I write map:match pattern=test/test.wml map:generate src=test/test.wml/ map:serialize type=html/ /map:match I receive a file with my wml code. But of course of the html serialization I haven't access to the file with a wap device only with a html browser. - 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: Cocoon confusion
-Original Message-
From: Mauro Daniel Ardolino [mailto:[EMAIL PROTECTED]]
I've created a pipeline to access my welcome.html file like this:
map:match pattern=*.html
map:generate type=file src={1}.html/
map:serialize type=html/
/map:match
hello mauro,
why don't you use a reader instead if you don't do any transformation ?
map:match pattern=*.html
map:read mime-type=text/html src={1}.html/
/map:match
regards,
tom
-
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]
