SAX Parser - Decoding request data

I have implemented the SAX Parser on a web application. To do this I create a BufferedReader from the request and then call the SAX parse() method.
BufferedReader reader = request.getReader();
InputSource inputSource = new InputSource( reader );
xmlReader.parse( inputSource );
The problem is that when the XML data is posted to our web application the data from the request is encoded, and thus I need to decode it before calling parse().
Has anyone encountered this problem? If so, what was their solution?

I'm not sure, but are you posting the XML data as a form field? In that case you need to fetch the string data for the given parameter from the request object using getParameter() and feed that to the XML parser. What you are fetching now is the raw HTTP request data.

Similar Messages

Error processing request in sax parser No 'action' attribute found in XML

Hi All,
 I am doing a FILE to JDBC Scenario. I just want to send a data from file to Sql Db table. For this I have written a stored procedure to insert the row in a table.
This is the message mapping for FILE to JDBC .
Sender Receiver
*FILESENDER_MT 1..1 FILESENDER_DT * SPRECEIVER_MT 1..1
 .NO 1..1 xsd:string * Statement 1..1 string
 .Name 1..1 xsd:string *user_PROC 1..1
action 1..1required
 *No
isInput 1..1 string
 type 1..1 string
 *Name
 isInput 1..1 string
 type 1..1 string
Mapped Values....
Statement is mapped with FILESENDER_MT
action attribute is mapped with "EXECUTE" Constant
No is mapped with NO
Name is mapped with Name
for both isInput is mapped with TRUE
for both type is mapped with CHAR
Here is the my stored procedure.....
CREATE PROCEDURE [dbo].[user_PROC]
@NO char(10), @Name char(10) AS
insert into FILE2JDBC values('a','ab')
GO
when i run this stored procedure in Sql directly it was executed successfully....
I have checked In SXMB_MONI status is showing green...
xml messages from SXMB_MONI ....
this is the message from payloads of Inbound Message
<PRE> <?xml version="1.0" encoding="UTF-8" ?>
- <ns0:FILESENDER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
<NO>111</NO>
<NAME>murthy</NAME>
</ns0:FILESENDER_MT></PRE>
this is the message from payloads of Request Message Mapping
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
- <Statement>
- <user_PROC>
<action>EXECUTE</action>
- <NO>
<isInput>TRUE</isInput>
<type>CHAR</type>
</NO>
- <Name>
<isInput>TRUE</isInput>
<type>CHAR</type>
</Name>
</user_PROC>
</Statement>
</ns0:SPRECEIVER_MT>
this is the error showing in runtime workbench>component monitoring->communication channel monitoring-->Receiver Communication Channel....
Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Can any body tell me whether the problem is in Mapping or in Data Type Structure..
Please resolve this issue....
Thanks in Advance,
Murthy.

<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
- <Statement>
- <user_PROC>
<action>EXECUTE</action>
- <NO>
<isInput>TRUE</isInput>
<type>CHAR</type>
</NO>
- <Name>
<isInput>TRUE</isInput>
<type>CHAR</type>
</Name>
</user_PROC>
</Statement>
</ns0:SPRECEIVER_MT>
The Action should be a Attribute of Element user_Proc as,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:SPRECEIVER_MT xmlns:ns0="http://www.prospectadelhi.com/DELHI_FILE2JDBC">
- <Statement>
- <user_PROC action="Execute">- <NO>
<isInput>TRUE</isInput>
<type>CHAR</type>
</NO>
- <Name>
<isInput>TRUE</isInput>
<type>CHAR</type>
</Name>
</user_PROC>
</Statement>
</ns0:SPRECEIVER_MT>
Likewise isInput and Type should be Attributes and not Elements .
Regards
Bhavesh

JDBC receiver adapter - Error processing request in sax parser

Hello,
I want to INSERT idoc data via JDBC adapter into a MS SQL database. After digging through SAP Help, numerous blogs and forum discussions on SDN and even posting an OSS message I still get the same error:
'Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)'
When testing my mapping in the Integration Repository the resulting XML message is:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
 <STATEMENT>
 <T_PD_Employees action="INSERT">
 <access>
 <KeyTag>00088888</KeyTag>
 <PerNo>00088888</PerNo>
 </access>
 </T_PD_Employees>
 </STATEMENT>
</ns0:Employee>
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Can anyone help me solve this problem? I'm lost.
Best regards,
Roelof Jan Bouwknegt

