Error in parsing taglib 'NavigationTagLibrary'

Hello Tiberiu,
You have referenced a wrong TLD file, here is the right one:
<property name="NavigationTagLibrary" value="/SERVICE/com.sap.portal.navigation.navigationtaglibrary/taglib/TagLibrary.tld"/>
Check the link for more help on TLDs:
http://help.sap.com/saphelp_nw04/helpdata/en/43/11a2db95de567fe10000000a11466f/content.htm
Greetings,
Praveen Gudapati

Hi Praveen,
I am facing a similar situation! I do have few com.sap.portal.navigation.*.jar, except this com.sap.portal.navigation.navigationtaglibrary! Does this come with standard portal installations?
I am checking in Support Desk --> deployment Overview --
I don't see com.sap.portal.navigation.navigationtaglibrary in the list.
Any ideas on this will be very useful!

Similar Messages

Error in parsing taglib 'customtag' tag in web.xml or .tld file of the tagl

Hi
While execution Portal application, I am getting error," Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library."
Complete stack is
>>#1.5 #005056AE006400690000002000000A440004BA8F3ECB004A#1331024303056#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#M1005000#6994##99593FD6676911E1807500000041A352#99593fd6676911e1807500000041a352-0#99593fd6676911e1807500000041a352#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###02:28_06/03/12_0020_4301650
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException: Error in parsing taglib 'customtag' tag in web.xml or .tld file of the taglib library.
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:189)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse0(JspDirective.java:162)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.JspDirective.parse(JspDirective.java:117)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ElementCollection.parse(ElementCollection.java:86)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.syntax.ParserImpl.parse(ParserImpl.java:595)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2170)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:133)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Regards
Pratyush

Hi,
See the following guide and make sure to carefully follow all instructions.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40599e45-8cf9-2910-cbaa-d4cd8e15ff34?QuickLink=index&overridelayout=true&14770392545262]
Regards,
Alex

Error in parsing taglib taglib tag in web.xml or .tld file of the taglib

Hi All,
I have added ResourceBundle.tld file in following path : /PORTAL-INF/taglib/tld/
I have added portalapp.xml file following entry :
<property name="/PORTAL-INF/taglib/tld/ResourceBundle.tld" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
I have added jsp file following entry :
<%@ taglib uri="/PORTAL-INF/taglib/tld/ResourceBundle.tld" prefix="bundle" %>
I am getting the following the error: Error in parsing taglib taglib tag in web.xml or .tld file of the taglib library
can you tell me where i am giving the wrong.
Regards
Siva

hi rabih,
in jsp..
<%@ taglib uri="tagLib" prefix="bundle" %>
in portalapp.xml
<component-profile>
<property name="tagLib" value="/PORTAL-INF/taglib/tld/ResourceBundle.tld"/>
</component-profile>
it may help u..
regards,
Chinnadurai.R

Error in parsing taglib

Hi *
does anybody know how I can resolve my problem?
Environment: EP 6.40 STack 10, simple jsypdynpage
jsp:
<%@ taglib uri="tagLib" prefix="hbj" %>
<hbj:content id="myContext" >
<hbj:page title="Yet Another Page">
 <hbj:form>
 test
 </hbj:form>
</hbj:page>
</hbj:content>
portalapp.xml:
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
 <property name="SharingReference" value="htmlb"/>
</application-config>
<components>
 <component name="CatManNavigationView">
 </component>
 <component name="JNetJsp">
 <component-config>
 <property name="ComponentType" value="jspnative"/>
 <property name="JSP" value="private/jnet.jsp"/>
 </component-config>
 <component-profile/>
 </component>
 <component name="TreeTableView">
 <component-config>
 <property name="SecurityZone" value="com.sap.portal.pdk/low_safety"/>
 <property name="ClassName" value="TreeTableView"/>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-config>
 <component-profile>
 <property name="tabStripItem2Width" value="300">
 <property name="personalization" value="dialog"/>
 </property>
 <property name="tabStripItem2Tooltip" value="Tooltip 2">
 <property name="personalization" value="dialog"/>
 </property>
 <property name="tooltip" value="Tooltip">
 <property name="personalization" value="dialog"/>
 </property>
 </component-profile>
 </component>
</components>
<services/>
</application>
ERROR:
Caused by: com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException:
Error in parsing taglib 'tagLib' tag in web.xml or .tld file of the taglib library.
thanks in advance

