Unknown entity(Acirc;) included by the SAX parser instead of in UNIX

I have a piece of code that parses html files.I had given in one of the html.The output of this parsing is another xml file.In the output xml file i see a Acirc; instead of on Unix.
On windows the same code doesnt generate this character in the output xml file.
Pls suggest a fix if anyone has faced this problem before.

I have found in the XML1.0 recomendations
------------ include ----------------------
2.11 End-of-Line Handling
XML parsed entities are often stored in computer files which, for editing convenience, are organized into lines. These lines are typically separated by some combination of the characters carriage-return (#xD) and line-feed (#xA).
To simplify the tasks of applications, wherever an external parsed entity or the literal entity value of an internal parsed entity contains either the literal two-character sequence "#xD#xA" or a standalone literal #xD, an XML processor must pass to the application the single character #xA. (This behavior can conveniently be produced by normalizing all line breaks to #xA on input, before parsing.)
----------------- end of include ----------------------
According to this the parser's behavior is 100% correct.
Unfortunately I have no control on what appear in the CDATA section. Thus, before processing the entry (CRC calculation) the content of the CDATA should be normilized, i.e. all new-lines should be substitued with '#xA'. Until now I haven't found a better solution.

Similar Messages

Using the SAX Parser

As I reported in this thread: Carriage Returns in XSLT output I am trying to produce a text output file with each line terminating in cr-lf (using the output from ViewObject.writeXML() passed through the XSLProcessor.processXSL() method to apply a XSLT stylesheet transformation to it), but the cr characters in the stylesheet are being converted to nl characters, so I am ending up with two nl characters at the end of each line.
I found a 2002 query (here: http://www.xslt.com/html/xsl-list/2002-04/msg00193.html) by someone with the same problem, and a reply by Steve Muench explaining it and stating that the Oracle SAX parser does not have the same problem.
So my question now is - does the SAX parser still retain cr characters (or is it too now converting them to nl) and if it does, how do I make XSLProcessor.processXSL() use it rather than the default XML parser? Can I do it from within my code, or does it need to be set in some sort of environment variable? We are on version 9.0.5.2 of JDeveloper(10g)

Repost

Using the SAX parser to split up a document to be processed by a DOMParser

I need to process a potentially large document which could prove too large to be read into memory at once by the DOM parser. The document would look something like..
(sorry about the formatting - can't use tabs!)
<Root>
<Parent>
<Child>
<Blah.....................
</Blah>
</Child>
</Parent>
<Parent>
<Child.......
</Child>
</Parent>
etc...
etc...
</Root>
The number of Parent elements could potentially be in the thousands. What I would like to do would be to use the SAX parser to read the document and when a Parent element is encountered, write the parent element and all its children to a stream in order that an input source can be created. The input source can then be parsed by a DOM parser. Once complete, the next Parent element encountered by the SAX parser could be passed to the DOM parser and so on until all of the Parent elements have been processed.
This way I can combine the ease of parsing the document using the DOM parser without having to worry about the overhead on memory.
Does anyone have any ideas as to the best approach? I could use the SAX parser for the whole thing but the XML is quite complex and lends itself to DOM parsing much more conveniently.

Can you read the file line by line:
start the reading at <child>
pause reading at </child>
copy the string to a var
wrap it with respective tags (<?xml<doctype etc...) and parse
proceed to the next <child>xx</child>
and repeat till you hit the closing of the file...
- Ravi

Why the SAX parser cannot support the special character like "¡"

I do not understand why the SAX parser cannot support the special character like ¡ but it can replace the " & < > to ", &, <, >, ,, but other characters will be replaced to empty charater.
can somebody give me any suggestions or solutions. THX.
Edited by: 844086 on 2011-3-14 上午2:27
Edited by: 844086 on 2011-3-14 上午2:27

I quote:
Alternatively implement an EntityResolver that resolves the desired escapes.You are again an example that people only read/register the first thing written in a post.

I've a problem with errors message in the sax parser

Hello,
I'm quite new to Java.
I'm trying to create a SAX parser for my XML file, with a XML schema.
When my pars run a XML file, the following mistakes go out:
1)org.sax.SAXParseException:s4s-elt-must-match: the content of 'restriction' must match (annotation?,.....)
2)org.sax.SAXParseException: src-ct.0.1:Complex Type Definition Rappresentation Error for type..... Element 'sequence' is invalid,misplaced or occurs to often
but I don't understand where I must go in the schema to correct.
Many thanks!

Hi,
Perhaps it would help if you post your XML file.

How to Create XML file with SAX parser instead of DOM parser

HI ALL,
I am in need of creating an XML file by SAX parser ONLY. As far as my knowledge goes, we can use DOM for such purpose(by using createElement, creatAttribute ...). Can anyone tell me, is there any way to create an XML file using SAX Parser only. I mean, I just want to know whether SAX provides any sort of api for Creatign an element, attribute etc. I know that SAX is for event based parsing. But my requirement is to create an XML file from using only SAX parser.
Any help would be appreciated
Thanx in advance
Kaushik

Hi,
You must write a XMLWriter class yourself, and that Class extends DefaultHandle ....., the overwrite the startElement(url, localName, qName, attributeList), startDocument(), endElement().....and so on.
in startElement write your own logic about how to create a new element and how to create a Attribute list
in startDocument write your own logic about how to build a document and encodeType, dtd....
By using:
XMLWriter out = new XMLWriter()
out.startDocument();
Attribute attr1 = new Atribute();
attr1.add("name", "value");
out.startElement("","","Element1", attr1);
Attribute attr2 = new Atribute();
attr2.add("name", "value");
out.startElement("","","Element2", attr2);
out.endElement("","","Element2");
out.endElement("","","Element1");
out.endDocument();

How to stop the sax parser with parsing

hi,
I'm parsing some large xml-files with jaxp sax.
To do it I use a contenthandler that goes through the file.
Wat I want now is that when I have found the nodes that I need that parsing of the xml stops.
I tried to do it with detecting a certain endElement and putting there a return, but it will not work, parsing continues till the end of the file (see code underneath).
Does anyone can say what I'm doing wrong,
thanks, Hans
code:
public void endElement(String namespaceURI,
String sName,
String qName
) throws SAXException {
if (qName.equals("file")) {
return;
} // end of if ()
}

You have to return from that method anyway, so a return statement is not going to tell the parser to stop. You could throw a SAXException, but be prepared to catch that in the code that called the parser, and be prepared to treat it differently from SAXExceptions that indicate problems.

Java SAX parser. How to get raw XML code of the currently parsing event?

Java SAX parser, please need a clue how to get the raw XML code of the currently parsing event... needed for logging, debugging purposes.
Here's and example, letting me clarify exactly what i need: (see the comments in source)
public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException {
     //..Here... or maybe somewhere elsewhere I need on my disposal the raw XML code of
     //..every XML tags received from the XML stream. I need simply to write it down
     //..in a log file, for debugging purposes, while parsing. Can anyone give me a suggestion
     //..how can i implement such logging while the SAX parser only returns me the tagname and
     //..attributes. While parsing I want to log the XML code for every tag in
     //..its 'pure form', like it is comming from the server directly on the
     //..socket's input reader.
     if ("p".equals(qName)) {
          etc...
}Than you in advance.

YES!
I've solved my problem using class RecordingInputStream that wraps the InputStream
here is the class source code:
import java.io.ByteArrayOutputStream;
import java.io.FilterInputStream;
import java.io.InputStream;
import java.io.IOException;
* @author Unknown
class RecordingInputStream extends FilterInputStream {
     protected ByteArrayOutputStream sink;
    RecordingInputStream(InputStream in) {
        this(in, new ByteArrayOutputStream());
    RecordingInputStream(InputStream in, ByteArrayOutputStream sink) {
        super(in);
        this.sink = sink;
    public synchronized int read() throws IOException {
        int i = in.read();
        sink.write(i);
        return i;
    public synchronized int read(byte[] buf, int off, int len) throws IOException {
        int l = in.read(buf, off, len);
        sink.write(buf, off, l);
        return l;
    public synchronized int read(byte[] buf) throws IOException {
        return read(buf, 0, buf.length);
    public synchronized long skip(long len) throws IOException {
        long l = 0;
        int i = 0;
        byte[] buf = new byte[1024];
        while (l < len) {
            i = read(buf, 0, (int)Math.min((long)buf.length, len - l));
            if (i == -1) break;
            l += i;
        return l;
    byte[] getBytes() {
        return sink.toByteArray();
    void resetSink() {
        sink.reset();
} Then here is the initialization before use with SAX:
this.psock = new Socket(this.profile.httpServer, Integer.parseInt(this.profile.httpPort));
this.out = new PrintWriter(this.psock.getOutputStream(), true);
this.ris=new RecordingInputStream(this.psock.getInputStream());
this.in=new BufferedReader(new InputStreamReader(this.ris));
try {
     this.parser = SAXParserFactory.newInstance().newSAXParser();
     this.parser.parse(new InputSource(this.in),new XMLCommandsHandler());
catch (IOException ioex) { }
catch (Exception ex) { }Then the handler class looks like this (it will be an inner class, so you can access ris, from the parent class):
class XMLCommandsHandler extends DefaultHandler {
     public void startDocument() throws SAXException {
          //...nothing
     public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException {
          // BEGIN - Synchronized logging of raw XML source code in parallel with SAX parsing :)
          byte[] bs=ris.getBytes();
          logger.warn(new String(bs));
          ris.resetSink();
          // End logging
          if ("expectedTagThatTriggersMeToDoSomething".equals(qName)) {
               //...Do smth.
}Edited by: patladj on Jul 3, 2008 12:30 PM

Why are all the events in the XML SAX parser not activated?

Hi everyone,
I have written a mini server that parses XML files into SQL queries.
Below is a segment of my code;
          try          {
               Class.forName( JDBC_DRIVER );
               myConnection = DriverManager.getConnection( DATABASE_URL, "username", "password");
               EventXMLParser myEXP = new EventXMLParser(directory, myConnection);
               File[] xmlFiles = directory.listFiles();
               for (File xmlFile : xmlFiles)               {
                    myEXP.XMLtoDB(xmlFile);
                    outWriter.println("File:" + xmlFile.getName() + " DONE");
          } catch (SQLException e)     {
               System.err.println("SQLException for establishing connection");
               e.printStackTrace();
          } catch (ClassNotFoundException e)     {
               System.err.println("CLASS NOT FOUND EXCEPTION HERE");
               e.printStackTrace();
          } catch (Exception e)     {
               System.err.println(e);
               e.printStackTrace();
          finally {
               outWriter.println("PARSING COMPLETED");
               outWriter.close();
     }Where the constructor EventXMLParser constructs the following:
     public EventXMLParser(File path, Connection connection)     {
          super();
          try     {
               this.XMLpath = path;
               this.db_connection = connection;
               this.xr = XMLReaderFactory.createXMLReader();
               this.XMLSAXhandler = new DefaultHandler(); //create a new own handler
               this.xr.setContentHandler(XMLSAXhandler);
               this.xr.setErrorHandler(XMLSAXhandler);
               //System.out.println("DEBUG: db_connection is " + db_connection.toString());
          catch (Exception e)     {
               System.out.println("Constructor Error!");
               e.printStackTrace();
     }Below are all my helper methods within EventXMLParser.java
     public void XMLtoDB(String XMLpath) throws Exception {
          try     {
               //Input
               System.out.println("XMLpath is : " + XMLpath);
               /*FileReader r = new FileReader(XMLpath); debug
               InputSource in = new InputSource(r);
               xr.parse(in);
               xr.parse(XMLpath);
               /* Note that while parsing, the end of each event, </event>
                * will trigger sendSQL to execute the query on the database
          catch (Exception e)     {
               throw new Exception("Error with XMLtoDB!! Exception: " + e);
     public void sendSQL(Event event, Connection sql_connection) throws SQLException     {
               //JDBC part
               try     {
                    System.err.println("DEBUG sendSQL");
                    Statement sql_statement = sql_connection.createStatement();
                    ResultSet resultSet = sql_statement.executeQuery( event.toSQL() );
               catch (SQLException e)     {
                    e.printStackTrace();
     /* Parsing XML
      * From here onwards it's all designed for the SAX Parsing with different event calling methods
     public void startDocument()     {
          System.err.println("Start Document");
     public void endDocument()     {
          System.err.println("End Document");
     public void startElement(String uri, String name, String qName, Attributes atts)     {
          CurrentElement= name;
          System.out.println("This is parsing");
     public void characters(char ch[], int start, int length)     {
          SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss");
          StringBuffer sb = new StringBuffer();
          for (int i = start; i < start + length; i++)
               sb.append(ch);
          String content = sb.toString();
          if (CurrentElement.equals("eid"))
               temp.setEventID( (Integer.valueOf(content)).intValue() ) ;
          else if (CurrentElement.equals("sd"))
               temp.setShort_description(content);
          else if (CurrentElement.equals("ld"))
               temp.setLong_description(content);
          else if ( (CurrentElement.equals("dt")))
               temp.setDate_Time( formatter.parse(content, new ParsePosition(0)) );
          else if (CurrentElement.equals("repeat"))
               temp.setRepeat_pattern( (Integer.valueOf(content)).intValue() );
          else if (CurrentElement.equals("valid"))
               temp.setValid_period(content);
          else if (CurrentElement.equals("status"))     {
               temp.setStatus( (Integer.valueOf(content)).intValue() );
          else {}
     public void endElement(String uri, String name, String qName)     {
          System.err.println("DEBUG" + temp.toString()); /*debug*/
          if (name.equals("event"))     {
               try     {
                    /*debug*/ temp.setUserID(1);
                    /*debug*/ System.err.println("DEBUG: " + temp.toString());
                    sendSQL(temp, db_connection);
                    //temp = new Event();
               catch (SQLException e)     {
                    System.err.println(e);
               }//end catch
          }//end try
Where event is a public class Event     {
     //fields
     private int userID = 1; // = 1 only applies for testing
     private int eventID;
     private String short_description;
     private String long_description;
     private Date date_time = null;
     private int repeat_pattern;
     private String valid_period;
     private int status;     //1 for new, 0 for modification and -1 for delete
     SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss");
     //Constructors
     //every event requires the following: userID eventID and short_Description
     public Event(int uID, int eID, String shortDescrp)     {
          setUserID(uID);
          setEventID(eID);
          setShort_description(shortDescrp);
     public Event(int uid, int eid, String sd,
                              String ld, Date d_t, int r_p, String v_p, int s)     {
          setUserID(uid);
          setEventID(eid);
          setShort_description(sd);
          setLong_description(ld);
          setDate_Time(d_t);
          setRepeat_pattern(r_p);
          setValid_period(v_p);
          setStatus(s);
     //set
     public void setUserID (int x)                         { this.userID = x ;}
     public void setEventID (int x)                         { this.eventID = x ;}
     public void setShort_description (String x)          { this.short_description = x ;}
     public void setLong_description (String x)          { this.long_description = x ;}
     public void setDate_Time(Date x)                    { this.date_time = x ;}
     public void setRepeat_pattern (int x)               { this.repeat_pattern = x ;}
     public void setValid_period (String x)               { this.valid_period = x ;}
     public void setStatus (int x)                         { this.status = x; }
     //get
     public int           getUserID()                              { return this.userID;}
     public int           getEventID()                         { return this.eventID;}
     public String      getShort_description()               { return this.short_description;}
     public String      getLong_description()               { return this.long_description;}
     public Date        getDate_Time()                         { return this.date_time;}
     public int         getRepeat_pattern()                    { return this.repeat_pattern;}
     public String      getValid_period()                    { return this.valid_period;}
     public int           getStatus()                              { return this.status; }
     //Event to SQL statements;
     public String toSQL()     {
          StringBuffer sb = new StringBuffer();
          ///if ( status == 1)     {
               sb.append( "INSERT INTO events SET" );
               sb.append( " userID = " + userID + ", ");
               sb.append( "eventID = " + eventID + ", " );
               sb.append( "short_description = " + "\'" + short_description + "\'" + ", "); //String
               sb.append( "long_description = " + "\'" + long_description + "\'" + ", "); //String
               sb.append( "date_time = " + "\'" + formatter.format(date_time) + "\'" + ", ");
               sb.append( "repeat_pattern = " + repeat_pattern + ", " );
               sb.append( "valid_period = " + "\'" + valid_period + "\'" ); //String
               sb.append( ";");
          //} else if ( status == 2)      {
          System.err.println(sb.toString());
          return sb.toString();
}     My question is: I have taken my SQL query generated by toSQL() method in events and it worked.
Here is the funny thing:
Everything is correct syntax wise: No complaints what soever
The mysql part works: Tested separately.
So I tend to think that the problem lies within the SAX parser. I have written SAX2 parsers on this machine before and they have worked too. I tried inserting println statements all over startElement endElement etc etc only to find out that the SAX parser did not call any of the methods that I overided!! Why is that so?
Can you guys spot where my SAX parser fails?

I see.
I try to correct this problem by removing super();
so right now my code looks like this:
     static Event temp = new Event(0, 0, "null", "null", new Date(), 0, "null", 0);
     static String CurrentElement = null;
     static File XMLpath;
     static Connection db_connection;
     static XMLReader xr;
     static DefaultHandler XMLSAXhandler;
     //Constructor,      Build the SAX Parser
     public EventXMLParser(File path, Connection connection)     {
          try     {
               this.XMLpath = path;
               this.db_connection = connection;
               this.xr = XMLReaderFactory.createXMLReader();
               this.XMLSAXhandler = new DefaultHandler(); //create a new own handler
               this.xr.setContentHandler(XMLSAXhandler);
               this.xr.setErrorHandler(XMLSAXhandler);
               //System.out.println("DEBUG: db_connection is " + db_connection.toString());
          catch (Exception e)     {
               System.out.println("Constructor Error!");
               e.printStackTrace();
     }This time, I created a new instance of default handler() which can be referenced by as the objects's XMLSAXhandler. However, that did not solve the problem, why does the problem still persist?
Right now, there is only one instance of a default handler created. So why does all my parsing event functions still get ignored?

JAVAMAP-Sax Parser ...............Linkage error when loading the class.

Dear all,
Do we have any extra things to execute the Java mapping using the Sax Parser?
When I am executing the interface mapping ,I am getting the" Linkage error when loading the class" error.
Kindly let me know your personnel maildId so that I can mail you the screen shots.
Thanks,
Srinivasa

Dear sunil,
Find the File.
Source:
<MTO_FTP_MAT_DETAILS>
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
TARGET
MTI_FTP_MAT_DETAILS
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
Source:
<MTO_FTP_MAT_DETAILS>
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
TARGET
MTI_FTP_MAT_DETAILS
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
import org.xml.sax.Attributes;
import org.xml.sax.SAXException;
import org.xml.sax.helpers.DefaultHandler;
import com.sap.aii.mapping.api.StreamTransformation;
class Echo {
public static OutputStream out;
public class myEcho extends DefaultHandler implements StreamTransformation {
private Map map;
public void setParameter(Map param) {
map = param;
public void execute(InputStream in, OutputStream out) {
DefaultHandler handler = this;
SAXParserFactory factory = SAXParserFactory.newInstance();
try {
SAXParser saxParser = factory.newSAXParser();
Echo.out = out;
saxParser.parse(in, handler);
} catch (Throwable t) {
t.printStackTrace();
public void startDocument() throws SAXException {
try {
Echo.out.write("<?xml version='1.0' encoding='UTF-8'?>".getBytes());
} catch (IOException e) {
e.notify();
public void endDocument() throws SAXException {
try {
Echo.out.flush();
} catch (IOException e) {
throw new SAXException("I/O error", e);
public void startElement(String namespaceURI, String sName, // simple name
String qName, // qualified name
Attributes attrs) throws SAXException {
String eName = sName; // element name
if ("".equals(eName))
eName = qName; // not namespace-aware
if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
try {
Echo.out.write(("<MTI_FTP_MAT_DETAILS>").getBytes());
} catch (Exception e) {
e.printStackTrace();
} else {
try {
Echo.out.write(("<" + qName + ">").getBytes());
} catch (Exception e) {
e.printStackTrace();
public void endElement(String namespaceURI, String sName, // simple name
String qName // qualified name
) throws SAXException {
String eName = sName; // element name
if ("".equals(eName))
eName = qName; // not namespace-aware
if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
try {
Echo.out.write(("</MTI_FTP_MAT_DETAILS>").getBytes());
} catch (Exception e) {
e.printStackTrace();
} else {
try {
Echo.out.write(("</" + qName + ">").getBytes());
} catch (Exception e) {
e.printStackTrace();
public void characters(char buf[], int offset, int len)
throws SAXException {
String s = new String(buf, offset, len);
try {
Echo.out.write(s.getBytes());
} catch (Exception e) {
e.printStackTrace();

SAX-parser and mapping on the XI

Helllo everybody,
I'm trying to map an xml-document using the SAX-parser.
I'm reading the data using an impustream. the problem is, while testing on the XI, the following message comes :
Creating Java mapping xmlDataExchangeSAPSample/XMLValidation
Loaded class xmlDataExchangeSAPSample.XMLValidation
Loaded class xmlDataExchangeSAPSample.myErrorHandler
Call method execute of the application Java mapping xmlDataExchangeSAPSample.XMLValidation
START APPLICATION TRACE ***
xxx implementierende Klasse Parserscom.sap.engine.lib.jaxp.SAXParserFactoryImpl
erstelltes Dokument aus in EDIFACTINTERCHANGE
Beginn Parsenjava.io.ByteArrayInputStream@1aa342a3
SAXException when parsing Generic Exception:
com.sap.engine.lib.xml.util.NestedException -> com.sap.engine.lib.xml.parser.ParserException -> java.io.IOException: Parsing an empty source. Root element expected!
END APPLICATION TRACE ***
Java mapping xmlDataExchangeSAPSample/XMLValidation completed. (execute() of xmlDataExchangeSAPSample.XMLValidation
Ausführung war erfolgreich.
10:18:14 Testende
the the Document ist generated :
"...erstelltes Dokument aus in EDIFACTINTERCHANGE.."
but the parser find an empty source.
do you have an idea what could be happening here?
Kind regards

Hi,
<<
xxx implementierende Klasse Parserscom.sap.engine.lib.jaxp.SAXParserFactoryImpl
erstelltes Dokument aus in EDIFACTINTERCHANGE
Beginn Parsenjava.io.ByteArrayInputStream@1aa342a3
SAXException when parsing Generic Exception:
com.sap.engine.lib.xml.util.NestedException -> com.sap.engine.lib.xml.parser.ParserException -> java.io.IOException: Parsing an empty source. Root element expected!
>>
This seems that u r trying parse a file rather than valid XML document..
Usually you will notice this problem when u r trying to parse a payload which is in txt format usually when u r using File Adapter message protocol as "FILE" instead of "FCC".
Usually SAX is an API Desinged to parse Valid XML Documents only.
If you want to do manipulations on NON XML data better to use Java.io.InputStream & OutputStream.
Regards,
Rao.Mallikarjuna

Stop Sax Parser in the middle of parsing

Hi all,
I am using Sax Parser.
I want to stop the parsing after finding a specific element for the first time. I have thought on two ways -
1. Throwing an exception - Pros- clean, short. Cons - ugly it is not Exception.
2. adding a flag and if statement in the begin of each event-driving method checking whether I have found the element or not - Cons - I am still wasting lots of time on parsing all the file and doing nothing.
Does anybody know any better way of stopping the Sax Parser?

I've never tried to do this. The two options you have provided should work. I don't know of any others. The second option could be modified to use a Strategy pattern. Make a Handler that jst defers to your real handler. Once you hit the element tha you need, swap out your handler with one that has an empty implemetation.

Extending included SAX parser in Java 5.

Hi all,
I have a somewhat unique problem and I could use some help. I�m tackling a project to integrate a mainframe system with a J2EE processing cluster. The main frame produces a data file that is formatted via template �overlays�. Since this process is very old, I cannot create the template that uses XML to delimit the data elements, and I don�t want to perform screen scraping. Also, the text in the tags will not be correctly escaped. Instead I can create tags based off of the same principal. I will probably use the format below for tags.
{{{tag-name}}}My data goes here{{{/tag-name}}} Since this is basically a structured tagged document, I would like to extend the existing SAX parser to use the tag syntax of {{{.*}}} for opening and {{{\/.*}}} for the closing tag. I would then also remove the parsing of escaped characters in the body. Is this feasible using the SAX parser, or will I need to create my own from scratch and just use the existing event interfaces?
Todd

I thought of that initially too, but unfortunately that still doesn't fix the encoding problem. I could replace '{{{' with '<' in the templates, that is not the issue. Here is a more concise example. Let�s say I have the following basic output.
Transaction
Description: Barnes & Noble
Amount: 25.50
If this came out in well formed XML it would look like this
<transaction>
     <description>Barns & Noble</description>
     <amount>25.50</amount>
</transaction>However, if I were to just use XML tags in my template on the mainframe, this is what I would get.
<transaction>
     <description>Barns & Noble</description>
     <amount>25.50</amount>
</transaction>As you can see, the �&� is not correctly XML encoded by the mainframe. When I run this through the SAX parser, it will not work because the �&� is not part of an escape sequence. I have a rudimentary implementation of org.xml.sax.XMLReader and it works with the SAX content handler implementation, it just seems like a somewhat clunky solution. The only other option I can think of is to run the whole file through sed on the mainframe to encode everything.

SAX Parser Error in JDBC Adapter

I am using a JDBC adapter to execute SQL statements during mapping runtime. However, it issues me an error regarding the SAX Parser when I have a '&' character in the SQL statement. I am not able to remove the & since it is in the database that I access and it will result to data inconsistency. I think that when the JDBC adapter of XI converts the SQL string to the XML format, it does not include the amp; string to the &, thus causing the SAX Parser to throw the error.
Is there someway I can configure the JDBC adapter in such a way that it will replace the & with &. Or is there a way to display how the JDBC adapter converts the SQL statement to its the XML representation of it?
Thanks a lot.

Hi,
For this kind of situation use some unique character combination like "#@!" for replacing "&" then parse the document and the restore the "&" later .
For this convert the input stream into Strring and then replace the occurences of "&".
regards.

SAX Parser and special character problem

Hi,
Could anyone help with the following problem?
Background:
1. Using a SAX Parser (Oracle Implementation) to read XML from a CLOB, convert this XML to another format to be inserted in the database.
2. Due to performance issues we parse the input stream from the CLOB.
3. For same reason, we are not using XSL.
This is the problem we face:
1. Values of some of the tags in the XML have special characters (Ex: &, <, >).
2. While using the SAX Parser, the element handler function for the SAX Parser is called by the frame work with the value of these tags broken up with each of these characters being treated as a tag delimiter.
Ex: <Description>SomeText_A & SomeText_B</Description>
is treated as SomeText_A in first call to the handler; SomeText_B in the second call.
The handler function does not get to see the "&" character.
Thus, the final conversion is
Say, <Description> is to be converted to <FreeText>
we, get <FreeText>SomeText_A</FreeText>
<FreeText>SomeText_B</FreeText>
We tried using &; but it then breaks it up into SomeText_A, & and SomeText_B.
How can we get the whole value for the <Description> tag in the characters() function in the SAXParser so that we can convert it to <FreeText>SomeText_A & SomeText_B</FreeText>.
Thanks in advance..
Chirdeep.

We already tried that..looks like the line where I mentioned that it converted the entity referece characters to an ampersand..
"We tried using <entity reference for &> but it then breaks it up into SomeText_A, & and SomeText_B."
null

Unknown entity(Acirc;) included by the SAX parser instead of in UNIX

Similar Messages

Maybe you are looking for