Hi Bhavesh,
I have tried out the change you suggested. Without success. Message I get back is
- 2006-12-28 10:34:08 CET: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
structure in testtool:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
 <STATEMENT>
 <T_PD_Employees action="INSERT">
 <ACCESS>
 <KEYTAG>00088888</KEYTAG>
 <PERNO>00088888</PERNO>
 </ACCESS>
 </T_PD_Employees>
 </STATEMENT>
</ns0:Employee>
Somehow the SAX parser doesn't like the result of my mapping. Maybe there is something wrong with the structure cardinality. Let me describe what I have built:
XSD:
WA_T_PD_Employees - Complex Type
> STATEMENT - Element - Occurence = 1
>> T_PD_Employees - Element - Occurence = 1
>>> STATEMENT - Attribute - Occurence = optional
>>> access - Element - Occurence = 1..Unbounded
Best regards Roelof Jan and thanks for your quick response

Error processing request in sax parser...Excepciu00F3n de E/S: Connection reset

Hello,
I've RFC to JDBC interface.
Sometimes in the RWB me the following error message,
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'LISMATWQ' (structure 'STATEMENT'): java.sql.SQLException: Excepción de E/S: Connection reset</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
How can I prevent?
Thanks very much,

Hello,
the error does not always appear, sometimes the interface works well and others do not (even when the data are the same) I find no solution to this error,
anyone have any idea?
thanks very much

Error processing request in sax parser: Error when executing statement...

Hello,
I want to INSERT data from R/3 System to AS400 via JDBC adapter into a DB2 database. The interfaces from R/3 are Ok. but i have some problems to use the JDBC in DB2 Systems. The message in comunitation channel is:
" Error processing request in sax parser: Error when executing statement for table/stored proc. 'SPE106TST' (structure 'STATEMENT'): java.sql.SQLException: SPE106TST de SADMT1 no válido para la operación."
in the SXMB_MONI -> Request Message Mapping payloads this:
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Please Can anyone help me solve this problem? I'm lost.
Best regards,
Edited by: Nicola Occhipinti on May 22, 2008 7:40 PM

Hi Nicola,
This error occurs when the receiver side structure is incorrect.
Your structure seems to be correct.
Please use lower case for action, access and table.
Please check whether the field names are exactly the same as in the actual Database table sadmt1.SPE106TST.
Check if the table has permissions to write.
You can try an alternate structure without using table tag.
<ns0:MT_XMLSQL_SPEC xmlns:ns0="urn:damm.com/pi/EmployeeMasterData">
<STATEMENT>
<sadmt1.SPE106TST action="INSERT">
<access>
<CODEMP>D</CODEMP>
<CODPRO>00202339</CODPRO>
<NOMPRO>ROSIQUE PERALSGENIS</NOMPRO>
<DIRPRO>GIRONA</DIRPRO>
<POBPRO>S. VICENS HORTS</POBPRO>
<RUTA>0</RUTA>
<ORDEN>0</ORDEN>
<NOMINA>S</NOMINA>
</access>
</sadmt1.SPE106TST>
</STATEMENT>
</ns0:MT_XMLSQL_SPEC>
Hope your problem gets solved.
-Shamly

Error processing request in sax parser

Hi all,
I am doing an asynchronous interface.
It is an interface from IDOC to JDBC. While testing the interface,am getting the following error
"Error processing request in sax parser: Error when executing statement for table/stored proc. 'put_delivery' (structure 'Statement_Delivery'): java.lang.NumberFormatException: null"
Any kind of help is appreciated.
Regards,
Thireesha.

Hello,
Please refer to SAP NOTE 801367.
In advanced tab, use logSQLQuery-->true. Tt will display the actual sql statement in audit log instead of xml format.
You can copy this sql statement and execute directly in database to check the problem.
-Rahul

SAX parser splits up character data; I expected Ign. whitesp

Im am working on a XML parser for loading data from some back
end systems into an Oracle 8i database. I am using the SAX
parser for this purpose. After doing some tests with larger
amounts of XML data (> 1M), I found some unexpected behaviour.
The parser sometimes splits up character data into two chunks of
data. The XML looks as follows:
<TAGNAME> this is the character data </TAGNAME>
The parser raises the following events:
1 startElement name = "TAGNAME"
2 characters chbuf = " "
3 characters chbuf = "this is the character data "
4 endElement name = "TAGNAME"
I expected an ignorableWhitespace event at step 2. The XML
document contains repetitive tagnames. The strange thing about
the parse process is that the parser splits up the character
data only sometimes, and I can't determine any kind of logica
for this behaviour. Most occurrences of exactly the same tagname
and character data are parsed correctly (that is, as I
expected).
Am I dealing with correct behaviour here, or is it a bug??
Rolf.
null

