XI XML Parser: tag content with "'", single apostrophe: invalid character

Hi all,
we import XML-documents with the file adapter in a sender channel. everything works well.
But if one of the XML-tag contents contains a single apostrophe ( ' ), then the XML parser stops with an error "An invalid character was found inside an entity reference. ". The message can not be processed. If I test the message content in the mapping -> no error.
When the single apostrophe is dereferenced by an additional single apostrophe the XML-File can be processed.
Question: does anybody know how this can be handled because it is not very nice of SAP XI to send single apostrophes in outgoing messages but cannot handle it in incoming messages from other systems? special adapter settings?
Thank you very much
regards
Hans

check bhavesh reply
Suppress Special Character
also check
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
Implementing a Java Mapping in SAP PI to remove Escape Sequences from a file

Similar Messages

  • How to get 2 xml(Sibling tag) content same time and merge them

    how to get 2 xml(Sibling tag) content same time and merge them and search the result value in indesign file with page number  
    Like
    <Record>
    <A>this is a text</A>
    <B>a-123</B>
    </Records>
    First we need  tag A and B value as  :
    this is a text - a-123 and then get  this text page number form the indesign doc
    plz help

    hi
    var root = app.activeDocument.xmlElements[0];
    var aTag = root.evaluateXPathExpression("//Record/INAAMF");
    var bTag = root.evaluateXPathExpression("//Record/IAFKF");
    here I got  aTag  and bTag  = empty
    may be the reason is as I forgot to menion the proper XML path as
    <Records>
    <Record>
    <A>this is a text</A>
    <B>a-123</B>
    </Record>
    <Record>
    <A>Second text</A>
    <B>a-132</B>
    </Record>
    <Record>
    <A>Thied text</A>
    <B></B>
    </Record>
    <Records>

  • Sax parser returned an exception. Message: Invalid character (Unicode: 0x12

    Hi,
    I'm getting the error 'Sax parser returned an exception. Message: Invalid character (Unicode: 0x12), Entity publicId: , Entity systemId: , Line number: 47, Column number: 75'
    when I try and run a report in BI Answers 10g.
    Apparently it's to do with a Java applet (or piece of Java code anyway) not being sent to an exception so it can't handle it. The problem is that I can't
    run the report to get at some of the views that seem only available at run time. eg. charts.
    Does anyone know how I can see behind the scenes of views without running the report?
    Or does anyone know how to get rid of this error anyway?
    Many thanks,
    - Jenny

    Hi Satya,
    I am facing the same issue. but I am facing this issue with Mozilla Firefox browser only. If I modify same reports in internet explorer I don't get this error.  It seems this issue is with OBIEE 10g version only and Oracle has provided some patches on this in OBIEE 11g .
    You have posted this question long back. If you have got any solution for this then please let me know also.
    Thanks

  • Does Oracle XML Parser support Content Validation

    Hi there,
    Could someone out there give me a hint on whether the Oracle XML Parser has the capability of handling Content Validation? If yes, what's the mechanism behind it?
    From my understanding of the Oracle XML Parser, even with the validating mode turned on, the parser only validates the XML data against the DTD (if any), which involves checking whether or not the attribute names and element tags are legal, whether nested elements belong to where they are, and so on. But I dont see any Content Validation. And my guess is that this feature, namely Content Validation, is simply not supported in the current version of the Oracle XML Parser. Am I right?
    Any suggestion would be greatly appreciated. Thanks.
    ---Denali
    null

    Hi there,
    Could someone out there give me a hint on whether the Oracle XML Parser has the capability of handling Content Validation? If yes, what's the mechanism behind it?
    From my understanding of the Oracle XML Parser, even with the validating mode turned on, the parser only validates the XML data against the DTD (if any), which involves checking whether or not the attribute names and element tags are legal, whether nested elements belong to where they are, and so on. But I dont see any Content Validation. And my guess is that this feature, namely Content Validation, is simply not supported in the current version of the Oracle XML Parser. Am I right?
    Any suggestion would be greatly appreciated. Thanks.
    ---Denali
    null

  • XML Parser and Content-type/encoding problem

    I've write a little and simple XML parser and a simple "trasformer" that recive an XML file and an XSL one and return HTML, here is the code:
    public static String toHTML(Document doc, String xslSource){
            ByteArrayOutputStream testo = new ByteArrayOutputStream();
            try{
                DOMSource source = new DOMSource(doc);
                TransformerFactory tFactory = TransformerFactory.newInstance();
                System.out.println("----> " + xslSource);
                Transformer transformer = tFactory.newTransformer(new StreamSource(xslSource));
                transformer.setOutputProperty(OutputKeys.INDENT, "yes");
                transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
                transformer.setOutputProperty(OutputKeys.METHOD, "html");
             transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
             transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
                transformer.transform(source, new StreamResult(testo));
            }catch(Exception ioe){
                System.out.println("2 XMLTool.toHTML " + new java.util.Date());
                System.out.println(ioe);        
            return testo.toString();
        }the problem is that I would like to put the HTML code its return into a JEditorPane; now I'm trying with this code:
    JEditorPane jep1 = new JEditorPane();
    jep1.setContentType("text/html");
    jep1.setText(v);
    // 'v' is the string returned by the code posted up (the XML/XSL transformer)but I can't see anything in my JEditorPane.
    I think that the problem is this line of code that the transformer add automaticaly ad HTML code:
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">Infact if I try to delete this line from the code I can see what I want but is'n good delete a line of code without understend where is the problem.
    So, can anyone help me?

    good.
    when u set ur output properties to html , transformer
    searches for all entity references and converts accordingly.
    if u r using xalan these files will be used for conversion of
    Character entity references for markup-significant
    output_html.properties
    (this should be in templates package)
    and HTMLEntities.res(should be in serialize package)
    vasanth-ct

  • ClassCastException oracle.xml.parser.v2.XMLElement with correlation receive

    Hi,
    I am trying to run an asynchronous process that makes an invocation to an external WLI process, then gets an asynchronous receive from a second WLI process using correlation callbacks. We have two 10.1.3.3.0 servers, and the process works perfectly on the first server. The second server invokes WLI fine, and goes into a receive. But then when I call back into the BPEL process, I get the following error:
    Receive_1 (faulted)
    [2008/02/08 09:46:37] Waiting for "receive" from "client". Asynchronous callback.
    [2008/02/08 09:46:53] "ClassCastException" has been thrown.less
    oracle.xml.parser.v2.XMLElement
    It's the same process, calling the same external processes, with identical input/output. What does the error on the second server mean?
    Thank you,
    Nicholas

    Hi,
    I'm using BPEL process manager for calling a asynchronous web service,I can invoke the service from BPEL and the service is invoked correctly,but when I view the business process flow my process is stopped at receive state and doesn't pass it.
    Could anybody tell me if any thing should be set to receive a callback from an asynchronous web service to BPEL process?
    Thnx in advance,
    Nasim

  • XML Parsing Base64 Content - Special Characters Umlaut etc

    Hello!
    I am currently parsing an XML file which has it's content encoded in Base64. My application parses the XML file (from a provider) and pass on the content to a GUI where the user can change the value of the nodes and store the same back in a new XML (which is then to be sent back to the provider). The Application uses only "UTF-8" . I am currently using the Base64 class provided at http://iharder.net/base64
    The problem I have is that the special characters like �, � etc, are being depicted as (?) i.e. unreadable. Only when I control the decoding process i.e. String resoolt = new String (result.getBytes(), "UTF-8") do I get the correct content, and the same can be posted on the GUI.
    The application produces an XML file (The application in question is a translation app), which when re-opened in the application for retranslation has the same problem... it is shown with teh special characters with (?).
    After a lot of debugging I found that the XML produced by the application does not need the forcing of content into UTF-8 using the code above, it is read automatically correctly (with all the content correct), but due to the coding I have done... String resoolt = new String (result.getBytes(), "UTF-8") the nodes are decoded with the earlier problem umlauts et al missing.
    Now I could use a test to differntiate between the two cases XML from the provider or the XML which is produced by my own app, and doesn"t work on the Provider and treat them differently, but I don't want this solution since the XML which my app produces is not accepted as input at the providers.
    So my query.. what is the best way to go about it now... I am quite stymied >(
    Thanks!
    Tim

    Amazingly enough some other user has the identical problem to yours and has expressed it in exactly the same words. Has the same name as you too.
    http://forum.java.sun.com/thread.jspa?threadID=606929&tstart=0
    (Cross-posting is frowned on here.)

  • Consolidate XML End Tag on a single line

    By default, it seems JAXB puts the end tag on the second line. For example:
    <w:Element w:prefix="c" w:name="Person" w:isReference="false">
    </w:Element>
    Is there any way to tell the Marshaller to put the end tag on the same line so the output would be:
    <w:Element w:prefix="c" w:name="Person" w:isReference="false"/>

    I use JAXP+Sax to generate XML files. Here a sample example:
    import java.io.*;
    // SAX classes.
    import org.xml.sax.*;
    import org.xml.sax.helpers.*;
    //JAXP 1.1
    import javax.xml.parsers.*;
    import javax.xml.transform.*;
    import javax.xml.transform.stream.*;
    import javax.xml.transform.sax.*;
    // PrintWriter from a Servlet
    PrintWriter out = response.getWriter();
    StreamResult streamResult = new StreamResult(out);
    SAXTransformerFactory tf = (SAXTransformerFactory) SAXTransformerFactory.newInstance();
    // SAX2.0 ContentHandler.
    TransformerHandler hd = tf.newTransformerHandler();
    Transformer serializer = hd.getTransformer();
    serializer.setOutputProperty(OutputKeys.ENCODING,"ISO-8859-1");
    serializer.setOutputProperty(OutputKeys.DOCTYPE_SYSTEM,"users.dtd");
    serializer.setOutputProperty(OutputKeys.INDENT,"false");/////////////////////// Not Indented XML File but has smaller size
    hd.setResult(streamResult);
    hd.startDocument();
    AttributesImpl atts = new AttributesImpl();
    // USERS tag.
    hd.startElement("","","USERS",atts);
    // USER tags.
    String[] id = {"PWD122","MX787","A4Q45"};
    String[] type = {"customer","manager","employee"};
    String[] desc = {"Tim@Home","Jack&Moud","John D'o�"};
    for (int i=0;i<id.length;i++)
      atts.clear();
      atts.addAttribute("","","ID","CDATA",id);
    atts.addAttribute("","","TYPE","CDATA",type[i]);
    hd.startElement("","","USER",atts);
    hd.characters(desc[i].toCharArray(),0,desc[i].length());
    hd.endElement("","","USER");
    hd.endElement("","","USERS");
    hd.endDocument();
    This line: serializer.setOutputProperty(OutputKeys.INDENT,"false");/////////////////////// Not Indented XML File but has smaller size sets the identation of the xml file. See whether there is an equivalent with JAXB
    Hope that Helps

  • Unattend.xml parsing/merging issue with SCVMM 2012 R2

    Hi all
    I have a problem with a new install of SCVMM 2012 R2. I have created templates for 2008 R2, 2012 and 2012 R2. I have an issue with the unattend.xml losing some of its configuration when the 2012 and 2012 R2 templates are built, this issue however doesn't
    occur on a 2008 R2 template build.
    I have generated unattend.xml files for all 3 OS's using System Image Manager in the latest AIK using the original install.wim from each OS media.
    In the unattend.xml file I have specified language settings, and a few other bits but the issue I have is when I configure autologon with local admin and password. I specify a logon count of 1, I also specify a GUIRunOnce command in SCVMM and not the answerfile.
    The problem is the resulting merged unattend.xml has a logon count of 999 and no GUIRunOnce command. I have tried different variations where I specify GUIRunOnce in the xml and not SCVMM, applying the autologon to the Template or Guest OS profile and
    all end with the resulting xml with logon count of 999 and no GUIRunOnce. If I remove the autologon part then GUIRunOnce gets parsed and works correctly.
    As mentioned this only happens with Server 2012 and 2012 R2, 2008 R2 works correctly.
    Any ideas?

    Hi Kevin
    I am struggling with the same thing during bare metal installs of Hyper-V hosts. In my case I have managed to narrow it down to the language settings in the oobe pass. If I include them, parsing of the unattend file halts (without an explicit error anywhere)
    and the host fails to join the domain. Could you try to leave out the language settings in oobe pass and see if it then completes as expected? Would be interesting to see if it actually is the same issue with a slightly different flavour :)
    EDIT: Got a bit further now with the new release of WS2012 R2. All the testing I've done has been with the 05182 build. Stumbled across KB2913316 which stated that a new build (31419) was released december 11th. Allthough the KB does not directly apply to our
    issue I thought I'd give it a go, so I went about building a new vhdx-image. Low and behold - the first test went smoothly applying all the settings in the unattend file! I'm going to continue testing to make sure the successful run wasn't just a fluke.

  • XML Parser on UTF8

    The project I am working with is involves with UTF8 chars (ie. japanese,chinese) stored in XML file. I tried to test and use the sample XML Parser on Weblogic 7 by putting Japanese character on order.xml and ran the OrderParser.jsp then I got weird characters instead of the Japanese word.
    I saved the xml file on utf8 coding and changed the OrderParser.jsp encoding tag=utf8 too.
    If anybody can help, I appreciated much.
    Nick

    Nick,
    What progam and on what plateform are you making the xml file ?
    What is the plateform for the Weblogic ?
    If Unix, have you checked the LOCALE values ?
    Thanks for the reply,
    Nohmenn
    "Nick" <[email protected]> a écrit dans le message de news:
    [email protected]..
    The project I am working with is involves with UTF8 chars (ie.japanese,chinese) stored in XML file. I tried to test and use the sample XML
    Parser on Weblogic 7 by putting Japanese character on order.xml and ran the
    OrderParser.jsp then I got weird characters instead of the Japanese word.
    >
    I saved the xml file on utf8 coding and changed the OrderParser.jspencoding tag=utf8 too.
    >
    If anybody can help, I appreciated much.
    Nick

  • XML publisher : Error oracle.xml.parser.v2.XMLParseException: Expected ';'

    I am trying to output a customer list containing customer number and customer name using 11i ( 11.5.10 CU2) with latest XML publisher patches on.
    How do I debug the following error in OPP log:
    [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    The XML ouput file is generated fine but get the following error in the log file.
    | Starting concurrent program execution...
    +-----------------------------
    Spawned Process 13471
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 1088898 on node O11IDEV at 03-APR-2006 13:57:35.
    Post-processing of request 1088898 failed at 03-APR-2006 13:57:37 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    ------------- 2) PRINT   -------------
    Finished executing request completion options.
    The OPP service log messge is :
    [4/3/06 6:02:53 AM] [main] Starting GSF service with concurrent process id = 72156.
    [4/3/06 6:02:53 AM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
    [4/3/06 6:02:53 AM] [Thread-12] Service thread starting up.
    [4/3/06 6:02:53 AM] [Thread-13] Service thread starting up.
    [4/3/06 1:16:08 PM] [OPPServiceThread0] Post-processing request 1088889.
    [4/3/06 1:16:08 PM] [72156:RT1088889] Executing post-processing actions for request 1088889.
    [4/3/06 1:16:09 PM] [72156:RT1088889] Starting XML Publisher post-processing action.
    [4/3/06 1:16:09 PM] [72156:RT1088889]
    Template code: COCXDOTEST
    Template app: COC
    Language: en
    Territory: US
    Output type: PDF
    [040306_011610131][][EXCEPTION] [DEBUG] ------- Preferences defined PreferenceStore -------
    [040306_011610132][][EXCEPTION] [DEBUG] ------- Environment variables stored in EnvironmentStore -------
    [040306_011610133][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610134][][EXCEPTION] [DEBUG] [USER_ID]:[-1]
    [040306_011610134][][EXCEPTION] [DEBUG] [FND_JDBC_PLSQL_RESET]:[false]
    [040306_011610135][][EXCEPTION] [DEBUG] [NLS_TERRITORY]:[AMERICA]
    [040306_011610135][][EXCEPTION] [DEBUG] [RESP_APPL_ID]:[-1]
    [040306_011610136][][EXCEPTION] [DEBUG] [FND_MAX_JDBC_CONNECTIONS]:[500]
    [040306_011610136][][EXCEPTION] [DEBUG] [NLS_SORT]:[BINARY]
    [040306_011610137][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.LOW]:[-1]
    [040306_011610138][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610138][][EXCEPTION] [DEBUG] [RESP_ID]:[-1]
    [040306_011610139][][EXCEPTION] [DEBUG] [NLS_NUMERIC_CHARACTERS]:[.,]
    [040306_011610139][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_SIZE]:[5]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_LANGUAGE]:[AMERICAN]
    [040306_011610140][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.HIGH]:[-1]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_DATE_LANGUAGE]:[AMERICAN]
    [040306_011610141][][EXCEPTION] [DEBUG] [LOGIN_ID]:[-1]
    [040306_011610141][][EXCEPTION] [DEBUG] [NLS_DATE_FORMAT]:[DD-MON-RR]
    [040306_011610142][][EXCEPTION] [DEBUG] [APPS_JDBC_URL]:[jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS
    =(PROTOCOL=tcp)(HOST=O11IDEV.concentra.com)(PORT=9200)))(CONNECT_DATA=(SID=DEV1)))]
    [040306_011610143][][EXCEPTION] [DEBUG] [SECURITY_GROUP_ID]:[0]
    [040306_011610144][][EXCEPTION] [DEBUG] [NLS_CHARACTERSET]:[US7ASCII]
    [040306_011610144][][EXCEPTION] [DEBUG] [FND_JDBC_CONTEXT_CHECK]:[true]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_INTERVAL]:[300]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_USABLE_CHECK]:[false]
    [040306_011610147][][EXCEPTION] [DEBUG] ------- Properties stored in Java System Properties -------
    [040306_011610148][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610149][][EXCEPTION] [DEBUG] [sun.cpu.isalist]:[pa2.0 pa1.2 pa1.1 pa1.0]
    [040306_011610149][][EXCEPTION] [DEBUG] [java.version]:[1.3.1.09]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.awt.graphicsenv]:[sun.awt.X11GraphicsEnvironment]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610151][][EXCEPTION] [DEBUG] [sun.io.unicode.encoding]:[UnicodeBig]
    [040306_011610151][][EXCEPTION] [DEBUG] [JTFDBCFILE]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610152][][EXCEPTION] [DEBUG] [java.runtime.name]:[Java(TM) 2 Runtime Environment, Standard Edition]
    [040306_011610153][][EXCEPTION] [DEBUG] [user.home]:[u02/app/dev1app]
    [040306_011610153][][EXCEPTION] [DEBUG] [java.specification.version]:[1.3]
    [040306_011610154][][EXCEPTION] [DEBUG] [java.vm.info]:[mixed mode]
    [040306_011610154][][EXCEPTION] [DEBUG] [user.dir]:[u02/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.io.tmpdir]:[var/tmp/]
    [040306_011610155][][EXCEPTION] [DEBUG] [LONG_RUNNING_JVM]:[true]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.ext.dirs]:[opt/java1.3/jre/lib/ext]
    [040306_011610156][][EXCEPTION] [DEBUG] [dbcfile]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610156][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.awt.fonts]:[]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.class.version]:[47.0]
    [040306_011610158][][EXCEPTION] [DEBUG] [OVERRIDE_DBC]:[true]
    [040306_011610158][][EXCEPTION] [DEBUG] [sun.cpu.endian]:[big]
    [040306_011610159][][EXCEPTION] [DEBUG] [java.class.path]:[/opt/java1.3/lib/rt.jar:/opt/java1.3/lib/tools.jar:/opt/java1.3/jre/lib/rt.jar:/opt
    /java1.3/jre/lib/i18n.jar:/oracle/app/dev1app/dev1comn/java/appsborg.zip:/oracle/app/dev1app/dev1ora/8.0.6.9/forms60/java:/oracle/app/dev1app/d
    ev1comn/java]
    [040306_011610160][][EXCEPTION] [DEBUG] [os.name]:[HP-UX]
    [040306_011610160][][EXCEPTION] [DEBUG] [sun.boot.class.path]:[/opt/java1.3/jre/lib/rt.jar:/opt/java1.3/jre/lib/i18n.jar:/opt/java1.3/jre/lib/
    sunrsasign.jar:/opt/java1.3/jre/classes]
    [040306_011610161][][EXCEPTION] [DEBUG] [java.vendor.url.bug]:[http://www.hp.com/go/Java]
    [040306_011610161][][EXCEPTION] [DEBUG] [user.timezone]:[America/Chicago]
    [040306_011610162][][EXCEPTION] [DEBUG] [java.vm.name]:[Java HotSpot(TM) Server VM]
    [040306_011610163][][EXCEPTION] [DEBUG] [CACHEMODE]:[DISTRIBUTED]
    [040306_011610164][][EXCEPTION] [DEBUG] [cpid]:[72156]
    [040306_011610164][][EXCEPTION] [DEBUG] [java.vm.specification.name]:[Java Virtual Machine Specification]
    [040306_011610165][][EXCEPTION] [DEBUG] [java.vm.vendor]:[Hewlett-Packard Company]
    [040306_011610165][][EXCEPTION] [DEBUG] [user.language]:[en]
    [040306_011610166][][EXCEPTION] [DEBUG] [java.library.path]:[/opt/java1.3/bin/../jre/lib/PA_RISC2.0/native_threads:/opt/java1.3/bin/../jre/lib
    /PA_RISC2.0/server:/opt/java1.3/bin/../jre/lib/PA_RISC2.0:/oracle/app/dev1app/dev1ora/iAS_1.0.2/lib:/oracle/app/dev1app/dev1ora/8.0.6.9/network
    /jre11/lib/PA_RISC/native_threads:/oracle/app/dev1app/dev1appl/cz/11.5.0/bin::/oracle/app/dev1app/dev1ora/8.0.6.9/lib:/usr/lib:/usr/lib]
    [040306_011610167][][EXCEPTION] [DEBUG] [path.separator]:[:]
    [040306_011610167][][EXCEPTION] [DEBUG] [java.vm.specification.version]:[1.0]
    [040306_011610168][][EXCEPTION] [DEBUG] [java.awt.printerjob]:[sun.awt.motif.PSPrinterJob]
    [040306_011610168][][EXCEPTION] [DEBUG] [file.separator]:[]
    [040306_011610169][][EXCEPTION] [DEBUG] [java.runtime.version]:[1.3.1.09-030418-12:59]
    [040306_011610170][][EXCEPTION] [DEBUG] [java.vm.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610171][][EXCEPTION] [DEBUG] [java.vendor]:[Hewlett-Packard Co.]
    [040306_011610172][][EXCEPTION] [DEBUG] [file.encoding.pkg]:[sun.io]
    [040306_011610172][][EXCEPTION] [DEBUG] [java.vendor.url]:[http://www.hp.com/go/Java]
    [040306_011610173][][EXCEPTION] [DEBUG] [logfile]:[oracle/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev/FNDOPP72156.txt]
    040306_011610174][][EXCEPTION] [DEBUG] [os.arch]:[PA_RISC2.0]
    [040306_011610174][][EXCEPTION] [DEBUG] [os.version]:[B.11.11]
    [040306_011610174][][EXCEPTION] [DEBUG] [java.home]:[opt/java1.3/jre]
    [040306_011610175][][EXCEPTION] [DEBUG] [java.specification.name]:[Java Platform API Specification]
    [040306_011610175][][EXCEPTION] [DEBUG] [sun.boot.library.path]:[opt/java1.3/jre/lib/PA_RISC2.0]
    [040306_011610176][][EXCEPTION] [DEBUG] [line.separator]:[
    [040306_011610176][][EXCEPTION] [DEBUG] [file.encoding]:[8859_1]
    [040306_011610177][][EXCEPTION] [DEBUG] [user.name]:[oradev]
    [040306_011610177][][EXCEPTION] [DEBUG] [java.vm.version]:[1.3.1 1.3.1.09-_18_apr_2003_14_01 PA2.0]
    [4/3/06 1:16:13 PM] [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
    at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1001)
    at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1677)
    at oracle.xml.parser.v2.XMLReader.getEntity(XMLReader.java:1928)
    at oracle.xml.parser.v2.NonValidatingParser.parseContentEntityRef(NonValidatingParser.java:1575)
    at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1202)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
    at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:172)
    at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:160)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1015)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
    at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
    at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5975)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3555)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3614)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)

    I was able to correct the error. The data contained an '&' sign and that was causing the xml parser to fail with the above error. If the & is replaced by a different character other than & then this error does not occur.
    Ashok

  • XML Publisher Report ends with Warning -- Invalid Character Error in XML

    Hi,
    I have migrated the standard report 'Invoice Print Selected Invoices' from Reports 6i to XML Publisher. It has to print a Euro(€) in the report. It does not even generate the XML File fully. It gives the below error in the XML File. When i remove the special character, it works fine.
    Please let me know the settings to ensure that XML file also accepts the special characters. How do i get the Euro symbol printed in XML File with out giving Invalid Character Error?
    ===========================================================The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again
    later.
    An invalid character was found in text content. Error processing resource 'http://dfw1svdevapp03.ora.rackspace.com:8040/OA_...
    <C_INV_CURRENCY_SYMBOL>
    N class="m">>
    <LINE_UOM />
    <LINE_UNIT_SELLING_PRICE />
    ===========================================================
    The XML File even does not show which character set it uses. The output file starts with:
    ===========================================================
    <?xml version="1.0" ?>
    - <!-- Generated by Oracle Reports version 6.0.8.25.0
    -->
    ===========================================================

    Hi Tim,
    Thanks for your adhoc response.
    I have gone thru the Document 222663.1 and it says that the Developer 6.0.8.23 is required to handle this problem. We are using almost the updated Developer version i.e., Developer 6.0.8.25. So, this should be handled automatically, but it still errors out. Please suggest.
    Thanks,
    Kesava

  • Swapping XML Parser and XSLT to Xalan 2.7.0 - Not Working (OC4J 10.1.3)

    Hi-
    I'm trying to use the latest Xercies/Xalan classes in OC4J 10.1.3 as described in the How-To swap XML Parsers document:
    http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
    What I can see happening is that the oracle.xml shared library is successfully 'turned off', but the xalan libraries are not added. Instead, the default xml classes that are distributed with the JDK become visible. For instance, using a slightly modified version of the index.jsp page from the how-to, I get this result:
    ------ Output from JSP page ----------------
    TransformerFactory Instance: org.apache.xalan.processor.TransformerFactoryImpl
    Transformer Instance: org.apache.xalan.transformer.TransformerIdentityImpl
    Transformer Version: Xalan Java 2.4.1 (!!)
    What I expect is for that last line to say version 2.7.0, which is the version of the xalan.jar included in my shared library (code to add that line to the how-to shown below).
    I suspect what is happening is that the class loader is simply not letting a shared library override a system library - to do that you probably need to place the jar files in system endorsed directory.
    Has anyone gotten this how-to to work - actually replacing the XML parser/transform classes with the latest Xalan classes? Are you sure it is seeing the current version you placed in the shared library?
    Thanks,
    Eric Everman
    ---- My modified getXSLTDetails() method in the index.jsp page of the how-to -------
    <!-- Additional Import -->
    <%@ page import="org.apache.xalan.Version" %>
    public static String getXSLTDetails()
    Transformer transformer=null;
    TransformerFactory transformerfactory = TransformerFactory.newInstance();
         Version ver = null;
         String br = "<" + "br" + ">"; //otherwise the otn forum chocks on the break.
    try
    transformer = transformerfactory.newTransformer();
              ver = (Version) transformer.getClass().forName("org.apache.xalan.Version").newInstance();
              String ret_val =
                   "TransformerFactory Instance: "+transformerfactory.getClass().getName() + br +
                   "Transformer Instance: "+transformer.getClass().getName() + br;
              if (ver != null) {
                   ret_val = ret_val + "Transformer Version: " + ver.getVersion() + br;
              } else {
                   ret_val = ret_val + "Transformer Version not Available" + br;
              return ret_val;
    catch (Exception e)
    e.printStackTrace();
    return e.getMessage();
    }--------------------------------------------------------------------

    Steve - Thanks for responding on this.
    The Xalan SQL extension is built into Xalan. The most painless way to try it out is to run it via JEdit: www.jedit.org
    JEdit a OS Java application with a fairly painless install process (I'm assuming you already have a current JRE installed). Once its installed, you'll need to install the XSLT plugin - in JEdit goto Plugins | Plugin Manager | Install and pick the XSLT plugin. You'll need the Oracle JDBC classes on your classpath - this can be done by copying the oracle_jdbc4.jar into the [JEdit install directory]/jars directory.
    Restart to load that jar and you should be all set.
    I included a sample XSLT page at the bottom of this post that is somewhat of a template transform for the SQL extension - its more complicated then it needs to be, but it does some nice things with the results of the query. Save it as a file and make the appropriate changes to the 'datasource' parameter near the top of the file.
    Then in JEdit, open the file and make sure the XSLT plugin is visible (Plugins | XSLT | XSLT Processor Toggle - or alternately dock it in the window via global prefs). In the XSLT plugin: Allow the current buffer to be used as the source, Add that same file as a stylesheet via the '+' button, and pick a result file at the bottom. Then click the 'Transform XML' button.
    Troubleshooting: I seem to remember having some classpath errors when I tried this on windows, but others have had it work w/o issues. I do remeber that the XSLT plugin had a popup window that gave a pretty good explaintion of the problem, if it occurs. Also, for some reason the XSLT plugin will not create a new file for the output, so its often best to create a file first, then choose it as the output. Of course, you can always run a transformation from the command line or w/in an applicatoin. Full docs on the Xalan SQL extension can be found at: http://xml.apache.org/xalan-j/extensionslib.html#sql
    Here is my sample XSLT transform using the SQL extension:
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
              xmlns:sql="http://xml.apache.org/xalan/sql"
              xmlns:str="http://exslt.org/strings"
              xmlns:xalan="http://xml.apache.org/xalan"
              extension-element-prefixes="sql str xalan">
         <xsl:output indent="yes"/>
         <xsl:param name="driver">oracle.jdbc.OracleDriver</xsl:param>
         <xsl:param name="datasource">jdbc:oracle:thin:jqpublic/jqpublic@server_name:1521:dbname</xsl:param>
         <xsl:param name="jndiDatasource"><!-- jndi source for production use w/in enterprise environment --></xsl:param>
         <xsl:param name="debug">true</xsl:param>
         <xsl:variable name="connection" select="sql:new()"/>
         <xsl:variable name="uppercase" select="'ABCDEFGHIJKLMNOPQRSTUVWXYZ'"/>
         <xsl:variable name="lowercase" select="'abcdefghijklmnopqrstuvwxyz'"/>
         <!--
              The query:  You could pass parameters in to this query to build a where clause, but here is a simple example.
              Also, its nice to wrap the query with a max row number to prevent huge results.
         -->
         <xsl:param name="query">
         select * from (
      SELECT
              'One' FIELD_1,
              'Two' FIELD_2
         FROM DUAL
         ) where rownum < 100
         </xsl:param>
         <!-- Essentially, create a XConnection object -->
         <xsl:variable name="connection" select="sql:new()"/>
         <xsl:template match="/">
        <xsl:choose><!-- Connect using JNDI -->
          <xsl:when test="$jndiDatasource != ''">
            <xsl:if test="not(sql:connect($connection, $jndiDatasource))">
              <xsl:message>Failed to connect to db via jndi connection</xsl:message>
              <xsl:comment>Failed to connect to db via jndi connection</xsl:comment>
              <xsl:if test="$debug = 'true'">
                <xsl:copy-of select="sql:getError($connection)/ext-error"/>
              </xsl:if>
            </xsl:if>
          </xsl:when>
          <xsl:otherwise><!-- Connect using connection string -->
            <xsl:if test="not(sql:connect($connection, $driver, $datasource))">
              <xsl:message>Failed to connect to db via driver/url connection</xsl:message>
              <xsl:comment>Failed to connect to db via driver/url connection</xsl:comment>
              <xsl:if test="$debug = 'true'">
                <xsl:copy-of select="sql:getError($connection)/ext-error"/>
              </xsl:if>
            </xsl:if>
          </xsl:otherwise>
        </xsl:choose>
              <!--
              The results of the query.  The rowset is brought back in 'streaming' mode,
              so its not possible to ask it for the number of rows, or to check for zero
              rows.  There is a switch to disable streaming mode, but this requires all
              rows to be brought into memory.
              -->
              <xsl:variable name="table" select="sql:query($connection, $query)"/>
              <xsl:if test="not($table)">
                   <xsl:message>Error in Query</xsl:message>
                   <xsl:copy-of select="sql:getError($connection)/ext-error"/>
              </xsl:if>
              <page>
                   <!-- Your xalan environment -->
                   <xsl:copy-of select="xalan:checkEnvironment()"/>
                   <!-- Build a bunch of metadata about the rows -->
                   <meta>
                        <cols>
                             <xsl:apply-templates select="$table/sql/metadata/column-header"/>
                        </cols>
                   </meta>
                   <rowset>
                        <!--
                             With streaming results, you must use the apply-temmplates contruct,
                             not for-each, since for-each seems to attempt to count the rows, which
                             returns zero.
                        -->
                        <xsl:apply-templates select="$table/sql/row-set"/>
                   </rowset>
              </page>
              <xsl:value-of select="sql:close($connection)"/><!-- Always close -->
         </xsl:template>
         <xsl:template match="row">
              <row>
                   <xsl:apply-templates select="col"/>
              </row>
         </xsl:template>
         <xsl:template match="column-header">
              <col>
                   <xsl:attribute name="type">
                        <xsl:value-of select="@column-typename"/>
                   </xsl:attribute>
                   <xsl:attribute name="display-name">
                        <xsl:call-template name="create-display-name"/>
                   </xsl:attribute>
                   <xsl:value-of select="@column-name"/>
              </col>
         </xsl:template>
         <!-- Convert column names to proper caps: MY_FIELD becomes My Field -->
         <xsl:template name="create-display-name">
              <xsl:variable name="col-name">
                   <xsl:for-each select="str:tokenize(@column-name, '_')">
                        <xsl:value-of
                             select="concat(translate(substring(., 1, 1), $lowercase, $uppercase), translate(substring(.,2), $uppercase, $lowercase), ' ')"/>
                   </xsl:for-each>
              </xsl:variable>
              <xsl:value-of select="substring($col-name, 1, string-length($col-name) - 1)"/>
         </xsl:template>
         <!-- Creates data columns named 'col' with a column-name attribute -->
         <xsl:template match="col">
              <col>
                   <xsl:attribute name="column-name"><xsl:value-of select="@column-name"/></xsl:attribute>
                   <xsl:value-of select="."/>
              </col>
         </xsl:template>
    </xsl:stylesheet>

  • Fast XML parser for java 1.1.8

    Hello!
    I have to following problem. I am using at the moment kxml2 to parse XML data and it could be faster.
    The data is parsed in a application running on different digiboxes, which use java version 1.1.8(IIRC).
    Anybody here who knows of a smallish but very fast XML parser which runs with java 1.1.8?
    O.

    Found this while browsing this forum: http://www.japisoft.com/fastparser/
    I'll try it when I get to work tomorrow. It says it is 1.1 compliant so It could be the
    thing I'm looking for.
    O.

  • ADM-75024 [oracle.xml.parser] [904 vs. 906]

    Hi!,
    After running in the following exception in a 904 appserv (oracle.xml.parser.v2.XMLDOMException: Implementation does not support the object requested) we decided to use the 906 parser frrom the xdk. But now we are having a big problem: now there will no application will have been deployed/undeployed/redeployed interupted by an ADM-75024 exception. When restoring the original 904 parser it does work. but this isn't usuable!
    We tried following parameters, but it doesn't work:
    JVM parameters:
    -server -Djava.security.policy=/opt/oracle/oracleas/j2ee/app/config/java2.policy
    -Djava.awt.headless=false -Xms256m -Xmx1024m
    -Dhttp.proxySet=true -Dhttp.proxyHost=proxy -Dhttp.proxyPort=80
    -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
    -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
    -Djavax.xml.parsers.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
    -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
    but these parameters doesnt' have any influence because libraries will be loaded as follows:
    1. system
    2. container
    3. application
    We read many documents --> There exist following BUG numbers: 3565902, 4353119, 3654742, 3136577, 2591746, 3557552
    3565902 is nearest; The effect is always the same but different conditions. The suggestions are different. But one thing can be seen: that exception only occurs within 904 oracle xml parser!! With 3565902 the 906 switch solution is preferred.
    As seen under http://www.oracle.com/technology/tech/java/oc4j/904/collateral/OC4J-FAQ-904.html (25)
    the switch is no supported. Under http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-swapxmlparser/doc/readme.html the switching capabilites will be brougth with 10.1.3. But i can't use 10.1.3...however I need a solution for 904.
    1st: Is there any workaround for the problem mentioned above (oracle.xml.parser.v2.XMLDOMException)
    2nd: why the error while deployment/undeployment/redeployment occurs?
    thanks, merci, grazie ..en avance
    Andreas
    ps: i can provide log files if needed.

Maybe you are looking for

  • Is this possible without PBR - Routing from Specific Host to Any

    Hi, I have an issue where I don't currently have PBR options on my core switch. Now I know I can amend the SDM template and enable the routing one then reboot (I'm also runing ipservices). At the moment though this is not an option. I have a host - 1

  • Broken disk permissions

    broken disk permissions what causes them. thanks

  • Inability to print to networked Samsung M2825DW Printer from IE 11

    I recently installed a Samsung M2825 printer on my network. Now I'm unable to print to that printer from IE 11.  I get the following error message: "There was an internal error and Internet explorer is unable to print this document." I can print to m

  • App Update Wont Work IPhone 3GS

    My email is signed in to the app store on my iphone 3GS I can download apps and my email shows up asking for my password like always I put it in and it downloads but when I try to update apps my brothers email address pops up and asks for the passwor

  • POA SP3 and Data Synchroniser 1.2.3 Build 882

    Hi All, Last week we updated to Groupwise 8 SP3, running on Netware 6.5 with no issues. Since that update we have had major issues with Data Synchroniser 1.2.3 Build 882. Every 2 to 5 hours all the IOS devices ( we only use IOS devices) will throw up