DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-11-20 01:05 --- *** This bug has been marked as a duplicate of 13282 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-08 17:59 --- Well, it seems that Xerces 2.2.0 has a bug since the web-jsptaglibrary_1_2.dtd file is parsed without any errors using Crimson. I'm trying to get the bug confirmed with the xerces-j team. The only thing I know is that one user of Xalan currently report the same problem (Xalan uses Xerces). More to comes -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-07 16:23 --- At least the tarball distribution contains a couple of bad system ID's in TLD's and the tester web.xml. See my report and a patch in bug #13300. However, applying that patch doesn't fix the problem, but I dug around a bit, and it's somehow caused by the example TLD's. Commenting out the taglib's from examples/WEB-INF/web.xml at least lets 4.1.12 start up. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-08 04:24 --- is bug 13282 related to this? maybe even a dup? Jake -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-08 04:36 --- They certainly look the same, however bug 13241 uses ServletAPI-4 while bug 13282 uses ServletAPI-5. Bug 13282 seems to suggest that a clean compile can occur, however when Tomcat is started, it fails with errors in comments. Bug 13241 as explained allows tomcat to actually start and serve files, however JSP and Servlets can not be mounted/served because of the same error. Perhaps bug 13241 should be re-assigned to the xerces-j group and bug 13282 be marked a duplicate (or very close). The only difference of course is that both bugs cover different ServletAPI's. The question still remains, is Tomcat now shipping with XML files which are incompatible with xerces-2.2.0 or does xerces-2.2.0 have a problem parsing comments in XML? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-06 13:57 --- Hmm, the only thing is that casper by default isn't shipped with the base source code for Tomcat. It is just another XML parser/marshaller/unmarshaller. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-04 12:45 --- After switch to t4.1.12 I got this error: 0INFO mill.startup.StartupServlet - Application path: C:\opt2 \www\_toner.irk.ru\data\ 0INFO mill.startup.StartupServlet - class org.bouncycastle.jce.provider.BouncyCastleProvider present 0INFO mill.startup.StartupServlet - class com.oreilly.servlet.multipart.FilePart present 0INFO mill.startup.StartupServlet - class org.apache.log4j.Category present 50 INFO mill.startup.StartupServlet - class org.exolab.castor.mapping.Mapping present 16530 DEBUG mill.member.MemberMapping - Create Mapping instance from file c:\opt2\www\_toner.irk.ru\data\WEB-INF\mill\castor_mapping.xml 16530 DEBUG mill.member.MemberMapping - Previos instance not found. Create new instance, file - c:\opt2\www\_toner.irk.ru\data\WEB-INF\mill\castor_mapping.xml 16810 FATAL mill.member.MemberMapping - Error get instance of org.exolab.castor.mapping.Mapping java.net.MalformedURLException: unknown protocol: c at java.net.URL.init(URL.java:586) at java.net.URL.init(URL.java:476) at java.net.URL.init(URL.java:425) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:463) at org.exolab.castor.mapping.Mapping.loadMappingInternal (Mapping.java:488) at org.exolab.castor.mapping.Mapping.loadMappingInternal (Mapping.java:441) at org.exolab.castor.mapping.Mapping.loadMapping(Mapping.java:368) at mill.member.MemberMapping.getInstance(MemberMapping.java:61) at mill.member.MemberMapping.getInstance(MemberMapping.java:27) at mill.startup.InitParam.parseConfigFile(InitParam.java:120) at mill.startup.InitParam.readConfig(InitParam.java:237) at mill.startup.InitParam.getHTMLCharset(InitParam.java:429) at mill.port.InitPage.setContentType(InitPage.java:92) at mill.portlet.ContextNavigator.doGet(ContextNavigator.java:513) 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 (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.invokeNex t(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.invokeNex t(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:2396) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke (AccessLogValve.java:469) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 11:28 --- At this point, I am not using Jikes (at least I haven't got it defined or compiled anywhere in the project). When I downgraded to xerces-1_4_4 rather than use xerces-2_2_0, I am able to get a clean compile and I am able to use the Servlets and JSPExamples page. Looks like there might be a slight problem/incompatability in the xerces-2_2_0 library. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples/ Disabled
[EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 11:28 --- At this point, I am not using Jikes (at least I haven't got it defined or compiled anywhere in the project). When I downgraded to xerces-1_4_4 rather than use xerces-2_2_0, I am able to get a clean compile and I am able to use the Servlets and JSPExamples page. Looks like there might be a slight problem/incompatability in the xerces-2_2_0 library. Yes, the comment check was not present in previous xerces release (or disabled by default) and I still wonder where digester find problem with --. Any help will be welcomed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 12:44 --- The XML parsing is done by the XML parser. If the parser doesn't like your XML, it will throw an exception. Whether or not it is the right thing to do or a bug in the parser is another question, but it's not a Tomcat bug. Tomcat 4.1.12 includes Xerces 2.0.2 (by accident). Tomcat 4.1.13 was supposed to include Xerces 2.1.0. The question is now: which version should I include ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 13:13 --- I can certainly say that Xerces-2_1_0 is compatible as servlets and JSP pages work without any problems. Perhaps one option would be to recommend xerces- 2_1_0 for the time being until the problem is discovered with xerces-2_2_0. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 13:30 --- From xerces-j2 2.2.0 announce : - Many conformance bugs have been fixed and the parser's performance enhanced in many situations. [Elena Litani, Sandy Gao, Neil Graham] So we may have some invalid xmls into 4.1.12 which should be discovered ? Did you try with others parser, ie crimson ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241 Tomcat 4.1.12 / Webapps:Examples / Disabled --- Additional Comments From [EMAIL PROTECTED] 2002-10-03 14:45 --- Okay, just tried Tomcat 4.1.12 with the XML being handled with crimson.jar and jaxp.jar and it worked like a charm. It certainly looks like the parsing in xerces-2_2_0 is causing a problem. While looking through the source code for XMLScanner.java in xerces (v2.2.0) I noticed that a slight rework had been performed in the scanComment function but there is nothing there which should cause the problem. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