Oracle XML Team wrote:
: Rolf van Deursen (guest) wrote:
: : Im am working on a XML parser for loading data from some
back
: : end systems into an Oracle 8i database. I am using the SAX
: : parser for this purpose. After doing some tests with larger
: : amounts of XML data (> 1M), I found some unexpected
behaviour.
: : The parser sometimes splits up character data into two
chunks
: of
: : data. The XML looks as follows:
: : <TAGNAME> this is the character data </TAGNAME>
: : The parser raises the following events:
: : 1 startElement name = "TAGNAME"
: : 2 characters chbuf = " "
: : 3 characters chbuf = "this is the character data "
: : 4 endElement name = "TAGNAME"
: : I expected an ignorableWhitespace event at step 2. The XML
: : document contains repetitive tagnames. The strange thing
about
: : the parse process is that the parser splits up the character
: : data only sometimes, and I can't determine any kind of
logica
: : for this behaviour. Most occurrences of exactly the same
: tagname
: : and character data are parsed correctly (that is, as I
: : expected).
: : Am I dealing with correct behaviour here, or is it a bug??
: : Rolf.
: The behavior is expected and correct. Could you elaborate on
why
: you would expect the parser to treat the whitespace signalled
in
: step 2 as ignorable?
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
Thank you for your quick response.
In my test XML, there are about 27500 tags containing character
data. All character data starts with a whitespace character.
After parsing the xml, the whitespace of only 5 (!) tags is
treated as a seperate character event (so two character events
are raised in succession). The remaining tags all raise only ONE
character event for the entire character data. I can't explain
the difference in treatment.
null

Unable to open some psd file - "could not complete your request ,unable to parse the path data"

Hi I am unable to open some psd file that i created . I get this message "could not complete your request ,unable to parse the path data" I am curently using cs6. Any idea how to fix it. I tried opening on other computer with photoshop but no luck yet.

Is Vista a supported CS6 system????
Photoshop CS6 / Tech specs
System requirements
Windows
Intel® Pentium® 4 or AMD Athlon® 64 processor
Microsoft® Windows® XP with Service Pack 3 or Windows 7 with Service Pack 1. Adobe® Creative Suite® 5.5 and CS6 applications also support Windows 8. Refer to the CS6 FAQ for more information about Windows 8 support.*
1GB of RAM
1GB of available hard-disk space for installation; additional free space required during installation (cannot install on removable flash storage devices)
1024x768 display (1280x800 recommended) with 16-bit color and 256MB (512MB recommended) of VRAM
OpenGL 2.0–capable system
DVD-ROM drive
This software will not operate without activation. Broadband Internet connection and registration are required for software activation, validation of subscriptions, and access to online services.† Phone activation is not available.

Parsing WBXML POSt Request Data