Hi
Can you please explain what i have done wrong ? I am getting error - Error in parsing taglib
My forum query is below
Create simple taglib for jsp but getting error of parsing taglib path
Thanks
Sachin

My application gives "Error in parsing taglib 'tagLib' tag in web.xml "

Hi ,
My Portal application developed completely on JSP Dynpages and JSPs gives at times the following error
"Error in parsing taglib 'tagLib' tag in web.xml or .tld file of the taglib library.."
I know that this error comes when the taglib declared in the jsp and portalapp.xml doesn't match. But I have made sure that they are the same.
Can anyone give me an opinion as to why this problem is occuring inspite of making sure that the taglib declaration are same in jsp and portalapp.xml.
Is the problem on the server side??
Valuable suggestions would be rewarded!!
-Thanks
Padmarajan.

Hi Anagha,
No the application is accessed using an http link.
I am unable to make out why this error comes up only once in a while and when you refresh the screen it starts working fine.
This is my big issue because when
-Thanks
Padmarajan.

Error in parsing the taglib tag in the JSP page

Hi
We are trying to deploy and run a Web Application in CE 7.1 SP01. We are successful in deploying and running servlet based web pages, but when it comes to JSP's the taglibs are not parsed and we get the following error message
Runtime error in processing of the JSP file E:\usr\sap\CE1\J01\j2ee\cluster\apps\sap.com\TestNWEAR\servlet_jsp\TestNW\root\admin\main.jsp.
The error is: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [webwork]. Possible reason - validation failed. Check if your TLD is valid against its scheme.02004C4F4F5000190000004E000013400191D308B45
Processing HTTP request to servlet [jsp] finished with error.
The error is: java.io.FileNotFoundException: E:\usr\sap\CE1\J01\j2ee\cluster\apps\sap.com\TestNWEAR\servlet_jsp\TestNW\root\admin\webwork (The system cannot find the file specified)02004C4F4F50001900000051000013400191D308B45AF1AB
We followed the below weblog to correct the TLD's in JAVA EE 5 @ SAP but it did not work for us.
/people/community.user/blog/2006/10/13/porting-the-java-blueprint-solutions-catalogue-applications-to-sap-netweaver-application-server-java-ee-5-edition
Any immediate help will be rewarded with full points
Thanks in advance
Lakshmi
Edited by: lakshmi N Munnungi on May 5, 2008 11:36 PM
Edited by: lakshmi N Munnungi on May 5, 2008 11:39 PM

Hi Lakshmi,
I have also the same problem. If you have found the solution please post it thanks,
Thanks,
Tariq

Error in using taglib uri in jsp

When i write the following code in my jsp to use the tags, i got the error -
JSP Parsing Error:The absolute uri: http://java.sun.com/jsf/html cannot be resolved in either web.xml or the jar files deployed with this application
And when i used the tld (html_basic.tld & jsf_core.tld), it gave me the error
JSP Parsing Error:Failed to load or instantiate TagLibraryValidator class: com.sun.faces.taglib.html_basic.HtmlBasicValidator

you can use
<taglib>
<taglib-uri>/WEB-INF/html-basic.tld</taglib-uri>
<taglib-location>
/WEB-INF/html-basic.tld
</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/jsf-core.tld</taglib-uri>
<taglib-location>
/WEB-INF/jsf-core.tld
</taglib-location>
</taglib>
in your web.xml

Error about custom taglib

i want to have a test and write some simple code to test.
 i add the class beneath the meta-inf/classes.
 when i check the weblogic5.1 doc,i find a strange sentence:"If you are
 deploying your JSP pages using the standard weblogic.properties file (in the
 default servlet context),
 create a directory called WEB-INF under the documentRoot, and place the TLD
 file under the WEB-INF directory.
 All content beneath the WEB-INF directory is non-public and will not be
 server over HTTP by the WebLogic Server. "
 the first sentence before the comma and the second looks contrary,can any
 guru clear my confusion?
 my jsp code is:
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML>
 <HEAD>
 <TITLE>SeleceTag test</TITLE>
 <LINK REL=STYLESHEET
 HREF="JSP-Styles.css"
 TYPE="text/css">
 </HEAD>
 <BODY>
 <H1>SeleceTag test</H1>
 <%@ taglib uri="JHJ-taglib.tld" prefix="JHJ" %>
 <JHJ:test/>
 </BODY>
 </HTML>
 when compile it,it report:/SelectTag.jsp(14): Could not parse deployment
 descriptor: org.xml.sax.SAXParseException: Could not parse taglib, starting
 at line 5


