XML UTFDataFormat Exception

Hi,
I am trying to create an XML Dataset from a PHP file that has
been exported as XML. I've had no trouble with this before. But
now, when I click on "DISPLAY SCHEMA", I am getting an
UTFDataFormat exception. The one difference is that this recordset
consists of joined tables. But I think I've done this before so I
can't figure out what is different. When I view the PHP page, I see
my xml data and it looks alright.
Is there something that I am missing?

DaggerLily wrote:
> I discovered the problem...which of course raises
another question. I had names
> in the data that had non-english letters. One had a ?
and the other had an ?.
> As soon as I had changed those, it worked.
Unfortunately, I can't see which characters you're referring
to, because
they're converted to question marks by the NNTP server.
> So that brings up the question, can I change it in some
way to be able to have
> these characters?
Since you're using the XML Export extension, it should work
if you
select UTF-8 as the encoding. However, your database encoding
needs to
be UTF-8 as well.
One alternative is to pass your data to the PHP
htmlentities() function
before storing it in the database.
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Similar Messages

  • XML dataset exception

    Hi,
    I've created a PHP page with a recordset consisting of joined tables. I've then exported it as XML. When I am on my main page and attempting to create an XML dataset, as I have done successfully before, when I click on "Get Schema" I get the exception "Type:UTFDataFormat Exception". I don't know why. I haven't had this before.
    I have viewed my original PHP page with the recordset and I see all the information there, so I don't think there should be a problem.
    Am I missing something?

    You know, I've got this problem again. I think the last time, I took out some special text characters - like the french e with an accent and the swedish o with a line through it, and then it worked. I hate to do that since it is an international site. And now I'm having this exception error again and I'm not sure why.
    Any ideas of what I should look for? This time it is not an XML file created from a joined recordset - it's a simply recordset.
    Very frustrating.

  • XML Parser Exception in Install of AIA 11.1.1.5 on SOA 11.1.1.5

    I am attempting to install AIA Foundation Pack on a SOA domain and continually encounter an XML parsing exception error as the installer is attempting to install WSM security policies. Here are the key details:
    AIA version = 11.1.1.5
    SOA Suite = 11.1.1.5
    WebLogic = 10.3.5
    Operating System = Fedora14 (a home lab machine but I don't think this is an OS issue)
    The error is encountered about 17 minutes into the lengthy process. Just before the error appears in the installation log, the following message appears indicating roughly what step is being performed:
    [zip] Building zip: /opt/oraclemw/aia11115/aia_instances/dev1/tmp/aia_security_policies.zip
    The core error messages are:
    [exec] SEVERE: WSM-01605 XML parser exception
    [exec] oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
    [exec] at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
    The python modules being executed by the WLST scripting tool at the time of the failure are:
    [exec] Problem invoking WLST - Traceback (innermost last):
    [exec] File "/opt/oraclemw/aia11115/Infrastructure/Install/AID/lib/py/importpolicy.py", line 29, in ?
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/wsmManage.py", line 719, in importRepository
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/lib/ora_util.py", line 51, in raiseScriptingException
    [exec] OracleScriptingException: None
    Finally, the outer XML files being used as input for the deployer that seems to be running at the time are:
    /opt/oraclemw/aia11115/Infrastructure/Install/AID/AIAExecuteDriver.xml
    with references to lines 221 and 64.
    The problem occurs whether I try to use Java JDK 16.0.20 or JRockit R28.2.0 as the JRE when running the AIA installer. (The WebLogic domain is configured to use JRockit).
    Any suggestions? Is there a library conflict being picked up between different releases of XercesImpl? I would hope there isn't actually a bad XML file in the AIA artifacts or WSM (Web Service Management) policies being deployed.

    HI
    How this issue was resolved? Please explain in detail. I am facing the same issue.
    Regards
    Arun

  • XML Loader Exception

    I get the following exception whenever I run the XMLLoader class.
    Error loading stylesheet file:/C:/Documents and Settings/mfortner/jbproject/MedlineXMLLoader/medline.xslt
    oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'INSERT'.
    at oracle.xml.parser.v2.XSLStylesheet.error(XSLStylesheet.java:1403)
    at oracle.xml.parser.v2.XSLStylesheet.processResult(XSLStylesheet.java:615)
    at oracle.xml.parser.v2.XSLStylesheet.initStylesheet(XSLStylesheet.java:421)
    at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:217)
    at XMLLoader.main(XMLLoader.java:21)
    00001: Inserted.
    Processed 1Documents
    I've tried moving the xsl:version attribute, putting it in it's own <?xsl-stylesheet ?> tag didn't work either. I've tried removing it, same problem. I've tried switching xmlparserv2.jar files (there are two files with different file sizes that come in the xdk) -- that didn't work either.
    I'm running the XMLLoader with the following parameters:
    -file sampmed2.xml -connName medline -transform medline.xslt -docTag MedlineCitationSet
    Any suggestions????
    The XSLT I'm using looks like this.
    <?xml version="1.0"?>
    <INSERT xsl:version="1.0" xmlns:xsl="http://www.w3.org/XSL/Transform">
    <!-- Process Medline Records -->
    <ROWSET table="medline_records">
    <xsl:for-each select="MedlineCitation">
    <ROW>
    <MedlineID><xsl:value-of select="MedlineID"/></MedlineID>
    <PMID><xsl:value-of select="PMID"/></PMID>
    <DateCreated><xsl:apply-templates select="DateCreated" mode="processDateCreated"/></DateCreated>
    <DateCompleted><xsl:apply-templates select="DateCompleted" mode="processDateCompleted"/></DateCompleted>
    <DateRevised><xsl:apply-templates select="DateRevised" mode="processDateRevised"/></DateRevised>
    <Journal><xsl:apply-templates select="Journal" mode="processJournal"/></Journal>
    <ArticleTitle><xsl:value-of select="ArticleTitle"/></ArticleTitle>
    <AuthorList><xsl:value-of select="AuthorList"/></AuthorList>
    <Country><xsl:value-of select="MedlineJournalInfo"/></Country>
    <MedlineTA><xsl:value-of select="MedlineJournalInfo/MedlineTA"/></MedlineTA>
    <MedlineCode><xsl:value-of select="MedlineJournalInfo/MedlineCode"/></MedlineCode>
    <NlmUniqueID><xsl:value-of select="MedlineJournalInfo/NlmUniqueID"/></NlmUniqueID>
    <CitationSubset><xsl:value-of select="CitationSubset"/></CitationSubset>
    </ROW>
    </xsl:for-each>
    </ROWSET>
    <!-- Process Date Elements (DateCreated, DateCompleted, and DateRevised -->
    <xsl:template select="DateCreated" mode="processDateCreated">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <xsl:template select="DateCompleted" mode="processDateCompleted">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <xsl:template select="DateRevised" mode="processDateRevised">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <!-- Process Journal Elements -->
    <xsl:template select="JOURNAL" mode="processJournal">
    ISSN<xsl:value-of select="ISSN"/> VOLUME<xsl:value-of select="Volume"/> PAGES<xsl:value-of select=""/>
    </xsl:template>
    <!-- Process Medline Abstract Records -->
    <ROWSET table="medline_abstracts">
    <xsl:for-each select="MedlineCitation">
    <MedlineID><xsl:value-of select="MedlineID"/></MedlineID>
    <Abstract><xsl:value-of select="AbstractText"/></Abstract>
    </xsl:for-each>
    </ROWSET>
    </INSERT>
    And the XML I'm loading looks like this:
    <MedlineCitationSet>
    <MedlineCitation>
    <MedlineID>96264942</MedlineID>
    <PMID>8655018</PMID>
    <DateCreated>
    <Year>1996</Year>
    <Month>07</Month>
    <Day>30</Day>
    </DateCreated>
    <DateCompleted>
    <Year>1996</Year>
    <Month>07</Month>
    <Day>30</Day>
    </DateCompleted>
    <DateRevised>
    <Year>2000</Year>
    <Month>12</Month>
    <Day>18</Day>
    </DateRevised>
    <Article>
    <Journal>
    <ISSN>0017-0011</ISSN>
    <JournalIssue>
    <Volume>67</Volume>
    <Issue>1</Issue>
    <PubDate>
    <Year>1996</Year>
    <Month>Jan</Month>
    </PubDate>
    </JournalIssue>
    </Journal>
    <ArticleTitle>[Effect of fetal and neonatal growth on the occurrence of some diseases in adults]</ArticleTitle>
    <Pagination>
    <MedlinePgn>34-6</MedlinePgn>
    </Pagination>
    <Abstract>
    <AbstractText>The findings of many authors show that reduced fetal growth is followed by increased mortality from cardiovascular disease in adult life. They are further evidence that cardiovascular disease originates, among other risk factors, through programming of the bodies structure and metabolism during fetal and early post-natal life. Wrong maternal nutrition may have an important influence on programming.</AbstractText>
    </Abstract>
    <Affiliation>Katedry i ZakEadu Chemii i Analizy LekC3w, AM w Katowicach.</Affiliation>
    <AuthorList>
    <Author>
    <LastName>Jendryczko</LastName>
    <FirstName>A</FirstName>
    <Initials>A</Initials>
    </Author>
    <Author>
    <LastName>Poreba</LastName>
    <FirstName>R</FirstName>
    <Initials>R</Initials>
    </Author>
    </AuthorList>
    <Language>pol</Language>
    <PublicationTypeList>
    <PublicationType>Journal Article</PublicationType>
    <PublicationType>Retracted Publication</PublicationType>
    <PublicationType>Review</PublicationType>
    <PublicationType>Review, Tutorial</PublicationType>
    </PublicationTypeList>
    <VernacularTitle>WpEyw przebiegu rozwoju pEodu i noworodka na ujawnienie sie niektC3rych chorC3b okresu dorosEego.</VernacularTitle>
    </Article>
    <MedlineJournalInfo>
    <Country>POLAND</Country>
    <MedlineTA>Ginekol Pol</MedlineTA>
    <MedlineCode>FR3</MedlineCode>
    <NlmUniqueID>0374641</NlmUniqueID>
    </MedlineJournalInfo>
    <CitationSubset>IM</CitationSubset>
    <CommentsCorrections>
    <CommentIn>
    <RefSource>Ginekol Pol. 1998 Jul;69(7):561</RefSource>
    </CommentIn>
    <RetractionIn>
    <RefSource>Ginekol Pol 1998 Jul;69(7):559-60</RefSource>
    </RetractionIn>
    </CommentsCorrections>
    <MeshHeadingList>
    <MeshHeading>
    <Descriptor>Adult</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Cardiovascular Diseases</Descriptor>
    <SubHeading>etiology</SubHeading>
    <SubHeading MajorTopicYN="Y">mortality</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Child Development</Descriptor>
    <SubHeading MajorTopicYN="Y">physiology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>English Abstract</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Fetal Development</Descriptor>
    <SubHeading MajorTopicYN="Y">physiology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Fetal Growth Retardation</Descriptor>
    <SubHeading>complications</SubHeading>
    <SubHeading MajorTopicYN="Y">physiopathology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Human</Descri ptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Infant, Newborn</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Nutrition</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Risk Factors</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Survival Rate</Descriptor>
    </MeshHeading>
    </MeshHeadingList>
    <NumberOfReferences>11</NumberOfReferences>
    </MedlineCitation>
    <MedlineCitation>...</MedlineCitation>
    </MedlineCitationSet>

    You have a typo in your namespace declaration:
    xmlns:xsl="http://www.w3.org/XSL/Transform"
    should be
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

  • XSLT Transform in XML Signature: Exception

    Hello,
    I have following problem with an XSLT tranform in my XML signature. Here is the code I use to add XSLT to signature:
    main() {
    DOMStructure stylesheet = new DOMStructure( getStylesheet() );
    XSLTTransformParameterSpec spec = new XSLTTransformParameterSpec( stylesheet );
    transforms.add( fac.newTransform( Transform.XSLT, spec ) );
    private Element getStylesheet() throws Exception {
         String stylesheet = //"<?xml version=\"1.0\"?>" +
                        "<xslt:stylesheet version=\"1.0\" xmlns:xslt=\"http://www.w3.org/1999/XSL/Transform\">\n" +
                        " <xsl:include href=\"http://extern XSLT\" />\n" +
                        " <xslt:template match=\"/\">" +
                        " <xsl:apply-imports />" +
                        " </xslt:template>" +
                        "</xslt:stylesheet>\n";
         DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
         //dbf.setValidating( true );
         return dbf.newDocumentBuilder().parse( new ByteArrayInputStream( stylesheet.getBytes() ) ).getDocumentElement();
    I get following exception:
    javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.dsig.TransformException: com.sun.org.apache.xml.internal.security.transforms.TransformationException: Cannot find xslt:stylesheet in Transform
    Original Exception was com.sun.org.apache.xml.internal.security.transforms.TransformationException: Cannot find xslt:stylesheet in Transform
         at org.jcp.xml.dsig.internal.dom.DOMReference.transform(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMReference.digest(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.digestReference(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.sign(Unknown Source)
    In google I cannot find any details what can be wrong.
    Any suggestions?
    Thanks in advance,
    errno

    Thanks for your response. Sorry - I tried both versions with xslt and xsl - doesn't worked -> the error in my post is actually caused through the multiple changes of this part of code. Here once again:
    private Element getStylesheet() throws Exception {
              String stylesheet = //"<?xml version=\"1.0\"?>" +
                                       "<xslt:stylesheet version=\"1.0\" xmlns:xslt=\"http://www.w3.org/1999/XSL/Transform\">\n" +
                                       " <xslt:include href=\"external XSLTl\" />\n" +
                                       " <xslt:template match=\"/\">" +
                                       " <xslt:apply-imports />" +
                                       " </xslt:template>" +
                                       "</xslt:stylesheet>\n";
              DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
              //dbf.setValidating( true );
              return dbf.newDocumentBuilder().parse( new ByteArrayInputStream( stylesheet.getBytes() ) ).getDocumentElement();
    Thanks,
    errno

  • XML Parser Exception on Punch Out Setup Request

    I am on the supplier side of the procurement process. Recently I was tasked with bringing on a new buying group, but we have encountered a strange issue. The buyer set up my company in their ERP system, however they are getting an error when trying to punch out to my website...which is listed below.
    Error Code: 400 Invalid XML Format In Login Response Document Unable to parse the Login Response XML.
    XMLParserException
    oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'meta'.
    at oracle.xml.parser.v2.XMLError.flushErrors1
    After some investigation, I am confident the problem resides in the buyers BrowserFormPost URL. The problem seems to be that instead of using "&amp;" for ampersand between the URL variables, it is passing in the & symbol (& is a protected character in XML), which is causing the Oracle XML parser to throw this exception. As a result, the set up request is never getting to me.
    The buyer has opened a couple of tickets now with Oracle support, but both times the ticket has been closed and the buyer has been instructed to contact the supplier (me). I don't know enough about the buyer side Oracle system to instruct them on how to fix this issue. Any help would be greatly appreciated.

    Hi Rakesh,
    You need to have an S-User ID to access SAP Notes. For your convenience, I am pasting the content of SAP Note 954035.
    Process, block and CO could not be created in GP
    Symptom
    After upgrade of SAP-EU component to version 7.0 SP8 in Guided Procedures process, block and callable object could not be created. On design time screen   appears error message:
    com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
    During attempt to start process through the Runtime screen you will get an error message:
    Cannot load callable object container:
    Failed to get Related Model Object for the object
    com.sap.caf.eu.gp.ui.actions.decpage.
    CDecisionPageInterfaceViewdecisionPageUsage1,relation View
    In SP9, the following message could be found:
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
    Proceed as stated for SP8.
    Other terms
    This is WebDynpro problem caused by an inconsistency of versions.
    Solution
          1. Redeploy the SCA SAP-EU (if redeployment does not help undeploy and deploy again) components:
              o caf/eu/gp/ui/dt/comp/cons,
              o caf/eu/gp/ui/dt/comp and
              o caf/eu/gp/ui/actions  from software component SAP-EU
    or
          2. Apply the SP8 patch 1 if you upgrade to SP8. Both components mentioned below will be updated:
              o caf/eu/gp/ui/dt/comp/cons
              o caf/eu/gp/ui/dt/comp
    See if it solves your problem.
    Bye
    Ankur

  • Xml parsing exception

    Hi,
    I am having xml content as a string like below
    <?xml version="1.0" encoding="UTF-8"?>
    <TransactionResponse>
    <InterchangeControlHeader>
    <AuthorInfoQualifier>00</AuthorInfoQualifier>
    <AuthorInformation> </AuthorInformation>
    </InterchangeControlHeader>
    </TransactionResponse>
    I am trying to parse this xml using below code
    factory.setValidating(false);
    factory.setNamespaceAware(true);
    DocumentBuilder builder = factory.newDocumentBuilder();
    StringReader XMLStringReader = new StringReader(xmlString);
    InputSource XMLInputSource = new InputSource(XMLStringReader);
    document = builder.parse(XMLInputSource);
    I am using
    javax.xml.parsers.DocumentBuilderFactory and DocumentBuilder for parsing but i am getting exception
    "The markup in the document preceding the root element must be well-formed"
    any idea what is missing?
    Thanks

    I am using websphere4.0.6,in standalone appln it works fine.

  • XML parser Exception

              Hi
              I try to deploy a servlet that serve as a MapPoint web services client. So the
              servlet receive a post with latitude and longitude then it try it to retrieve
              a Map showing the location from MapPoint through web services. I am able to deploy
              the servlet, but it throws the following exception when it receives a request.
              java.lang.RuntimeException: ; nested exception is:
                   org.xml.sax.SAXParseException: The root element is required in a well-formed
              document.
                   at com.spatialpoint.mappoint.storelocator.StoreLocator.getAddressMatches(StoreLocator.java:266)
                   at jsp_servlet.__locate._jspService(__locate.java:181)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
                   at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
                   at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
              Any help will be very much appreciated. Thanks
              

    If you're using the XMLTYPE constructor to insert your XML into the DB you can avoid the well-formed validation declaring that the xml is well formed:
    SQL> insert into MYXMLTABLE values (
      2  XMLTYPE('
      3  <ROOT a="1" a="3"/>
      4  ',null,0,1));
    1 row created.Oracle inserts the xml in the table but, obvoiusly, you'll never be able to use it as an XML file:
    SQL> select object_value
      2  from MYXMLTABLE ;
    OBJECT_VALUE
    <ROOT a="1" a="3"/>
    SQL> select extract(object_value,'/*')
      2  from MYXMLTABLE ;
    ERROR:
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00224: multiple occurrences of attribute "a" found
    Error at line 8Max
    [My Italian Oracle blog|http://oracleitalia.wordpress.com/2010/01/31/le-direttive-di-compilazione-pragma/]

  • XML transform exception

    Hi
    I am trying to transform a shopping cart to display from an XSL.
    But I get the following exception
    javax.xml.transform.TransformerException: Content is not allowed in prolog.
    Transformer transformer = tFactory.newTransformer(new StreamSource(xslPath));
                             transformer.transform(new StreamSource(new StringReader(cart.getItemsAsXml().trim())), new streamResult(html));
                             out.println(html);
    What does this indicate ?
    Thx
    aRN

    I think that you are missing
    <?xml version="1.0"?>
    cart.getItemsAsXml()
    you are posting very little information for answering

  • XML Definition Exception not working

    I want to display ON and OFF a footer in oracle report based on a database field. My code is as follows but when I run the report it says that
    ErrorAttribute 'hide' used but not declared. Any suggestions? Appreciate your help in advance..
    <?xml version="1.0"?>
    <report name="corr" DTDVersion="1.0">
    <layout>
    <section name="margin">
    <field name="F_4" source="CF_footer">
    <exception textColor="red" hide="no">
    <condition source="eligbility_code" operator="eq" operand1="A"/>
    </exception>
    <exception textColor="blue" hide="yes">
    <condition source="eligbility_code" operator="eq" operand1="B"/>
    </exception>
    </field>
    </section>
    </layout>
    </report>

    When will be the next release. I have a lot of issues that I'm not sure how to solve. I've been trying to get unique, key, and keyref to work (I'm using the Dom parser version 2.0.2.9.1 Production) with just the simple example ORACLE downloads called report.xsd and it doesn't work. I've also cut and pasted some pretty basic code off the w3c site where it gives the whole standard for schemas and I can't use the extension functionality. Could your oracle team please send me some example code of how to use this stuff. It very well may be I'm just an idiot who can't figure it out. I would really appreciate any help.
    null

  • XML Parsing exception: org.w3c.dom.ls.LSException

    Hi All,
    <p>We have a WSM(Webservice Management Application) product which will generate a 'Proxy WSDL URL' for a 'Real WSDL URL' and it does security/auditing/logging/routing and other stuffs at runtime while getting a webservice request (on Proxy WSDL) and route it to the Functional(Real WSDL URL - Application server where the actual webservice is deployed) endpoint.
    On receiving response from the functional endpoint, it again comes back to WSM which has to just give the response back to the user unless and until some special policies are attached (like schema validation policy - it will validate the response body based on the schema XSD) </p>
    <p/>
    <p>Here, while reading the response (from functional/application endpoint) over the wire and at the time of creating the actual SoapResponse (XmlResponse) for the end user
    xercesImpl.jar is used to parse the data -lsParser.parse(lsInput); which is throwing the exception <b>"org.w3c.dom.ls.LSException: An invalid XML character (Unicode: 0x16) was found in the element content of the document" </b>when it sees not properly formatted XML at any cause (having incompatible data/special character).</p>
    <p/>
    <p><b>As the exception does not even give enough information like where the XML is corrupt/having incompatible data/special character, we cant have a control to do anything from our application/product side ,as it is third party jar xercesImpl.jar. It would be really very helpful if we
    > either get a option/boolean to turn off the validation logic which is done internally in xercesImpl.jar at the time of parsing 'lsParser.parse(lsInput);'
    > or get additional information in the exception (original cause - like the incompatible/special character (or) a full corrupted response in the exception itself) with which we can get a clue to resolve the issue.</b></p>
    <p/>
    Thanks in Advance
    Priya

    I did a search on Sun site, nothing came back.
    It is on http://xml.apache.org/xerces2-j though.
    You might need to go there and download it. or make sure your
    classpath includes the right jar file.

  • XML parser exception: No documentation !

    Hi,
    I'm getting an exception when looking for
    an <xsl:apply-templates> tag in an XSL file
    thats loaded via the DOMParser.
    Do I need to do anything special to declare
    the XSL Namespace?
    Also, the Parser API docs don't seem to have
    this Exception listed!!!
    Does anyone know more regarding this?
    TIA,
    Vijay
    oracle.xml.parser.v2.XPathException: Namespace prefix 'xsl' used but not declared.
    at oracle.xml.parser.v2.XSLParseString.nextToken(XSLParseString.java:406)
    at oracle.xml.parser.v2.PathExpr.<init>(XSLNodeSetExpr.java:313)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:147)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:131)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:124)
    at oracle.xml.parser.v2.UnaryExpr.parse(XSLExpr.java:357)
    at oracle.xml.parser.v2.MultiplicativeExpr.parse(XSLExpr.java:295)
    at oracle.xml.parser.v2.AdditiveExpr.parse(XSLExpr.java:243)
    at oracle.xml.parser.v2.RelExpr.parse(XSLExpr.java:210)
    at oracle.xml.parser.v2.EqualExpr.parse(XSLExpr.java:160)
    at oracle.xml.parser.v2.AndExpr.parse(XSLExpr.java:110)
    at oracle.xml.parser.v2.XSLExpr.parse(XSLExpr.java:59)
    at oracle.xml.parser.v2.FilterExpr.getPrimaryExpr(XSLNodeSetExpr.java:1444)
    at oracle.xml.parser.v2.FilterExpr.<init>(XSLNodeSetExpr.java:1128)
    at oracle.xml.parser.v2.PathExpr.<init>(XSLNodeSetExpr.java:275)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:147)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:131)
    at oracle.xml.parser.v2.XSLExprBase.createNodeSetExpr(XSLExprBase.java:123)
    at oracle.xml.parser.v2.XMLNode.selectNodes(XMLNode.java:763)
    at oracle.xml.parser.v2.XMLNode.selectSingleNode(XMLNode.java:861)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.createStylesheet(FxRatesPortletContentProvider.java:302)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.getStylesheet(FxRatesPortletContentProvider.java:341)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.getContent(FxRatesPortletContentProvider.java:125)
    at portlet.BasePortlet.doPost(BasePortlet.java:100)
    at portlet.BasePortlet.doGet(BasePortlet.java:137)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunNamedDispatcher.include(JRunNamedDispatcher.java:42)
    at allaire.taglib.ServletTag.doEndTag(ServletTag.java:84)
    at jrun__html__fxrates__tagtest2ejsp19._jspService(jrun__html__fxrates__tagtest2ejsp19.java:53)
    at allaire.jrun.jsp.HttpJSPServlet.service(HttpJSPServlet.java:40)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunNamedDispatcher.forward(JRunNamedDispatcher.java:34)
    at allaire.jrun.jsp.JSPServlet.service(JSPServlet.java:175)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:88)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1131)
    at allaire.jrun.servlet.JvmContext.dispatch(JvmContext.java:330)
    at allaire.jrun.jrpp.ProxyEndpoint.run(ProxyEndpoint.java:367)
    at allaire.jrun.ThreadPool.run(ThreadPool.java:272)
    at allaire.jrun.WorkerThread.run(WorkerThread.java:75)
    null

    Hi
    below is the statement which is looking
    for the "xsl:app-templates" element under
    node1, it need an instance of NSResolver.
    XMLElement node1Child2 = (XMLElement) node1.selectSingleNode ("//xsl:apply-templates", resolver );
    // Name Space Resolver
    private class MyNSResolver implements NSResolver {
    * returns the Namespace definition int scope for a given namespace prefix
    public String resolveNamespacePrefix( String prefix ) {
    if ( prefix.equals("xsl")) {
    return "http://www.w3.org/1999/XSL/Transform";
    } else return null;
    } // private class MyNSResolver
    null

  • XML Provider Exception

    Hi,
    I�m trying to develop a new XMLProvider a after compiling it and conf. the provider and channel in the portal, it shows ERROR: Content is not available.
    I�m working with portal 6.2 and AppServ 7.
    The debug is the following:
    02/05/2004 04:08:43:623 PM ART: Thread[Thread-307,5,main]
    ERROR: ProviderCaller.run(): exception thrown from MGCustomXML
    java.util.MissingResourceException: Can't find bundle for base name CustomXMLProvider, locale en_US
         at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804)
         at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:694)
         at java.util.ResourceBundle.getBundle(ResourceBundle.java:661)
         at com.sun.portal.providers.ProviderAdapter.getResourceBundle(ProviderAdapter.java:734)
         at com.sun.portal.providers.xml.XMLProvider.getContent(Unknown Source)
         at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusableProviderCaller.java:158)
    I�ll thank any advice, Pablo

    Refer http://forum.java.sun.com/thread.jspa?tstart=30&forumID=34&threadID=542044&trange=15

  • XML Transformation exception ??

    I customized a XMLProvider to get feed from a content provider on the fly. During transformation I get this exception:
    04/15/2003 03:18:15:896 PM EDT: Thread[Thread-25,5,main]
    ERROR: XMLProvider.doTransform():Error in transforming xml.
    ; Line#: 2; Column#: -1
    javax.xml.transform.TransformerException: Next character must be ";" terminating
    reference to entity "ID".
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
    l.java:660)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
    l.java:1118)
    at com.sun.portal.providers.xml.XMLProvider.doTransform(XMLProvider.java
    :216)
    at com.sun.portal.providers.xml.XMLProvider.getContent(XMLProvider.java:
    280)
    at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusablePro
    viderCaller.java:145)
    04/15/2003 03:18:15:902 PM EDT: Thread[Thread-25,5,main]
    ERROR: XMLProvider.getContent():Error in XML transformation.
    XML piece looks like this:
    <Story>
    <headline>Scientists finish the DNA book of life</headline>
    <url>http://apidemo.yellowbrix.com/pages/apidemo/Story.nsp?story_id=38091348& amp;ID=apidemo</url>
    <pubsource>Evening Times; Glasgow (UK)</pubsource>
    <pubdate>2003-04-14</pubdate>
    <arrival_time>Apr 15, 01:11 AM </arrival_time>
    <category>Biotechnology</category>
    </Story>
    url element has '&' before ID has been properly taken care of with escape codes '& amp;' from the content provider.
    The issue is that the xml document goes through fine when I copy this feed in a file and run the portal.
    Anyone any ideas please.
    Thanks.

    Thanks for the reply. I tried using 'value-of' and 'copy-of' and it didn't work. While using 'value-of' portal hangs and timesout.
    XSL looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="html" indent="yes"/>
    <xsl:template match="/">
    <html>
         <body style="font-family:Arial,helvetica,sans-serif;font-size:12pt; background-color:#EEEEEE">
              <xsl:for-each select="WebApi/Story">
                   <div>
                        <span style="font-weight:bold;color:white">
                        <a> <xsl:attribute name="href">
    <xsl:copy-of select="url"/> </xsl:attribute><xsl:value-of select="headline"/></a>
                        </span>
                   </div>
              </xsl:for-each>
         </body>
    </html>
    </xsl:template>
    </xsl:stylesheet>
    Sample piece of XML
    <WebApi>
    <Story>
    <headline>Gene Work May Help Treat Aging</headline>
    <url>http://apidemo.yellowbrix.com/pages/apidemo/Story.nsp?story_id=38158601&ID=apidemo</url>
    <pubsource>The Boston Globe</pubsource>
    <pubdate>2003-04-17</pubdate>
    <arrival_time>Apr 17, 10:10 AM </arrival_time>
    <category>Biotechnology</category>
    </Story>
    </WebApi>

  • XML marshalling exception

    Hello,
    I'm using Toplink JAXB to generate XML document from java classes in a JSF application (all in JDeveloper 10.1.3).
    Everything works fine in JDeveloper embedded OC4J, but when deploed to OAS 10.1.3, the application gives the following exception:
    Exception [TOPLINK-25007] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.XMLMarshalExceptionException Description: A descriptor for class com.allstate.mqq.re.xao.jaxb.map.MqqrequestImpl was not found in the project]
    Has anyone experienced the same problem?
    Please help
    Thanks
    Kate

    See:
    Re: Toplink JAXB Marshalling
    -Blaise

Maybe you are looking for