AW: [opencms-dev] problems editing content-files in opencms 5.0 beta1 SOLVED!!!

["Bührle, Martin, FCI1"]

HI Michael,

we changed everything as suggested, but still got the same error:
============================================================================
============================
16:00:08] <opencms_critical> [CmsXmlTemplateFile] Cannot parse XML file
"/content/templates/gscontent4". org.xml.sax.SAXParseException: An invalid
XML character (Unicode: 0xfc) was found in the CDATA section.
[02.09.2002 16:00:08] <opencms_critical> [CmsXmlTemplateFile] Cannot parse
XML file "/content/templates/gscontent4". org.xml.sax.SAXParseException: An
invalid XML character (Unicode: 0xfc) was found in the CDATA section.
============================================================================
============================

As we checked the templates again, we found the solution to this behaviour
of the parser:
We used german "umlaute" in the COMMENT-sections of the XML-templates. 
Thats all. 
After substitution of these characters everything worked.

Just for Your information.


Best regards!
 Martin

_________________________________________________________________________
Martin Buehrle, FCI1
EADS - European Aeronautic Defence and Space Company
Telefax: +49 89 3179-8927
eMail: Martin.Buehrle at lfk.eads.net
_________________________________________________________________________



> -----Ursprüngliche Nachricht-----
> Von:	Michael Emmerich [SMTP:Michael.Emmerich at framfab.de]
> Gesendet am:	Freitag, 30. August 2002 08:33
> An:	'opencms-dev at www.opencms.org'
> Betreff:	AW: [opencms-dev] problems editing content-files in opencms
> 5.0  beta1
> 
> Martin,
> 
> OpenCms 5.0 uses a different kind of character encoding than the previous
> versions (which will be fully implementet in the 5.0 final). 
> So take a look at your XML-Templates and check the encoding. If your
> current
> Templates are encoded 
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> 
> or 
> 
> <?xml version="1.0"?>
> 
> please change it to:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> 
> and you should not get the error message again.
> The fastest thing to do this is to unzip the export file on your local
> disc,
> make a global search and repalce on it and zip it again.
> 
> Regards,
> 	Michael Emmerich
> 
> -----Ursprüngliche Nachricht-----
> Von: "Bührle, Martin, FCI1" [mailto:martin.buehrle at lfk.eads.net]
> Gesendet: Donnerstag, 29. August 2002 20:09
> An: 'opencms-dev at www.opencms.org'
> Betreff: [opencms-dev] problems editing content-files in opencms 5.0
> beta1
> 
> 
> Hi everybody,
> 
> 
> we have installed the new beta1 of opencms 5.0 on tomcat 4.0.4 and 4.1.9.
> 
> After importing our web-content-files to test everything it is not
> possible
> to EDIT (WYSIWYG-Editor) any of the files.
> There is a detailed error:
> ==========================================================================
> ==
> =======
> [CmsException]: 21 XML parsing error. Detailed Error: Cannot parse XML
> file
> "/content/templates/privatcontent". org.xml.sax.SAXParseException: An
> invalid XML character (Unicode: 0xfc) was found in the CDATA section.. 
> 	at
> com.opencms.template.A_CmsXmlContent.throwException(A_CmsXmlContent.java:1
> 86
> 9)
> 	at
> com.opencms.template.A_CmsXmlContent.parse(A_CmsXmlContent.java:1270)
> 	at
> com.opencms.template.A_CmsXmlContent.parse(A_CmsXmlContent.java:1237)
> 	at
> com.opencms.template.A_CmsXmlContent.init(A_CmsXmlContent.java:1038)
> 	at
> com.opencms.template.CmsXmlTemplateFile.<init>(CmsXmlTemplateFile.java:91)
> 	at
> com.opencms.template.CmsXmlTemplate.getOwnTemplateFile(CmsXmlTemplate.java
> :3
> 82)
> 	at
> com.opencms.workplace.CmsXmlTemplateEditor.getContent(CmsXmlTemplateEditor
> .j
> ava:455)
> 	at
> com.opencms.template.cache.CmsElementXml.getContent(CmsElementXml.java:167
> )
> 	at
> com.opencms.template.cache.CmsUri.callCanonicalRoot(CmsUri.java:171)
> 	at
> com.opencms.template.cache.CmsElementCache.callCanonicalRoot(CmsElementCac
> he
> .java:148)
> 	at
> com.opencms.launcher.CmsXmlLauncher.generateOutput(CmsXmlLauncher.java:253
> )
> 	at
> com.opencms.launcher.CmsXmlLauncher.launch(CmsXmlLauncher.java:309)
> 	at
> com.opencms.launcher.A_CmsLauncher.initlaunch(A_CmsLauncher.java:267)
> 	at com.opencms.core.OpenCms.showResource(OpenCms.java:653)
> 	at
> com.opencms.core.OpenCmsHttpServlet.doGet(OpenCmsHttpServlet.java:231)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> 	at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicati
> on
> FilterChain.java:247)
> 	at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter
> Ch
> ain.java:193)
> 	at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.
> ja
> va:243)
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 66)
> 	at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472
> )
> 	at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> 	at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.
> ja
> va:190)
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 66)
> 	at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472
> )
> 	at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> 	at
> org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
> 	at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1
> 80
> )
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 66)
> 	at
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValv
> e.
> java:170)
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 64)
> 	at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1
> 70
> )
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 64)
> 	at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 64)
> 	at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472
> )
> 	at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> 	at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja
> va
> :174)
> 	at
> org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java
> :5
> 66)
> 	at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472
> )
> 	at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> 	at
> org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.jav
> a:
> 1027)
> 	at
> org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:11
> 25
> )
> 	at java.lang.Thread.run(Thread.java:479)
> 
> 
> ==========================================================================
> ==
> ===
> 
> Does anybody know what to do?
> 
> 
> 
> Best regards
>  Martin
> 
> _________________________________________________________________________
> Martin Buehrle, IT-Projects/Services
> EADS - European Aeronautic Defence and Space Company
> eMail: Martin.Buehrle at lfk.eads.net
> _________________________________________________________________________
>