The second 2 errors were solved by copying the ExpenditureTypeNoAwardLovVORowImpl.class to my myclasses directory under oracle/apps/icx/lov/server and then recompiling.
I'm still not sure why an empty .java file was added to my project causing the first error. I was doing this extension on a machine with Windows 2000 and I had created a new workspace (other than toolbox.jws) when I got this error. When I did the same extension on a machine with Windows XP and in the toolbax.jws workspace, the empty .java file didn't get added to my project and I didn't get the first compile error. Not sure if one of these variables was the cause.

Getting the following error while parsing the values usng xml parser

Hi
I am getting the following error while parsing the values using the code in r12 instance on linux
declare
XML_PARSER XMLPARSER.PARSER;
DOC XMLDOM.DOMDOCUMENT;
DOCELEMENT DBMS_XMLDOM.DOMELEMENT;
BEGIN
-- NEW PARSER
XML_PARSER := XMLPARSER.NEWPARSER;
-- SET SOME CHARACTERISTICS
XMLPARSER.SETVALIDATIONMODE(XML_PARSER, FALSE);
     IF P_DIR IS NOT NULL AND P_FILENAME IS NOT NULL
     THEN
     FND_FILE.PUT_LINE(FND_FILE.LOG,'DIRECTORY FOUND'||'-'||P_DIR);
     XMLPARSER.SETBASEDIR(XML_PARSER, P_DIR);
     -- PARSE INPUT FILE
     FND_FILE.PUT_LINE(FND_FILE.LOG,'FILE FOUND'||'-'||P_FILENAME);
     XMLPARSER.PARSE(XML_PARSER, P_DIR || '/' || P_FILENAME);
     -- GET DOCUMENT
     DOC := XMLPARSER.GETDOCUMENT(XML_PARSER);
     LOAD_SUPP(doc);
     ELSE
     DBMS_OUTPUT.PUT_LINE('DIRACTORY/FILENAME CANNOT BE NULL');
     END IF;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('DATA NOTINSERTED'||sqlerrm);
     ROLLBACK;
END
I am getting the following error
DIRACTORYL-/home/appldevORA-0000: normal, successful completion
FILE NAME-suppliersample_data.xmlORA-0000: normal, successful completion
DATA NOTINSERTEDORA-31001: Invalid resource handle or path name "/home/appldev/suppliersample_data.xml"
ORA-06512: at "SYS.XDBURITYPE", line 11
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 142
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-29280: invalid directory path
It could be great if some one could give a suggestion/solution.
Thanks
Ajesh

Besides this is not the correct forum try to google the error message first before posting:
http://ora-29280.ora-code.com/
cheers

Error while parsing or executing XML-SQL document

friends,
my scenario is based on file to jdbc.i am facing an error in receiver CC in RWB.
The error states that '
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'MATMAS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.'
My SOAP xml message is
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:TimeSent>2008-02-06T22:30:21Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>ECC</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>BS_JDBC</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://file_to_jdbc">MI_JDBC_RECEIVER</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">
sapecc50\sapmnt\trans</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">UTF-8</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">matmas1.txt</sap:Record>
</sap:DynamicConfiguration>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info />
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="IS">is.01.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:22Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
</sap:Hop>
</sap:HopList>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
and payload message is
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
- <STATEMENT>
- <ROW action="INSERT">
<TABLE>MATMAS</TABLE>
- <access>
<MATNR>38</MATNR>
<MTART>HALB</MTART>
<MATKL>00107</MATKL>
<MEINS>pc</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>10</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>88</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>13</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>89</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.03.02</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>14</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>98</MATNR>
<MTART>HALB</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.09.01</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>170</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2005.03.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>178</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.03.06</ERSDA>
<BRGEW>3</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>188</MATNR>
<MTART>NLAG</MTART>
<MATKL>5</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.05.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>288</MATNR>
<MTART>HALB</MTART>
<MATKL>101</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.02.11</ERSDA>
<BRGEW>5</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>358</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.09.09</ERSDA>
<BRGEW>500</BRGEW>
<NTGEW>500</NTGEW>
<GEWEI>G</GEWEI>
</access>
- <access>
<MATNR>359</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.08.01</ERSDA>
<BRGEW>20</BRGEW>
<NTGEW>10</NTGEW>
<GEWEI>G</GEWEI>
</access>
</ROW>
</STATEMENT>
</ns0:MT_JDBC_RECEIVER>
Could anybody help me in sorting out this issue.My advance thanks

