|
We are pleased to announce the Beta Release of eBay SDK for Java (JAX-WS verson).
In this Beta Release, the eBay SDK for Java has been migrated from Axis 1.1 to JAX-WS.
Two Point Releases for eBay SDK for Java (Axis 1.1), are also being released at this time. One release is for JDK 1.4 and the other is for JDK 1.5. These releases allow you to update your current Axis implementation to the 575 WSDL. See the Readme for more details.
The Beta Full Release for eBay SDK for Java (JAX-WS) includes a Migration Guide that describes how to move to the JAX-WS version. It also includes a Readme that discusses requirements for installation, installation instructions, and general release information.
This migration includes changes to the SDK core classes, wrapper classes, samples, and test cases. Stubs and datatypes are now generated with the wsimport tool under the JAX-WS standard, and this process is automated as before using Ant (the name of the buildfile is build.xml).
Also, starting with this release, the eBay SDK for Java will support the following JDKs:
We strongly recommend that you update your JDK if you are currently on JDK 1.4.
JDK 1.4 and Axis 1.1 WILL be supported for the next year, but there will not be any new SDK releases for the Axis environment.
We look forward to hearing your feedback regarding this Migration and we would appreciate your suggestions and input. You can send your valuable input to developer-webmaster@ebay.com.
You can now download the latest full release of the eBay SDK for .NET. Before installation, please read about the changes to the SDK in the Readme file and see the changes to the API in the Trading API Release Notes.
Beginning with this release, the SDK will only support Microsoft .NET Framework versions 1.1 and 2.0 (not version 1.0, which Microsoft has retired).
This SDK release also contains updated wrapper classes and other updates that facilitate your use of new API features. The new API features are described in the Trading API Release Notes.
We've made several improvements to the User Token retrieval process, and made it even easier for developers to configure and maintain their application-level settings. New features of the token retrieval process include:
We look forward to hear your feedback regarding this tool and will appreciate the suggestions and input.You could send your valuable
feedback to developer-webmaster@ebay.com.
Now you can check out the eBay Developers Conference 2008 industry keynotes virtually, complete with applause, laughter, and lots of thought provoking ideas about where our industry is headed. These industry speakers have a real point of view and deliver it with unique insights and the WOW factor - all from the developer's perspective.
Even if you attended these keynotes at DevCon they're worth another viewing:
Max Mancini, eBay, Senior Director of Platform and Disruptive Innovation and Rolf Skyberg, Disruptive Innovator, give a detailed demo of Project Echo, the opportunity for our developers to integrate their applications where sellers manage their businesses on eBay.com. Don't miss this one.
Rajiv Dutta, eBay, President of eBay Marketplaces, will pump you up with his passion which he backs up with facts about the strong economic force that is driven by our third-party developers. He really grasps what the developer community means to us.
Tony Hseih, CEO of Zappos.com, will make you rethink (or think!) about customer service and how the exponential affect of the returning customer can rock your bottom line. He'll tell you, in plain English, how it's done.
Adam Gross, Vice President, Platform and Developer Marketing at Salesforce.com makes the case for cloud computing with 3 key concepts that sound like a dream development environment. Here's the first one, "Power Law of Web APIs". If you're intrigued, and you should be, then watch the video for the other two concepts and find out how cloud computing changes the game.
As we've been announcing since March, the token-based REST API will be deprecated and will no longer be supported as of August 1st, 2008. Our Shopping API still supports REST-style calls (traditionally URL in and XML out). If you currently use the "REST API," you should switch to using the REST format with Shopping API calls.
As of August 1st, there will no longer be any support, updates or enhancements for the deprecated REST API. Developers continuing to make active REST API calls after August 1st will begin to receive warning messages returned as part of the initial phase of deprecation. Eventually, deprecated REST API calls will return error messages, and applications who have not yet migrated to the Shopping API and continue to make active REST API calls will no longer function.
We strongly recommend switching to the Shopping API Get HTTP protocol for your development, since the Shopping API covers the same functionality as the token-based REST API and is easier to use.
As of March, making REST calls has become easier with the Shopping API. You no longer need a token to make HTTP Get (REST) calls!
- The deprecated REST API used to support URL in and XML out only.
- The deprecated REST API used a special token, called the "REST token" for authentication. You will no longer be able to generate NEW REST tokens. Your existing REST tokens will not be disabled.
- The deprecated REST API primarily supported one call: GetSearchResults.
- The Shopping API supports URL in and XML out, but also supports many other formats.
- The Shopping API uses your AppID for authentication, no special token required.
- The Shopping API supports several search and retrieval calls. For a full list, see the Call Ref.
To help migrate your application to Shopping API calls if you are still using a token-based REST API call, see the eBay REST API Guide for a table showing the comparable Shopping API calls. Also see the field by field mapping from GetSearchResults to FindItemsAdvanced (in Shopping API).
For technical questions about migrating from the deprecated REST API to Shopping API, you can post questions in our Shopping and Merchandising API Forum, or fill out a Support Request for a more immediate response using our premium technical support channel.
-Delyn
 |
