How is DW-generated XML not well-formed?

<ASP:Repeater DataMember="<%#
DataSetScheduleByDate.FieldValue("", Container) %>"
DataSource='<%# DataSetScheduleByDate.DefaultView %>'
runat="server">
This was generated by DW. When I run the page, its telling me
that line 116 is not well formed. Since this was generated, I'm
curious what's wrong? This is part of a datagrid and perhaps I'm
just not assigning things correctly?

What does the xml page around line 116 look like?
Dave
"dl0haus" <[email protected]> wrote in
message
news:fqkebl$mf9$[email protected]..
> <ASP:Repeater DataMember="<%#
DataSetScheduleByDate.FieldValue("",
Container)
> %>" DataSource='<%#
DataSetScheduleByDate.DefaultView %>' runat="server">
>
> This was generated by DW. When I run the page, its
telling me that line
116
> is not well formed. Since this was generated, I'm
curious what's wrong?
This
> is part of a datagrid and perhaps I'm just not assigning
things correctly?
>

Similar Messages

XML not well formed - Java Mapping, Webservice to RFC Scenario

Hello All Experts,
I have facing a strange type of error. I have written a Java Mapping which implements a DOM parser to take a request from a Webservice and validate it on the basis of some prerequisites. i.e. If data in the incoming request is valid, it creates a message of the same structure type as the input. If the incoming data is incorrect or incomplete; It generates an Error response structure.
When I run and test the same mapping program using Editplus Java editor for the error scenario; it executes perfectly and creates the correct error XML structure. (I checked it by importing the structure in the XI Message mapping test tab). But when I create jar of my java mapping program and test it in my interface mapping, it gives me "XML not well formed error" (Problem while building the tree).
Any idea as to why is it behaving in such a way? There are 2 reasons which come to my mind as of now:
1. The initilization of my input and output streams in the public static void main:
            InputStream in = new FileInputStream(new File("Input.xml"));
           OutputStream out = new FileOutputStream(new File("Output.xml"));
           validateXML myMapping = new ValidateXML();
            myMapping.execute(in, out);
