I don't know if that was the answer you were looking for. When the debugging info does not give me useful information I generally when trying to tease out offending items I used divide and conquer method. Take 1/2 of the of the offending code/data/string etc. in iterations until you isolate the offending item.
HTH G! On Fri, Feb 19, 2010 at 12:16 PM, Gerald Guido <gerald.gu...@gmail.com>wrote: > You probably have a stray & in the xml. The XmlFormat() function should > clean that up. > Like so: > #XmlFormat(YourXMLString)# > > > > On Fri, Feb 19, 2010 at 11:48 AM, Don <danfar...@hotmail.com> wrote: > >> >> I am utilising XML parse ( when CF encounters a bum XML file it throws CF >> error ). But I've found the information returned is very limited. For >> example - 'The entity name must immediately follow the '&' in the entity >> reference.' - Obviously it would be nice to have more specific information >> such as line number that caused the error. >> >> exploring the Factory debugging service, I am trying to retrieve more >> information ( than standard Coldfusion Debugger ) whilst parsing an XML >> using XMLParse. >> >> Any idea which direction I should be going in? >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330942 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
