This method registers handlers for various parser events.
Packet Bundle Container.(Packet Bundle Container.java:177) at wbe.server.
Event Processor.process(Event Processor.java:337) at wbe.server.engine.aspects. Durable Event Persistence Impl.event Receiver Queue Write(Durable Event Persistence Impl.java:75) at wbe.server. Process Message(Receiver Bean Helper.java:205) at ejbs. Event Receiver Message(Event Receiver Bean.java:55) at ejs.container.
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums hi, well, the subject itself is the question.
I searched the IBM site for that file, but i couldn't find it.
Pls tell me the exact location from where the file can be downloaded. regds, Deepika, I'm unable to understand the purpose behind that question. My email Id is [email protected] have mentioned my email id in my profile.
Pls do mail me about the site where I can found the xml4file(IBM XML parser), and also tell me why didn't u reply directly in the forum.. When integrating Web Sphere Adapter for J D Edwards Enterprise One version 7.0 with Web Sphere Business Events version 7.0 in Web Sphere Application Server version 220.127.116.11, an XML parser error is thrown. SAXParse Exception will be thrown by Web Sphere Business Events: sax.SAXParse Exception: XML version "1.1" is not supported, only XML 1.0 is supported. DOMParser.parse(Unknown Source) at wbe.model.packet. Packet Bundle String(Packet Bundle Container.java:770) at wbe.model.packet.To resolve this problem, it is necessary to keep the default XML parser configuration of Web Sphere Application Server. XMLParser Configuration property and ensure that the default XML parser configuration of Web Sphere Application is the following: Serverorg.apache.parser. The file "xerces.properties" is located in the lib subdirectory of the JRE of Web Sphere Application Server. XMLParser Configuration property is defined in the "xerces.properties" file. By providing a false or undefined value as the handler, the existing handler can be unset.