The Output.xml has the xml structure for the correct case, do I have to initialize my outputstream for the error file? say error.xml
2. My Webservice interface is a sychronous interface (Request / Response) and output of the Java mapping program are two asynchronous interface. (I'll use a synch-asynch bridge when this works) - Is that causing a problem?
Please help.
Best regards,
Varun

Hello Varun,
it gives me "XML not well formed error" (Problem while building the tree).
I have come across the same error message while testing in interface mapping. My problem was when an exception occured in java mapping, the execution terminates with the messages XML not well formed error". In order to solve this issue what i did was catch the exception type TransformerException and in that catch block throw StreamTransformationException exception in main methos of mapping program i.e execute().
eg:-
catch (TransformerException e) {
               throw new StreamTransformationException("Can not write XML.", e);
By doing this you will see the exception raised , because some times when you execute your mapping with mail() method, though it create the file, when you try to open it will give error if any exceptions occured in mapping. By using the above notation you can handle those in java mapping.
Hope you have gone through this blog.
[Handling and Tracing Exceptions in java mapping|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID1055371050DB01666765031379427182End?blog=/pub/wlg/15061]
Regards,
Prasanna

XML Not well formed, Mapping error

Hi All,
I'm trying a simple file to file scenario..
Following is the structure of source and target file..
Source structure
===============
<?xml version="1.0" encoding="UTF-8"?>
<ns:SourceMT xmlns:ns="urn:tmp:workshop:file2file">
<Src1>1</Src1>
<Src2>2</Src2>
</ns:SourceMT>
Target Structure
===============
<?xml version="1.0" encoding="UTF-8"?>
<ns:TargetMT xmlns:ns="urn:tmp:workshop:file2file">
<Tgt1>1</Tgt1>
<Tgt2>2</Tgt2>
</ns:TargetMT>
I did a one to one mapping for the two fields and tested the same using the test tool in IR and it works fine..
However when I put the same source xml structure in the Input file it gives me the below error..
Also when I copy the payload from the sxmb_moni and paste the same in the test tool in IR it throws an error saying
"XML not well-formed"
Error
=====
<SAP:Stack>During the application mapping com/sap/xi/tf/_FileMM_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Payload
=======
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:SourceMT xmlns:ns="urn:tmp:workshop:file2file">
<Src1>1</Src1>
<Src2>2</Src2>
</ns:SourceMT>
Any inputs are greatly appreciated..
Thanks and Regards,
Nazim

Hi ,
<i>During the application mapping com/sap/xi/tf/_FileMM_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</i>
It is clearly saying that exception in mapping....Check your mapping correcly with one to one mapping.Dont do any mapping to the root node and check it...
And also check this...
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Sekhar

Re: XML NOT WELL FORMED??

Hi all I have the 8520 curve. All was well till today And now I'm also getting XML NOT WELL FORMED Its not on all sites as yet But its so annoying. I've also done all that's been Sujested here and still have the Problem. The only thing I have done Today is update the blackberry Messenger as I was fed up with the Update message. oh how I wished I hadn't. But maybe this would Have happened anyway by seeing how Many are having the same problem. Anyone got any other ideas or know Of a number in the uk I could call For advice. Or should I call o2 Can anyone help us all. Bless you all for trying. Thanks. Ps please go easy on tec stuff as I'm New to blackberry and feel like A right dummy, which I feel like Spitting out every time the xml message appears lol
Solved!
Go to Solution.

Hello,
In this case we can try to reload the software on the BlackBerry smartphone to make sure it is running the latest version and there are no issues with the OS.
To do this we would need to back up the BlackBerry smartphone. Please open the BlackBerry Desktop Manager and connect your BlackBerry smartphone. Click on the Backup and Restore button and select Back Up. Please note the location where the backup is being saved as we will need to access it later to restore the BlackBerry smartphone.
Once you have backed up your BlackBerry smartphone please follow the link below to complete a clean reload of the BlackBerry smartphone software.
Link: http://www.blackberry.com/btsc/KB11320
Please test the BlackBerry smartphone prior to restoring your data.
Thank you
-DrP
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

XML not well formed in - XSLT mapping

Hi,
I am doing a simple xslt mapping wherein my Source data structure is
MT
|__ details
        |__ Records
                  |_emp_no
                  |_ emp_name
                  |_emp_dno
In XSL file i hv specified <xsl:template match="MT">
and I am using <for-each select="details/Records">
when I m testing it in Interface mapping, it is giving me error "XML not well formed"
can anybody please suggest whats the problem in the code??
Thank you,
Anu Singhal

Hi Anu,
    I think in the select query in xslt mapping u have to mention the expression "//" so that for each iteration it can go according the path.
< for-each select = " //details/records">
I have some sample code of same type...just check it..
<xsl:template match="/">
<MT_EMP_TARGET>
     <xsl:for-each select="//EMP_DATA">
          <EMP_DATA>
                        <xsl:variable name="fname" select="//EMP_DATA/First_Name"/>
                        <xsl:variable name="lname" select="//EMP_DATA/Last_Name"/>
               <Emp_Code><xsl:value-of select="//EMP_DATA/Emp_Code"/></Emp_Code>
               <Name><xsl:value-of select="concat($fname,' ',$lname)"/></Name>
               <Join_Dt><xsl:value-of select="//EMP_DATA/Join_Dt"/></Join_Dt>
               <Designation><xsl:value-of select="//EMP_DATA/Level"/></Designation>
               <Dept><xsl:value-of select="//EMP_DATA/Dept"/></Dept>
          </EMP_DATA>
     </xsl:for-each>
</MT_EMP_TARGET>
</xsl:template>
For more info:
http://www.w3schools.com/xsl/el_for-each.asp
Cheers,
Prasanthi.
Reward marks if helpful.

"XML not well-formed" error while testing Interface mapping.

Hello Experts,
I have a simple Interface mapping test, where a single input field of type string is mapped to a target Interface.
The content of a string actually will be a XML. I am using a XSLT mapping to convert string XML to XML. The XSLT mapping used by me is as :
<?xml version="1.0" encoding="ISO-8859-1" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes" />
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()" />
</xsl:copy>
</xsl:template>
<xsl:template match="/">
<xsl:value-of select="//string" disable-output-escaping="yes" />
</xsl:template>
</xsl:stylesheet>
Test data to be used is :
<?xml version="1.0" encoding="ISO-8859-1"?>
<string>
<catalog>
     <cd>
          <title>Empire Burlesque</title>
          <artist>Bob Dylan</artist>
          <country>USA</country>
          <company>Columbia</company>
          <price>10.90</price>
          <year>1985</year>
     </cd>
     <cd>
          <title>Unchain my heart</title>
          <artist>Joe Cocker</artist>
          <country>USA</country>
          <company>EMI</company>
          <price>8.20</price>
          <year>1987</year>
     </cd>
</catalog>
</string>
My Target structure is like:
catalog
CD
    title
    artist
    country
    company
    price
    year
No matter what I input as a test data , I get the error as "XML not well-formed" while testing Interface mapping.
Please suggest what could be the reason for this error?
Regards,
Abhi.

Hi check your XSLT mapping in XMLY spy with test data,the out of the XSLT Mapping should be valid XML , then only you can see output in interface mapping.
Regards,
Raj

Error using XML Loader: XML not well-formed

Hi all,
I am facing a problem using the XML loader in xMII 12.0 when trying to load the following XML file:
<?xml version="1.0" encoding="UTF-8"?>
<Users>
<User>
    <UserID>IMXOO</UserID>
    <CWID>IMXOO</CWID>
    <Prename>Michael</Prename>
    <Surname>Otto</Surname>
    <CreatedOn>2001-12-31T12:00:00</CreatedOn>
    <CreatedBy>IMXOO</CreatedBy>
</User>
</Users>
I also tried a most basic XML file which shows the same error:
<?xml version="1.0"?>
<ausgabe>
<anzeige>Testausgabe</ausgabe>
</ausgabe>
To my understanding both files are well-formed, however xMII shows the error:
"The markup in the document following the root element must be well-formed."
Do I break any rules concerning the markup? IE loads the files without showing any errors.
Best Regards
Michael

Jeremy,
again you gave the key to the solution. When the error occured, I have set up the following path within the xMII workbench:
"Catalog-Tab"
<server>
  > Sandbox
        > XML
            myFile.xml
When I tried to load the mxFile.xml with the XML Loader, I got the error described above (XML not well-formed). I also cannot drag the file into a transaction in the workbench. I have manually configured the XML Loader with "http://<server:port>/XMII/CM/Sandbox/XML/mxFile".
Now using your hint I have changed to the "Web-Tab":
"Web-Tab"
<server>
    > Sandbox
        > WEB
            > XML
                myFile.xml
Then all works fine, when I now drag the file into the transaction. As you described, an XML Loader action is created with configuration "db://Sandbox/WEB/XML/myFile.xml" and the XML is loaded correctly.
Thanks for your help!
Best regards
Michael

XML Not well formed

I have an XSLT mapping as described below:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/biztalk_1">
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
<ns0:header>
<ns0:delivery>
<ns0:message>
<ns0:messageID><xsl:value-of select="header/delivery/message/messageID"/></ns0:messageID>
</ns0:message>
</ns0:delivery>
</ns0:header>
<ns0:body>
<ns0:FinancialTransaction.CreateFromData>
<ns0:CompanyCode><xsl:value-of select="body/FinancialTransaction.CreateFromData/CompanyCode"/></ns0:CompanyCode>
</ns0:FinancialTransaction.CreateFromData>
</ns0:body>
</ns0:biztalk_1>
</xsl:template>
</xsl:stylesheet>
however when I execute this mapping I keep getting the error saying that the XML is not well formed...
I have looked at it but really cant see where I am going wrong.. Could someone take a look at the above xslt and let me know where this error could be coming from....

ok this is the xslt again
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/biztalk_1">
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
<ns0:header>
      <ns0:delivery>
         <ns0:message>
            <ns0:messageID><xsl:value-of select="header/delivery/message/messageID"/></ns0:messageID>
         </ns0:message>
      </ns0:delivery>
   </ns0:header>
   <ns0:body>
      <ns0:FinancialTransaction.CreateFromData>
         <ns0:CompanyCode><xsl:value-of select="body/FinancialTransaction.CreateFromData/CompanyCode"/></ns0:CompanyCode>
      </ns0:FinancialTransaction.CreateFromData>
   </ns0:body>
</ns0:biztalk_1>
</xsl:template>
</xsl:stylesheet>
and the source will look something like this
<?xml version="1.0" encoding="UTF-8"?>
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
   <ns0:header>
      <ns0:delivery>
         <ns0:message>
            <ns0:messageID/>
            <ns0:sent/>
         </ns0:message>
      </ns0:delivery>
   </ns0:header>
   <ns0:body>
      <ns0:FinancialTransaction.CreateFromData>
         <ns0:CompanyCode/>
      </ns0:FinancialTransaction.CreateFromData>
   </ns0:body>
</ns0:biztalk_1>
There are actually more fields but this is a toned down version...

How to validate that XML is well-formed?

I have an "Any XML Service" on Oracle Service Bus (version 11.1.1.4) that I would like to have validate that the input is well-formed XML. There is no DTD or XSchema to apply -- it can be any generic well-formed XML. I didn't see a way to do it with a Validate Action. Is a Java Callout my only option?
Thanks,
Doug Newton

That's interesting...
Try creating a xquery expression using fn-bea:inlinedXML(), it doesn't require XSD
The fn-bea:inlinedXML() function parses textual XML and returns an instance of the XQuery 1.0 Data Model.
The function has the following signature:
fn-bea:inlinedXML($text as xs:string) as node()*
where $text is the textual XML to parse.
Examples:
fn-bea:inlinedXML(“<e>text</e>”) returns element “e”.
fn-bea:inlinedXML(“<?xml version=”1.0”><e>text</e>”) returns a document with root element “e”.
http://docs.oracle.com/cd/E13162_01/odsi/docs10gr3/xquery/extensions.html#wp1295964
Cheers,
Vlad
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893

XML - writing file #1088 (xml not well formed)

Hi,
What could cause the IO Error #1088 within the code below? All I can think of is white space issue. It prints to the screen AND saves to the xml file correctly, just keeps throwing up the code.
Also, writing it this way wont' allow me to add <?xml version='1.0' encoding='utf-8'?> is it required?
Thanks for any help.
var authors:XML;
authors =<authors>
                <author>
                <firstname>Rich</firstname>
                <lastname>Shupe</lastname>
                </author>
                <author>
                <firstname>Zevan</firstname>
                <lastname>Rosser</lastname>
                </author>
                </authors>;
var xml =authors;
var book:XML = new XML(xml);
var xmlResponse:XML;
var xmlURLReq:URLRequest = new URLRequest("saveXML.php");
xmlURLReq.data = book;
xmlURLReq.contentType = "text/xml";
xmlURLReq.method = URLRequestMethod.POST;
var xmlSendLoad:URLLoader = new URLLoader();
xmlSendLoad.addEventListener(Event.COMPLETE, onComplete, false, 0, true);
xmlSendLoad.addEventListener(IOErrorEvent.IO_ERROR, onIOError, false, 0, true);
xmlSendLoad.load(xmlURLReq);
function onComplete(evt:Event):void {
    try {
        xmlResponse = new XML(evt.target.data);
        respTxt.text = xmlResponse;
        removeEventListener(Event.COMPLETE, onComplete);
        removeEventListener(IOErrorEvent.IO_ERROR, onIOError);
    } catch (err:TypeError) {
        respTxt.text = "An error occured when communicating with server:\n" + err.message+" "+xml;
function onIOError(evt:IOErrorEvent):void {
    respTxt.text = "An error occurred when attempting to load the XML.\n" + evt.text;

Answered it myself....
The PHP script was adding additional<tags></tags> so the file I was outputing read:
<root>
<teams>
<team1></team1>
<team2></team2>
</teams>
</root>
<phpaddedInfo></phpaddedInfo>
so just a good idea to look in both places when you get an IO error #1088

The XML generated by the Lotus servlet component is not well formed

Hello Experts,
While integrating EP7 to Lotus Domino 7 we are facing some problem with XML parser.
We have following configuration
EP7 SP 13
Lotus Domino 7
All configurations related to SSO are done. SSO is working fine.
All transports are created properly. All services active
Please suggest some solution
The error is displayed when i try to access the calendar related objects, like calendar, appointments etc.
Here is error detail:
The XML generated by the Lotus servlet component is not well formed com.sap.ip.collaboration.gw.impl.transport.lotus.exception.XMLParserException: The XML generated by the Lotus servlet component is not well formed
     at com.sap.ip.collaboration.gw.impl.transport.lotus.LotusCalendarTransport.getXmlDocument(LotusCalendarTransport.java:997)
     at com.sap.ip.collaboration.gw.impl.transport.lotus.LotusCalendarTransport.readResponse(LotusCalendarTransport.java:1922)
     at com.sap.ip.collaboration.gw.impl.transport.lotus.LotusCalendarTransport.getLotusServerTz(LotusCalendarTransport.java:405)
     at com.sap.ip.collaboration.gw.impl.transport.lotus.LotusCalendarTransport.getItemList(LotusCalendarTransport.java:377)
     at com.sap.ip.collaboration.gw.impl.framework.groupware.GroupwareManager.getItemList(GroupwareManager.java:263)
     at com.sap.ip.collaboration.gw.impl.manager.calendar.ContentManager.getChildren(ContentManager.java:237)
     at com.sapportals.wcm.repository.CollectionImpl.internalGetChildrenManager(CollectionImpl.java:1538)
     at com.sapportals.wcm.repository.CollectionImpl.internalGetChildren(CollectionImpl.java:1555)
     at com.sapportals.wcm.repository.CollectionImpl.doGetChildren(CollectionImpl.java:144)
     at com.sapportals.wcm.repository.CollectionImpl.getChildren(CollectionImpl.java:124)
     at com.sap.ip.collaboration.gwui.api.GWUtils.getAllCalendarItems(GWUtils.java:180)
     at com.sap.ip.collaboration.gwui.api.htmlb.component.day.DayControlDynPage.doProcessBeforeOutput(DayControlDynPage.java:65)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
     at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     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:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Waiting for replies
Regards
Kedar Kulkarni
Do Not worry for points.

Hello Michael Sambeth and all Lotus experts,
I read about a tool for Lotus Domino Ticket Verifier that is delivered by SAP.
Can you please send it to kedar.c.kulkarni @ gmail.com
I actually posted a thread, but could not get any reply for SAP standard error: GW-LOT-014
regards
Kedar Kulkarni
Edited by: Kedar Kulkarni on Apr 9, 2008 12:11 PM

What is a (xml parsing error:not well-formed) and how to fix this

what is a (xml parsing error:not well-formed) and how to fix this
== URL of affected sites ==
http://sudburyfinecars.subarudealer.ca
== Troubleshooting information ==
XML Parsing Error: not well-formed
Location: http://sudburyfinecars.subarudealer.ca/WebPage.aspx?WebSiteID=205
Line Number 258, Column 152:

I found the solution to my own problem by using Internet Explorer instead of Firefox, it turn out that the site i was trying to get into is an old site using proxy servers that Firefox doesn't read properly giving me the XML parsing error:not well-formed.
Its not Firefox's fault its just letting you know that this could be a problem site if it lets you in.

How to format a not well formed xml into well formed

Hi,
Here's what I'm trying to do: I have a build a report based on query results. In the query result, one field is a CLOB (which contains XML. The XML contains two tags - "description" and "count"). I want to read (&parse) the XML and store the "description" and "count" in a hashmap. But when I try to parse it, I end up in an error. I'm currently using XmlParse but I got an error "The markup following the root element should be well formed." I immediately used IsXml() to find out if the XML I am reading is well formed. And the answer is "NO".
Could someone help me in converting it into a "well formed" one?
(This is what I've tried: I appended "<?xml version="1.0" encoding="UTF-8"?>" to the XML I'm reading coz it was missing this. I later used XmlFormat to convert the XML into a string format. But IsXML tells me that even this is not well formed.)
Thanks much for your help!

XML encodes information is a specific way. Well-formedness determines whether or not a string is an XML document in the first place.
However, as well-formedness can be broken by any arbitrary number of factors, it is in general impossible to automate the repair process to recover a well-formed XML document. You have to do it manually, using an XML or a text editor.

XML from CF not well-formed?

I have been working through the Training from the Source book
on Flex2 (Trapper, Boles, Talbot, etc.). In Lesson 17, it deals
with accessing server-side objects.
One piece of code accesses a CF template, which brings in an
XML file:
<mx:HTTPService id="prodByCatRPC"
url="
http://localhost/flexGrocer/xml/categorizedProducts.cfm"
result="prodByCategoryHandler(event)"
resultFormat="e4x" />
The CF plate from the book's file has the following:
<cfheader name="Expires" value="#now()#" />
<cfxml variable="xProducts">
<cfinclude template="categorizedProducts.xml">
</cfxml>
<cfset xmlObject=ToString(xProducts)>
<cfcontent type="text/xml" />
<cfoutput>#variables.xmlObject#</cfoutput>
When run the Flex file, I get a run-time message which seems
to indicate that the XML is not well-formed. (Here is a bit of the
message; not sure I'm understanding it!):
[RPC Fault faultString="Error #1088: The markup in the
document following the root element must be well-formed."
faultCode="Client.CouldNotDecode" faultDetail="null"]
I am ASSUMING that the CF page is not returning the xml as
desired, because if I simply change the flex http service call to
the xml file that the CF page is including, the flex app runs as
expected and without errors:
url="
http://localhost/flexGrocer/xml/categorizedProducts.xml"
(something in the posting mech is making the above url
statement messed up, but you can probably tell what I mean)
I am a CF developer and although haven't used the book's
exact method to get the cf generated xml, I have done so
successfully for Spry and other things.
I tried some ot the things I had to do to get the CF
generated xml to work in Spry with this flex, but didn't help.
Tried adding a reset='true" with the cfcontent tag; tried making
the cfcontent wrap the output; added cfprocessing tags to
suppresswhitespace.
Appreciate any thoughts/help on how to solve this. Also,
whether others agree that the problem is with the generated xml
rather than something else.
Thanks
Keith

I don't remember the exact context when I first posted this
question and answered it; but, if one doesn't want to change
overall settings for debugging in cf admin., I *think* you can
ajust for a specific area using cfsetting and/or
cfprocessingdirective. There's a number of attributes and
combinations there that I think can take care of the problem. I
forget for sure, but may want to try that, especially on a
development box where you might generally want debugging to be on.
Also, if using cfcs in any part of what you generate, they
can produce whitespace. To solve (or minimize), make sure that
output attribute in the component is false and that output in
function is false (unless directly outputting within the function.
Seems like CF and whitespace is an ongoing item to try to
manage.
Keith

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

How is DW-generated XML not well-formed?

Similar Messages

Maybe you are looking for