hi,
ypur structure is bad defined.
if you want to do an insert, the DT should be
<ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
___<StatementName>
______<dbTableName action=INSERT>
_____<table>MATMAS</table>
_______ <access>
___________<MATNR>38</MATNR>
___________<MTART>HALB</MTART>
___________<MATKL>00107</MATKL>
___________<MEINS>pc</MEINS>
___________<ERSDA>2008.04.05</ERSDA>
___________<BRGEW>10</BRGEW>
___________<NTGEW>12</NTGEW>
___________<GEWEI>KG</GEWEI>
______</access>
_____</dbTableName>
__ </StatementName>
</ns0:MT_JDBC_RECEIVER>
the ROW field is used when you wait receive data from DB for example you execute and SQL Query from Sender communication channel "SELECT name FROM TABLE Names"
so, the result of this query would be, for example:
<row>
____<name>joge</name>
</row>
<row>
____<name>pepe</name>
</row>
<row>
____<name>nicola</name>
</row>
See this link
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:40 AM
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:42 AM

IMAP error messages "Error while parsing IMAP response"

I'm getting thousands of IMAP errors every hour, can I shut those off?
My console log is flooded with them and it keeps me from seeing anything else
in the system log. The IMAP errors happen continuously while Mail.app is running.
It looks like debug output from Mail.app !?!
IMAP server is Beehive Server -- it's my company email so I need to use it.
Windows Outlook (Windows 7) shows no errors, possibly they're silently ignored
on Windows. My disk is writing almost continuously when Mail.appo is running.
Sample error: (thousands are generated per hour)
Apr 8 10:29:18 Js-Coolio-iMac.local Mail[22903]: Error while parsing IMAP response (null): Incomplete response
 Remaining text: < Gian Luigi >
 Full text: < Gian Luigi >
Any idea how to shut these off? I reinstalled Mavericks, no improvement as expected
since this seems to be Mail complaining about IMAP protocol issues.
Thanks in advance for any suggestions. And yes I've rebooted, reinstalled the IMAP account,
reinstalled Mavericks, etc.
Entrecheck follows...
Hardware Information:
 iMac (27-inch, Late 2009)
 iMac - model: iMac11,1
 1 2.8 GHz Intel Core i7 CPU: 4 cores
 12 GB RAM
Video Information:
 ATI Radeon HD 4850 - VRAM: 512 MB
System Software:
 OS X 10.9.2 (13C64) - Uptime: 9 days 20:39:45
Disk Information:
 ST31000528ASQ disk0 : (1 TB)
 EFI (disk0s1) <not mounted>: 209.7 MB
 Macintosh HD (disk0s2) / [Startup]: 999.35 GB (801.18 GB free)
 Recovery HD (disk0s3) <not mounted>: 650 MB
 OPTIARC DVD RW AD-5680H
USB Information:
 Seagate Backup+ Desk 3 TB
 disk1s1 (disk1s1) <not mounted>: 209.7 MB
 JOHN TM (disk1s2) /Volumes/JOHN TM: 2 TB (1.81 TB free)
 LIU TM (disk1s3) /Volumes/LIU TM: 500 GB (203.45 GB free)
 Untitled 3 (disk1s4) /Volumes/Untitled 3: 499.39 GB (498.94 GB free)
 Apple Inc. BRCM2046 Hub
 Apple Inc. Bluetooth USB Host Controller
 Apple Internal Memory Card Reader
 Griffin Technology, Inc iMic USB audio system
 Apple, Inc. Keyboard Hub
 Logitech USB Trackball
 Apple, Inc Apple Keyboard
 Apple Computer, Inc. IR Receiver
 Apple Inc. Built-in iSight
FireWire Information:
Thunderbolt Information:
Configuration files:
 /etc/hosts - Count: 4
Kernel Extensions:
 com.seagate.driver.PowSecDriverCore (5.2.4 - SDK 10.4)
 com.seagate.driver.PowSecLeafDriver_10_5 (5.2.4 - SDK 10.5)
Launch Daemons:
 [System] com.adobe.fpsaud.plist 3rd-Party support link
 [System] com.barebones.textwrangler.plist 3rd-Party support link
 [System] com.oracle.java.Helper-Tool.plist 3rd-Party support link
Launch Agents:
 [System] com.oracle.java.Java-Updater.plist 3rd-Party support link
 [System] net.culater.SIMBL.Agent.plist 3rd-Party support link
