Anonymous | Login | Signup for a new account | 12-17-2024 10:42 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000945 | [Resin] | minor | always | 02-16-06 11:06 | 04-06-06 10:28 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.17 | ||||||
Summary | 0000945: JDOM XML issues | ||||||||
Description |
(rep by Jim Spring) I've been looking at the use of XFire for some SOAP related work and have run across an issue that looks like it is a problem with Resin, JDom or both. When running the XFire samples under Tomcat, things work fine. However, if I attempt to use Resin, I get the Exception stack listed at the bottom. In searching through the resin bug list, the only thing I find referencing JDOM is: http://bugs.caucho.com/view.php?id=451 [^] Any thoughts / input would be helpful. Thanks -jim spring org.jdom.IllegalNameException: The name "null" is not legal for JDOM/XML DocTypes: XML names cannot be null or empty. at org.jdom.DocType.setElementName(DocType.java:171) at org.jdom.DocType.<init>(DocType.java:111) at org.jdom.DocType.<init>(DocType.java:144) at org.jdom.DefaultJDOMFactory.docType (DefaultJDOMFactory.java:118) at org.jdom.input.DOMBuilder.buildTree(DOMBuilder.java:332) at org.jdom.input.DOMBuilder.buildTree(DOMBuilder.java:170) at org.jdom.input.DOMBuilder.build(DOMBuilder.java :135) at org.codehaus.xfire.wsdl11.builder.AbstractWSDL.writeDocument(AbstractWSDL.java:136) at org.codehaus.xfire.wsdl11.builder.WSDLBuilder.write(WSDLBuilder.java:80) at org.codehaus.xfire.wsdl11.builder.WSDLBuilderAdapter.write (WSDLBuilderAdapter.java:40) at org.codehaus.xfire.DefaultXFire.generateWSDL(DefaultXFire.java:109) at org.codehaus.xfire.transport.http.XFireServletController.generateWSDL(XFireServletController.java :304) at org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:140) at org.codehaus.xfire.transport.http.XFireServlet.doGet(XFireServlet.java:81) at javax.servlet.http.HttpServlet.service(HttpServlet.java:115) at javax.servlet.http.HttpServlet.service(HttpServlet.java:92) at com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java :106) at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:178) at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:229) at com.caucho.server.http.HttpRequest.handleRequest (HttpRequest.java:267) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:388) at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490) at com.caucho.util.ThreadPool.run(ThreadPool.java :423) at java.lang.Thread.run(Thread.java:552) The |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Notes | |
(0000887) anonymous 02-20-06 02:15 |
I’ve been having similar issues. Loading up a simple Document adds a null node value to the head of the document.. Everything works fine and dandy in 3.0.14 but fails in 3.0.17. <system-property javax.xml.parsers.DocumentBuilderFactory="com.caucho.xml.parsers.XmlDocumentBuilderFactory"/> <system-property javax.xml.parsers.SAXParserFactory="com.caucho.xml.parsers.XmlSAXParserFactory"/> <system-property javax.xml.transform.TransformerFactory="com.caucho.xsl.Xsl"/> This really basic servlet (http://www.webcoding.co.uk/testServlet.java) [^] will run in both 14 & 17 but in 17 the result to the browser also includes “null” at the head of the document which causes havoc when we try and run Xpath stuff within the code. |
(0001029) ferg 04-06-06 10:28 |
xml/03f3 |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
32 total queries executed. 27 unique queries executed. |