Hi everyone, Thanks so much for all the help....I went ahead and tried the ENCODING=CDATA on the fields that I know have possible weird characters...Now I get a response (I don't know whether it's the client server or Tango) that makes little sense...
"http://posturl.com: unable to send data: Operation now in progress" What is going on?? Here's the <@URL> Statement: <@URL LOCATION='http://posturl.com' <@CRLF>Content-Type: text/xml; charset=utf-8<@CRLF>POSTARGS='<?xml version="1.0" encoding="ISO-8859-1" ?>'<@VAR NAME="aiiDOM">'> Ummmmm help? This is so frustrating...to be so close and yet have this as a barrier to completion!!! >_< On 7/26/06 8:51 AM, "Scott Cadillac" <[EMAIL PROTECTED]> wrote: > Hi Kaustav, > > Posting your actual codes helps a lot. > > Basically the way this is now leaves you wide open for problems. > > If the value of your @@Market_MID variable (or any variable inside the XML) or > any of your <@ARG>'s contain characters like <, >, or & - then this will break > your XML upon assignment. > > Try adding ENCODING=CDATA to your variables and arguments, and see if that > helps. > > Good luck. > > Scott Cadillac, > Email: [EMAIL PROTECTED] > http://scott.cadillac.bz > > >> -----Original Message----- >> From: Kaustav Acharya [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, July 26, 2006 9:36 AM >> To: witango-talk@witango.com >> Subject: Re: Witango-Talk: @ASSIGN & XML? >> >> Good Morning Scott and all! >> >> Here is the original code...what's happening here that's >> causing tango to choke? Market_MID is being called from a >> branch that we have in the program (and we have it working in >> other programs so we know it works fine... I am new to XML, >> but I think the formatting is ok? Let me know!! This is with >> the DOM correct formatting: >> >> >> <@ASSIGN NAME="aiiDom" SCOPE="request" VALUE="<@DOM VALUE='<lead> >> <vendorCode>COLONLINE</vendorCode> >> <vendorLeadIdentifier>@@Market_MID</vendorLeadIdentifier> >> <versionIdentifier>3</versionIdentifier> >> <testCase>Y</testCase> >> <nameLast><@ARG LASTNAME></nameLast> >> <nameMiddle/> >> <nameFirst ><@ARG FIRSTNAME></nameFirst> >> <nameSuffix/> >> <addressLine1 ><@ARG ADDRESS1></addressLine1> >> <addressLine2 ><@ARG ADDRESS2></addressLine2> >> <addressCity ><@ARG CITY></addressCity> >> <addressState ><@ARG STATE></addressState> >> <addressZip ><@ARG ZIPCODE></addressZip> >> <addressCountryCode ><@ARG COUNTRY_CODE></addressCountryCode> >> <homePhone ><@ARG AREA_CODE_1><@ARG PHONE1></homePhone> >> <workPhone/> >> <otherPhone ><@ARG AREA_CODE_2><@ARG PHONE2></otherPhone> >> <internationalPhone >1<@ARG AREA_CODE_1><@ARG >> PHONE1></internationalPhone> >> <email ><@ARG EMAIL></email> >> <bestTimeToCall ><@ARG TIME_TO_CALL></bestTimeToCall> >> <highSchoolGradYear ><@ARG GRAD_YEAR></highSchoolGradYear> >> <educationCompleted/> >> <dateDegreeCompleted/> >> <studentVisaRequired >N</studentVisaRequired> >> <countryCitizenship/> >> <militaryStatus/> >> <locationCode><@ARG SCHOOL_CODE></locationCode> >> <areaOfInterest/> >> <programOfInterest ><@ARG PROGRAM></programOfInterest> >> <educationObjective/> >> <inquiredBefore/> >> <sourceCode >COLOL</sourceCode> >> <sourceDate ><@CURRENTDATE format=%Y/%M/%D></sourceDate> >> <sourceTime ><@CURRENTTIME> </sourceTime> >> <sourceTimeOffset/> >> <sourceNumber/> >> <vendorAffiliate/> >> <comments/> >> <preassignedAda/> >> <warmTransferResult/> >> <other/> >> <validationResults/> >> <validationNotes/> >> <validationMessage/> >> </lead>'>"> >> >> >> On 7/25/06 5:07 PM, "Scott Cadillac" <[EMAIL PROTECTED]> wrote: >> >>> Thank you for the compliments Dale and Kaustav, >>> >>> And yes, having a big desktop can be useful >>> http://download.xmlx.net/my-desktop.gif :-) >>> >>> @LITERAL just takes whatever you feed the value as literal >> text. It's mostly >>> useful if assigning a variable that may contain Metatags, >> so the Metatags are >>> not interpreted until calling the variable with @VAR (with >> ENCODING=META or >>> ENCODING=METAHTML) >>> >>> @LITERAL is not a requirement for @DOM, but can be useful >> in some cases. >>> >>> Can you post the actual code Kaustav? Because other than >> the element name >>> issue I don't see any problems with the code you posted in >> your email. >>> >>> Let us know. >>> >>> Scott Cadillac, >>> Email: [EMAIL PROTECTED] >>> http://scott.cadillac.bz >>> >>> >>> >>> >>>> -----Original Message----- >>>> From: Kaustav Acharya [mailto:[EMAIL PROTECTED] >>>> Sent: Tuesday, July 25, 2006 5:54 PM >>>> To: witango-talk@witango.com >>>> Subject: Re: Witango-Talk: @ASSIGN & XML? >>>> >>>> Hmmmm that is interesting indeed! Does the <@LITERAL> assign >>>> the text following it to someDOMname? >>>> >>>> >>>> On 7/25/06 4:44 PM, "Dale Graham" <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>> >>>> You have to be careful on your quoting, too... >>>> >>>> <@assign name="someDOMname" scope="request" >>>> value="<@dom value='<startthevalues> >>>> <value1>Somevalue</value1> >>>> <value2>Somevalue2</value2></startthevalues>'>"> >>>> >>>> and mighten it be a good idea to call this with >>>> <@literal > (see below) ? Scott can speak better to this >> than I can. >>>> >>>> <@assign name="someDOMname" scope="request" >>>> value="<@dom value='<@literal "<startthevalues> >>>> <value1>Somevalue</value1> >>>> <value2>Somevalue2</value2></startthevalues>">'>"> >>>> >>>> On Jul 25, 2006, at 7:04 PM, Kaustav Acharya wrote: >>>> >>>> >>>> >>>> Hi there, >>>> >>>> I am fairly new at all this, so please bear with me... >>>> >>>> So here is what I am trying to do. Take some >>>> information acquired by a user on a form, store them in >>>> variables, put the variables in XML format, assign the whole >>>> xml into a <@DOM> and shoot it off to our client using <@URL> >>>> >>>> My question is this: >>>> >>>> If my syntax looks like this: >>>> >>>> <@ASSIGN NAME="someDOMname" SCOPE="request" >>>> VALUE=<@DOM VALUE="<startthevvalues> >>>> <value1>Somevalue</value1> >>>> <value2>Somevalue2</value2></startthevalues>">> >>>> >>>> Why does Tango return this error message? >>>> >>>> Main Error Number: -902 >>>> >>>> An error occurred while parsing the XML. >>>> Expected equal sign >>>> >>>> >>>> Meta Stack Trace: >>>> >>>> Line Meta Tag >>>> 0002 >>>> *The meta stack is interpreted top-to-bottom: >>>> the top line shows the inner metatag that caused the error. >>>> >>>> >>>> Line ³2² of this particular resultshtml is the >>>> <@ASSIGN> syntax where I am trying to assign all the xml into >>>> the DOM variable. Am I missing something obvious here? I >>>> tried a soap approach, but it seemed to complicated, so I >>>> figured I would try something a little easier... What is the >>>> the expected ³=² Tango is looking for? >>>> >>>> Any help would be great! Thanks! >>>> >>>> >>>> ____________________________________________________ >>>> Kaustav Acharya >>>> Tango Programmer >>>> >>>> U. Inc. >>>> 12250 El Camino Real, Suite #104 >>>> San Diego, CA. 92130 >>>> >>>> Office: (858) 847-3350 x1004 >>>> Fax: (858) 847-3340 >>>> email: [EMAIL PROTECTED] >>>> >>>> http://www.colleges.com >>>> ____________________________________________________ >>>> >>>> All the News. No Ink. - http://www.onlinetimes.com >>>> Power to the People - http://www.campaign.com >>>> ____________________________________________________ >>>> >>>> >>>> >>>> >>>> >>>> ______________________________________________________________ >>>> __________ >>>> TO UNSUBSCRIBE: Go to >>>> http://www.witango.com/developer/maillist.taf >>>> >>>> >>>> >>>> >>>> >>>> ______________________________________________________________ >>>> __________ >>>> TO UNSUBSCRIBE: Go to >>>> http://www.witango.com/developer/maillist.taf >>>> >>>> >>>> >>>> >>>> >>>> >>>> ______________________________________________________________ >>>> __________ >>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>> >>> >>> >> ______________________________________________________________ >> __________ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> >> ______________________________________________________________ >> __________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