User Launch Agents:
 [not loaded] com.adobe.ARM.[...].plist 3rd-Party support link
 [not loaded] com.google.keystone.agent.plist 3rd-Party support link
 [not loaded] com.leadertech.PowerRegister.SEA1.7c77b2ab072a21a06107fccae868ff4b.plist 3rd-Party support link
 [not loaded] com.valvesoftware.steamclean.plist 3rd-Party support link
User Login Items:
 Flux
 smcFanControl
 SpeechSynthesisServer
 AdobeResourceSynchronizer
 Flux (13.0)
Internet Plug-ins:
 Default Browser: Version: 537 - SDK 10.9
 Flip4Mac WMV Plugin: Version: 3.1.0.24 - SDK 10.8 3rd-Party support link
 AmazonMP3DownloaderPlugin101750: Version: AmazonMP3DownloaderPlugin 1.0.17 - SDK 10.4 3rd-Party support link
 RealPlayer Plugin: Version: (null) 3rd-Party support link
 AdobePDFViewerNPAPI: Version: 10.1.3 3rd-Party support link
 FlashPlayer-10.6: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
 MRJPlugin: Version: 1.0-JEP-0.9.0 3rd-Party support link
 QuickTime Plugin: Version: 7.7.3
 Flash Player: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
 iPhotoPhotocast: Version: 7.0
 AdobePDFViewer: Version: 10.1.3 3rd-Party support link
 JavaAppletPlugin: Version: Java 7 Update 51 3rd-Party support link
Safari Extensions:
 Ghostery: Version: 5.1.0
 AdBlock: Version: 2.6.18
 Turn Off the Lights: Version: 2.3.0.5
Audio Plug-ins:
 BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
 AirPlay: Version: 2.0 - SDK 10.9
 AppleAVBAudio: Version: 203.2 - SDK 10.9
 iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
 Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
 WebEx: Version: 1.0 3rd-Party support link
 WebEx64: Version: 1.0 - SDK 10.5 3rd-Party support link
 Google Earth Web Plug-in: Version: 7.1 3rd-Party support link
3rd Party Preference Panes:
 RCDefaultApp
 Flash Player 3rd-Party support link
 Flip4Mac WMV 3rd-Party support link
 Java 3rd-Party support link
 MenuMeters 3rd-Party support link
Old Applications:
 asannotation2: Version: 10.21.26.0 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/924/asannotation2.app
 convertpdf: Version: 1.2 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/1224/convertpdf/convertpdf.app
 Neverwinter Nights 2: Version: 1.23.1765 - SDK 10.5 3rd-Party support link
 Amazon MP3 Downloader: Version: INFO_PLIST_VERSION - SDK 10.4 3rd-Party support link
 TurboTax Deluxe 2011: Version: 2011.r17.007 - SDK 10.4 3rd-Party support link
 Ventrilo: Version: 3.0.13 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/1224
 Cisco WebEx Meeting Center: Version: 1207.04.2732.10 - SDK 10.5 3rd-Party support link
 asannotation2: Version: 8.25.31.0 - SDK 10.5 3rd-Party support link
 atmsupload: Version: 4.14.29.0 - SDK 10.5 3rd-Party support link
 convertpdf: Version: 1.2 - SDK 10.5 3rd-Party support link
Time Machine:
 Skip System Files: NO
 Auto backup: YES
 Volumes being backed up:
 Macintosh HD: Disk size: 930.71 GB Disk used: 184.55 GB
 Destinations:
 JOHN TM [Local] (Last used)
 Total size: 2
 Total number of backups: 51
 Oldest backup: 2014-01-09 05:11:53 +0000
 Last backup: 2014-04-04 08:40:29 +0000
 Size of backup disk: Adequate
 Backup size 2 > (Disk used 184.55 GB X 3)
 Time Machine details may not be accurate.
 All volumes being backed up may not be listed.
Top Processes by CPU:
 2% WindowServer
 1% EtreCheck
 0% SystemUIServer
 0% com.apple.WebKit.Networking
 0% softwareupdated
Top Processes by Memory:
 344 MB Safari
 258 MB mds_stores
 258 MB com.apple.IconServicesAgent
 172 MB softwareupdated
 172 MB soffice
Virtual Memory Information:
 3.05 GB Free RAM
 5.12 GB Active RAM
 2.71 GB Inactive RAM
 1.05 GB Wired RAM
 7.04 GB Page-ins
 15 MB Page-outs

