16 messages in com.googlegroups.adwords-apiRe: Update re: new minCpc attribute| From | Sent On | Attachments |
|---|---|---|
| AdWordsAPIAdvisor | 17 Aug 2005 17:34 | |
| Richard Jones | 18 Aug 2005 02:58 | |
| wrestler | 18 Aug 2005 05:50 | |
| Kostas | 18 Aug 2005 06:15 | |
| peter | 18 Aug 2005 07:19 | |
| Richard Jones | 18 Aug 2005 07:22 | |
| Jordan | 18 Aug 2005 14:34 | |
| Rajiv M | 18 Aug 2005 16:19 | |
| Jordan | 19 Aug 2005 09:54 | |
| Harien de Mel | 22 Aug 2005 06:36 | |
| Rajiv M | 22 Aug 2005 08:23 | |
| tomasvdb | 22 Aug 2005 09:30 | |
| Harien de Mel | 23 Aug 2005 01:09 | |
| tomasvdb | 24 Aug 2005 01:35 | |
| Harien de Mel | 30 Aug 2005 07:48 | |
| tomasvdb | 30 Aug 2005 08:32 |
| Subject: | Re: Update re: new minCpc attribute![]() |
|---|---|
| From: | Jordan (jord...@gmail.com) |
| Date: | 08/18/2005 02:34:09 PM |
| List: | com.googlegroups.adwords-api |
Hi,
I am getting the same invalid minCpc element error. I am trying to fix it, but am confused by your proposed solution. How do I "regenerate the client stubs from the new WSDL file"? I have the adwords jar file which dates from June 2005 and has no source code. In my source code, I had to change the import statement that was in the example code as "import com.google.api.adwords.v2.*" to "import com.google.api.adwords.*". I am using an old library? Do I have to wait for a new jar file to get this to work? -Jordan
AdWordsAPIAdvisor wrote:
The new minCpc attribute in Keywords is causing trouble for some of our user's AdWords API clients. In particular people using Java and Apache Axis have been reporting errors like org.xml.sax.SAXException: Invalid element in com.google.api.adwords.v2.Keyword - minCpc
We expect similar errors may occur in other statically typed languages like C# and C++. If you are getting errors like this, please try regenerating the client stubs from the new WSDL file and recompiling your client code. That should take care of the problem, hopefully with no changes required in your own client code.
We apologize for the inconvenience, we didn't expect this change to cause a problem for our users.
--AdWords API Advisor




