Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Problem in sending back xml from servlet - Help

Problem in sending back xml from servlet - Help

2004-02-24       - By Jacob Kjome
Reply:     1     2  

Which browser?  Is it Mozilla?  You need to make sure you set the
appropriate content-types.  top.xml should be provided as "text/xml" or
whatever type of XML it is.  If it is XHTML, you might use
"application/xhtml+xml".  Note that "text/xsl" doesn't exist as a
content-type.  It is only, lamely, recognized by IE.  Make sure that the
server serving up the .xsl file sets the content type as "text/xml" as well.

The reason it might load up from your file system properly is that Mozilla
presumes the content-type based on the file extension ".xml".

Jake


At 10:38 AM 2/24/2004 -0500, you wrote:
>All,
>
>         I'm trying to read a xml file, then add a processing instruction
> and trying
>to send it back as response from a servlet. But when i send the response and
>try to view it from the browser, i dont see the processing instruction added
>to the xml file. But if i write the document object to a file in the server
>and read it from that file then the xslt processing tag is attached and the
>browser displays it correctly.
>
>
>Reading xml from the file and adding processing instruction.
>
>             FileInputStream fis = new FileInputStream("C:\\ragu\\top10.xml");
>                 InputSource     in_src = new InputSource(fis);
>                 DocumentBuilderFactory dbf =
>DocumentBuilderFactory.newInstance();
>                 DocumentBuilder db = dbf.newDocumentBuilder();
>                 Document document = db.parse(in_src);
>                 String xslpath = req.getScheme() + "://" +
>req.getServerName() + ":" + req.getServerPort();
>                 ProcessingInstruction pi =
>document.createProcessingInstruction("xml-stylesheet", "href=\""+
>"http://wsd-007/summary.xslt"  +"\" type=\"text/xsl\"");
>                 document.insertBefore(pi, document.getDocumentElement());
>                 document.normalize();
>
>
>***********************************************************************
>
>writing the document to a file. This file has the processing instruction
>attached to it.
>
>             FileOutputStream fos_1 = new
>FileOutputStream("c:\\ragu\\test_cv_servlet.xml");
>                 BufferedOutputStream bos_1 = new
>BufferedOutputStream(fos_1);
>                 OutputFormat format_1 = new OutputFormat(document);
>                 format_1.setEncoding("ISO-8859-1");
>                 //format.setEncoding(System.getProperty("DbEncoding"));
>                 StringWriter stringOut_1 = new StringWriter();
>                 XMLSerializer serial_1 = new XMLSerializer(stringOut_1,
>format_1);
>                 serial_1.asDOMSerializer();
>                 serial_1.serialize(document);
>                 bos_1.write(stringOut_1.toString().getBytes());
>                 bos_1.flush();
>                 fos_1.close();
>
>***************************************************************************
>
>sending it back from the document object. But the processing instruction is
>not there.
>
>
>             OutputStream os = res.getOutputStream();
>                 OutputFormat    format  = new OutputFormat( document );
>//Serialize DOM
>                 format.setEncoding("ISO-8859-1");
>                 StringWriter  StringOut = new StringWriter();
>//Writer will be a String
>                 XMLSerializer    serial = new XMLSerializer( StringOut,
>format );
>                 serial.asDOMSerializer();
>                 serial.serialize(document.getDocumentElement());
>                 //OutWriter.write(StringOut.toString());
>                 os.write(StringOut.toString().getBytes());
>                 os.flush();
>                 os.close();
>
>****************************************************************************
>**
>
>Please advice me what i'm doing wrong or how to send a document with the
>processing instructions.
>
>
>Ragu
>CircuitVision
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
>For additional commands, e-mail: xerces-j-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)