try Mail is not syncing an imap account correctly
(https://discussions.apple.com/message/21904088#21904088) , it just worked for me.

Since installing the latest update, Firefox will not load; it gives me the following error -- XML Parsing Error: not well formed.

since installing the latest update, Firefox first operated with some errors but now will not load at all; it gives me the following error --
XML Parsing Error: not well formed
locations chrome://browser/content/browser.xml
Line Number 1191, column 20:
utton id="back-forward-dropmarker" type="menu" chromedir="&locale.dir;"-------------------
please note that the words "utton ID" are exactly as the error message gives it; and at the end of the message there are exactly 19 hyphens.
I don't know why this faulty code is referencing things to do with "chrome"... the Chrome browser is not installed on this PC or anywhere on our network.
Also, this is not the first problem I had after clicking Firefox's prompt for the latest update. Before Firefox retreated into this error message, it was loading but running with some faults...
1. the bookmark symbol was not appearing on the right hand side of the URL line, so I had always to click on "bookmark this page", after which the bookmark symbol did appear; however I don't know if the bookmarking function worked properly.
2. the back and forward buttons were not highlighted, as if I had not come from a previous page; so once I clicked on a link to a new page I could not go back to where I came from because Fiefox thought I hadn't come from anywhere.
3. there may have been other errors, but I did not find them.
How do I reinstate my Firefox program to work properly please? do I have to download the latest version and reinstal? if so, do I have to remove the old version first? or is there a fix?
Even to write this message I have been forced to use (yuk -- I don't like to say this!!!) Internet Explorer. So please -- I need help urgently.
Thanks,
NOEL

Some how I solved my problem by opening a user account and downloading Firefox 4.0 beta and installing it, I did try it, worked fine, so I did close the user account and did go back to my own account(switched user), the main page that I had problem with Firefox which would not open, I dabble click on Firefox it start working again!! I hope that solves your problem too.
firefox will not open, it gives me this cod and would not turn off, Error on switching in renew: NS_ERROR_UNEXPECTED, Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref] id: none

Error in parsing value for ... Declaration dropped.

Hi,
I'm using Fedora 16. Everything is working perfect and Firefox was working perfect (version 9). But version 9.0.1 creates big problems for my intranet and webpages, including yours. The error console fills up with 100' of error messages like; 'Error in parsing value for '(background, display, moz-opacity, filter...)' . Declation dropped. Some tags (on my intranet) like fontsize are "bigger", it seems like Firefox skips my CSS settings, the same for some CSS page layouts. One page example is that one only dropbox fontsize is displayed correctly, the other 17 are not CSS formatted.
I have done all your posting regarding to solve problems, reading all posting but nothing helps.
Ny own research for the problem
Switch to the web browser Konqueror, everything about layouts and fonts displays properly (other things like '-moz-border-radius' is of course not working.
I also have a windows computer with Firefox 9.0.1. Everything is displayed properly with the same amount of error messages as in FF for Linux! The same goes for Internet Explorer 9 in windows (everything displays properly).
Confusing. Is it a Fedora problem or FF for Linux problem?

I found a solution to the problem. Uninstall Firefox and Firetray. Delete /.Mozilla folder. Reboot. Install Firefox. Now everything is displayed properly.

"Error while parsing SOAP XML payload: no element found" received when invoking Web Service

Running PB 12.1 Build 7000. Using Easysoap. Error ""Error while parsing SOAP XML payload: no element found" received when invoking Web Service". This error does not appear to be coming from the application code. Noticed that there were some erroneous characters showing up within the header portion of the XML ("&Quot;"). Not sure where these are coming from. When I do a find within the PB code for """" it gets located within two objects, whereas they both reference a "temp_xml_letter". Not sure where or what temp_xml_letter resides??? The developer of this is no longer with us and my exposure to WSDL and Web Services is rather limited. Need to get this resolved...please.
This is the result of the search. Notice the extraneous characters ("""):
dar1main.pbl(d_as400_mq_xml)
darlettr.pbl(d_email_xml)
---------- Search: Searching Target darwin for 'temp_xml' (9:52:41 AM)
---------- 2 Matches Found On "temp_xml":
dar1main.pbl(d_as400_mq_xml).d_as400_mq_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> number </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
darlettr.pbl(d_email_xml).d_email_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> imcnumber </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
---------- Done 2 Matches Found On "temp_xml":
---------- Finished Searching Target darwin for 'temp_xml' (9:52:41 AM)

Maybe "extraneous" is an incorrect term. Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the """? How do I find which parser is being utilized and how to control it?
<<<
If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
>>>

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Error in parsing taglib 'NavigationTagLibrary'

Similar Messages

Maybe you are looking for