Hi!
I want to read WBXML formatted SyncML data sent by a Mobile Device
There is a servlets at server side which receives the http request of the
device and tries to read the contents of the POST request data by using .
Request.getInputStream(); method....
I then Pass this data to a method "wbxmlToXml(req.getInputStream().toString().getBytes()) "
I am using kxml as XML parsing the Initial Lines of the method are as following
public static String wbxmlToXml(byte[] wbxml) throws IOException {
String xml = null;
try {
// Construct an InputStream on byte[] to be used by WbxmlParser
ByteArrayInputStream in = new ByteArrayInputStream(wbxml);
AbstractXmlParser parser; //org.kxml.parser.AbstractXmlParser
parser = new WbxmlParser(in);
// Construct a DOM Document to parse WBXML
Document document = new Document();
document.parse(parser);------------------> Error :java.io.IOException: id 54 undef.
I get "java.io.IOException: id 54 undef." error as mentioned above.
Please somebody guide regarding this problem
Regards,
Maneesha

The problem is solved! The error was in the post request. At the end of the query parameter was . For spa504,
spa303,spa508 it was not important, but for spa525 important. Once I removed this parameter from the request, the phone immediately began to dial.
Thanks for the help!
That's a valid request for spa525G2:
http://192.168.2.113/CGI/Execute
POST / CGI / Execute HTTP/1.1
Host: 192.168.2.113
Accept: * / *
Content-Type: text / xml; charset = "UTF-8"
Content-Length: 92
XML =

Code to read xml file and display that data using sax parser

Hai
My problem I have to read a xml file and display the contents of the file on console using sax parser.

here you go

RE: (forte-users) SAX Parser

I would be interested to see TechNote 11811. I just tried the Forté support
web site and couldn't get it. Can anyone help?
Thanks,
Nick.
-----Original Message-----
From: Zee Khan [mailto:[email protected]]
Sent: Tuesday, August 24, 1999 10:08 AM
To: [email protected]
Cc: [email protected]
Subject: RE: (forte-users) SAX Parser
Forte recommends not using DOM for 'documents with large
number of tags'
(TechNote 11811) so I am using SAX.
Any thoughts/suggestions would be welcome,
thanks,
>From: "Jeanne Hesler" <[email protected]>
>To: "'Zee Khan'" <[email protected]>,
<[email protected]>
>Subject: RE: (forte-users) SAX Parser
>Date: Tue, 24 Aug 1999 08:48:23 -0500
>
>Out of curiosity, is it the node structure that you are
trying to avoid,
>or is it the DOM itself? Can you share some of your
reasons? It would
>seem to me that a node or tree structure would be ideally
suited for
>representing the complex structures that you describe.
>
>Jeanne
>=====================================================
>Jeanne Hesler <[email protected]>
>MSF&W Software
>Product Development
>(217) 698-3535 ext. 207
>http://www.msfw.com
>=====================================================
>/\ Imaging Developer - the only imaging product
>\/ integrated into the Forte Development Environment
>=====================================================
>
>
>-----Original Message-----
>From: Zee Khan [mailto:[email protected]]
>Sent: Monday, August 23, 1999 10:32 AM
>To: [email protected]
>Subject: (forte-users) SAX Parser
>
>
>I am using the SAX parser to parse some complex XML.
>
>My problem comes with complex data structures. There
>are several embedded structures, how are these best
>reflected with a SAX parser.
>
>(I guess one solution is to use DOM which returns
>a node structure, but I want to avoid this)
>
>thanks in advace,
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>--
>For the archives, go to:
http://lists.sageit.com/forte-users
>To unsubscribe send in a new email the word:
>'Unsubscribe' to: [email protected]
>
>--
>For the archives, go to:
http://lists.sageit.com/forte-users and use
>the login: forte and the password: archive. To unsubscribe,
send in a new
>email the word: 'Unsubscribe' to:
[email protected]
>
Get Your Private, Free Email at http://www.hotmail.com
For the archives, go to: http://lists.sageit.com/forte-users
and use
the login: forte and the password: archive. To unsubscribe,
send in a new
email the word: 'Unsubscribe' to:
[email protected]

I would be interested to see TechNote 11811. I just tried the Forté support
web site and couldn't get it. Can anyone help?
Thanks,
Nick.
-----Original Message-----
From: Zee Khan [mailto:[email protected]]
Sent: Tuesday, August 24, 1999 10:08 AM
To: [email protected]
Cc: [email protected]
Subject: RE: (forte-users) SAX Parser
Forte recommends not using DOM for 'documents with large
number of tags'
(TechNote 11811) so I am using SAX.
Any thoughts/suggestions would be welcome,
thanks,
>From: "Jeanne Hesler" <[email protected]>
>To: "'Zee Khan'" <[email protected]>,
<[email protected]>
>Subject: RE: (forte-users) SAX Parser
>Date: Tue, 24 Aug 1999 08:48:23 -0500
>
>Out of curiosity, is it the node structure that you are
trying to avoid,
>or is it the DOM itself? Can you share some of your
reasons? It would
>seem to me that a node or tree structure would be ideally
suited for
>representing the complex structures that you describe.
>
>Jeanne
>=====================================================
>Jeanne Hesler <[email protected]>
>MSF&W Software
>Product Development
>(217) 698-3535 ext. 207
>http://www.msfw.com
>=====================================================
>/\ Imaging Developer - the only imaging product
>\/ integrated into the Forte Development Environment
>=====================================================
>
>
>-----Original Message-----
>From: Zee Khan [mailto:[email protected]]
>Sent: Monday, August 23, 1999 10:32 AM
>To: [email protected]
>Subject: (forte-users) SAX Parser
>
>
>I am using the SAX parser to parse some complex XML.
>
>My problem comes with complex data structures. There
>are several embedded structures, how are these best
>reflected with a SAX parser.
>
>(I guess one solution is to use DOM which returns
>a node structure, but I want to avoid this)
>
>thanks in advace,
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>--
>For the archives, go to:
http://lists.sageit.com/forte-users
>To unsubscribe send in a new email the word:
>'Unsubscribe' to: [email protected]
>
>--
>For the archives, go to:
http://lists.sageit.com/forte-users and use
>the login: forte and the password: archive. To unsubscribe,
send in a new
>email the word: 'Unsubscribe' to:
[email protected]
>
Get Your Private, Free Email at http://www.hotmail.com
For the archives, go to: http://lists.sageit.com/forte-users
and use
the login: forte and the password: archive. To unsubscribe,
send in a new
email the word: 'Unsubscribe' to:
[email protected]

I need help using a SAX parser

Hello,
I have a class that goes out to the web and retrieves an xml document w/o ever writing it to disk. I like to parse that object using SAX and a class that extends HandlerBase. Can any one show me how to parse an xml document that lives in memory rather than in a file? I've found many examples, but all of them assume you are reading from a file system. Any help is greatly appreciated.
Here is the jist of my code :
// Class 1 makes a request to another server based on some variable data. I've created a messenger object that handles all of the communications and returns the data in a DataInputStream
XMLMessage xml = new XMLMessage();
xml.createRequest(args[0],args[1],args[2]);
XMLMessenger messenger = new XMLMessenger(xml.getDoc());
DataInputStream dis = messenger.transferDocument();
ResponseObj resp = new ResponseObj();
resp.read(dis);
System.out.println(resp.getvalue1() + "*" + resp.getvalue2()+ "*");
// Class 2 is the ResponseObj and I want to use something similar to this read method, but
// I can't get it to work with a data stream, instead of a string that represents a file.
public void read(String filename) throws java.lang.Exception {
Class c = Class.forName("com.ibm.xml.parser.SAXDriver");
     org.xml.sax.Parser parser = (org.xml.sax.Parser)c.newInstance();
     parser.setDocumentHandler(this);
     parser.parse(filename);

Thanks for you help. I've modified my read() method to work like this :
org.xml.sax.Parser parser = new com.ibm.xml.parser.SAXDriver();
parser.setDocumentHandler(this);
InputSource is = new InputSource(dis);
parser.parse(is);
This makes sense, but I'm still not getting any thing returned from the startElement(),characters(), or endElement() methods. It reports no errors, it just doesn't happen. Do you have any suggestions on how to debug this? I'm stumped, but really need to get this working.

Another SAX Parser Question

Hi All,
I get an xml file by making an http request. The name of the DTD comes as a relative path in the response xml file.
Questions
1. Is there a way to handle this
2. I read somewhere that i could avoid looking at the DTD alltogether,
can someone show me how with a sample code.
Kind regards

Nothing seems to help, Please help,
Im using jdk1.4 A full source codee would be great.
Thanks in advance.
This is the trace and the Code follows below:
C:\codes\parser>java -classpath xerces.jar;. ReaderConnector
Initiating Connection to System URL = http://a.b.c.com:5280/vega/
request?method=login&ui=ch16132-user&pwd=pass
Connected ..
Opening Stream for reading data
Got input stream java.io.BufferedInputStream@19821f
Got reader java.io.BufferedReader@addbf1
Read login file ...
Parsing ...
Start of Login document
\vega\xml\xrf.dtd (The system cannot find the path)
Parsed
********************************3
*****Code*****
import javax.xml.parsers.*;
import org.xml.sax.*;
import java.io.*;
import java.util.*;
import java.net.*;
import org.xml.sax.EntityResolver;
import org.xml.sax.InputSource;
import org.xml.sax.helpers.*;
import org.xml.sax.ContentHandler;
import org.xml.sax.Locator;
import org.xml.sax.Attributes;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
* @author JAVA
* @version
public class ReaderConnector{
 public ReaderConnector() {
 /*Login URl doesnt change*/
 private String loginUrl = "http://a.b.c.com:5280/vega/request?method=login&ui=ch16132-user&pwd=pass";
 //private String loginUrl = "c://temp/test.xml";
 private String sessionId;
 public String getSessionId(){
 if(sessionId == null){
 createConnection();
 return sessionId;
 }else{
 return sessionId;
 public void createConnection() {
 DataInputStream inputStream = null;
 BufferedReader reader = null;
 InputStream in = null;
 FileOutputStream fos= null;
 //System.setProperty("javax.xml.parsers.SAXParserFactory", "org.apache.xerces.jaxp.SAXParserFactoryImpl");
 try {
 URL url = new URL(loginUrl);
 URLConnection connection = url.openConnection();
 connection.setUseCaches(false);
 System.out.println(" Initiating Connection to System URL = " + "http://a.b.c.com:5280/vega/request?method=login&ui=ch16132-usr&pwd=pass");
 connection.connect();
 System.out.println(" Connected ..");
 System.out.println(" Opening Stream for reading data ");
 in = new BufferedInputStream (new DataInputStream (connection.getInputStream()));
 System.out.println("Got input stream "+ in);
 reader = new BufferedReader(new InputStreamReader(new BufferedInputStream(in)));
 System.out.println("Got reader "+ reader);
 System.out.println("Read login file ...");
 parseStream(reader);
 }catch (Exception e) {
 System.out.println(e.getMessage());
 }finally {
 try {
 in.close();
 //fos.close();
 if (inputStream != null) {
 inputStream.close();
 if(reader!=null){
 reader.close();
 } catch (Exception ex) {
 System.out.println(ex.getMessage());
 ex.printStackTrace();
 public void parseStream(BufferedReader br){
 System.out.println("Parsing ...");
 try{
 /*SAXParserFactory spf = SAXParserFactory.newInstance();
 spf.setValidating(false);
 spf.setNamespaceAware(false);
 org.xml.sax.Parser sp = (org.xml.sax.Parser)spf.newSAXParser();
 //sp.isValidating(false);
 sp.setDTDHandler(new Resolver());
 //sp.setDocumentHandler(new Handler());
 InputSource iSource = new InputSource(br);
 Handler h = new Handler();
 sp.parse(iSource ); */
 XMLReader parser;
 parser = XMLReaderFactory.createXMLReader();
 parser.setContentHandler(new Handler());
 parser.setDTDHandler(new Resolver());
 parser.parse(new InputSource(br));
 }catch(Exception e){
 System.out.println(e.getMessage());
 System.out.println("Parsed");
 public static void main(String [] args){
 ReaderConnector connector = new ReaderConnector ();
 //connector.testParsing("c://temp/test.xml");
 connector.createConnection();
 private class Resolver extends DefaultHandler{
 public InputSource resolveEntity(String publicId, String systemId) throws SAXException {
 System.err.println(publicId + " ! " + systemId);
 if (("/vega/xml/xrf.dtd").equalsIgnoreCase(systemId) || ("/vega/xml/xrf.dtd").equalsIgnoreCase(publicId))
 try {
 return new InputSource(new URL("http://a.b.c.com:5280"+systemId).openStream());
 } catch (MalformedURLException e) {
 throw new SAXException(e);
 } catch (IOException e) {
 throw new SAXException(e);
 else return null;
 private class Handler extends org.xml.sax.helpers.DefaultHandler{
 public void startDocument() throws org.xml.sax.SAXException {
 System.out.println("Start of Login document");
 public void endDocument() throws org.xml.sax.SAXException {
 System.out.println("End of document");
 public void ignorableWhitespace(char[] values, int param, int param2) throws org.xml.sax.SAXException {
 public void endElement(java.lang.String str, java.lang.String str1, java.lang.String str2) throws org.xml.sax.SAXException {
 System.out.println("End of element reached: str, str1, str2 "+ str + " , "+ str1 + " , "+ str2);
 System.out.println("Session ID "+ sessionId);
 public void skippedEntity(java.lang.String str) throws org.xml.sax.SAXException {
 public void processingInstruction(java.lang.String str, java.lang.String str1) throws org.xml.sax.SAXException {
 public void startElement(java.lang.String str, java.lang.String str1, java.lang.String str2, org.xml.sax.Attributes attributes) throws org.xml.sax.SAXException {
 if(("A").equals(str2)){
 for(int i=0; i< attributes.getLength();i++){
 System.out.println("Attribute "+ i + ", Name, Value "+ attributes.getQName(i) + ", " + attributes.getValue(i));
 if(("v").equalsIgnoreCase(attributes.getQName(i)))
 sessionId = attributes.getValue(i);
 public void endPrefixMapping(java.lang.String str) throws org.xml.sax.SAXException {
 public void startPrefixMapping(java.lang.String str, java.lang.String str1) throws org.xml.sax.SAXException {
 public void characters(char[] values, int param, int param2) throws org.xml.sax.SAXException {
 String s = new String(values);
 String text = s.substring(param, param+param2);
 public void setDocumentLocator(org.xml.sax.Locator locator) {
XML File
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE XRF (View Source for full doctype...)>
- <XRF r="2.11.1" c="" g="" u="ch16132-user" k="" d="20050614" t="151146">
<A k="i0005" n="3" v="1964216949" />
</XRF>
****When you view source*******
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE XRF SYSTEM "/vega/xml/xrf.dtd">
<XRF r="2.11.1" c="" g="" u="ch16132-user" k="" d="20050614" t="151722">
<A k="i0005" n="3" v="350287547"/>
</XRF>

How to deal with empty tags in a SAX Parser

Hi,
I hope someone can help me with the problem I am having!
Basically, I have written an xml-editor application. When an XML file is selected, I parse the file with a SAX parser and save the start and end locations of all the tags and character data. This enables me to display the xml file with the tags all nicely formatted with pretty colours. Truly it is a Joy To Behold. However, I have a problem with tags in this form:
<package name="boo"/>
because the SAX parser treats them like this:
<package name = boo>
</package>
for various complex reasons the latter is unaccetable so my question is: Is there some fiendishly clever method to detect tags of this type as they occur, so that I can treat them accordingly?
Thanks,
Chris

I have spent some time on googling for code doing this, but found nothing better, than I had to write in by myself.
So, it would be something like this. Enjoy :)
package comd;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.SAXException;
import org.xml.sax.Attributes;
import java.util.Stack;
import java.util.Enumeration;
public class EmptyTagsHandler extends DefaultHandler {
 private StringBuilder xmlBuilder;
 private Stack<XmlElement> elementStack;
 private String processedXml;
 private class XmlElement{
 private String name;
 private boolean isEmpty = true;
 public XmlElement(String name) {
 this.name = name;
 public void setNotEmpty(){
 isEmpty = false;
 public EmptyTagsHandler(){
 xmlBuilder = new StringBuilder();
 elementStack = new Stack();
 private String getElementXPath(){
 StringBuilder builder = new StringBuilder();
 for (Enumeration en=elementStack.elements();en.hasMoreElements();){
 builder.append(en.nextElement());
 builder.append("/");
 return builder.toString();
 public String getXml(){
 return processedXml;
 public void startDocument() throws SAXException {
 xmlBuilder = new StringBuilder();
 elementStack.clear();
 processedXml = null;
 public void endDocument() throws SAXException {
 processedXml = xmlBuilder.toString();
 public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException {
 if (!elementStack.empty()) {
 XmlElement elem = elementStack.peek();
 elem.setNotEmpty();
 xmlBuilder.append("<");
 xmlBuilder.append(qName);
 for (int i=0; i<attributes.getLength();i++){
 xmlBuilder.append(" ");
 xmlBuilder.append(attributes.getQName(i));
 xmlBuilder.append("=");
 xmlBuilder.append(attributes.getValue(i));
 xmlBuilder.append(">");
 elementStack.push(new XmlElement(qName));
 public void endElement(String uri, String localName, String qName) throws SAXException {
 XmlElement elem = elementStack.peek();
 if (elem.isEmpty) {
 xmlBuilder.insert(xmlBuilder.length()-1, "/");
 } else {
 xmlBuilder.append("</");
 xmlBuilder.append(qName);
 xmlBuilder.append(">");
 elementStack.pop();
 public void characters(char ch[], int start, int length) throws SAXException {
 if (!elementStack.empty()) {
 XmlElement elem = elementStack.peek();
 elem.setNotEmpty();
 String str = new String(ch, start, length);
 xmlBuilder.append(str);
 public void ignorableWhitespace(char ch[], int start, int length) throws SAXException {
 String str = new String(ch, start, length);
 xmlBuilder.append(str);
}

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?

SAX Parser - Decoding request data

Similar Messages

Maybe you are looking for