+1 Thanks, Mridul Pathak
On Fri, Jul 3, 2026 at 2:58 PM Anil Patel <[email protected]> wrote: > Hi all, > > I'd like to propose removing the two eBay components, ebay and ebaystore, > on the same grounds we have recently used to retire other dead third-party > integrations. > > Both components are built entirely on eBay's old XML Trading API - they > call api.ebay.com/ws/api.dll with a pinned compatibility level of 635, > which is well over a decade old (eBay is now in the 1400s). eBay marked the > Trading API as legacy and ended active support for it at the end of 2021; > it gets no further enhancements and is being decommissioned call by call, > and the related Finding and Shopping APIs were switched off entirely in > February 2025. eBay's direction now is their REST APIs (Browse, Sell, > Taxonomy) with OAuth 2.0. So neither component can actually talk to live > eBay any more without a full rewrite - new API, new auth model, essentially > a new integration. > > Our own tree already reflects this. ebaystore has shipped disabled by > default (enabled="false") since the 2017 component-loading refactor > (OFBIZ-9182), and ebay, while still enabled, targets the same dead Trading > API. There is no working demo and no practical way to exercise either one. > > > This is really the same situation Mridul Pathak cleaned up recently when he > removed the defunct tax integrations, Taxware and ZIPsales (OFBIZ-7936), > the deprecated third-party payment gateways (OFBIZ-13446), and the > deprecated shipping carrier integrations (OFBIZ-7935 and OFBIZ-13447). The > eBay components are the same kind of thing - a third-party integration > whose backing service is effectively gone - and I think they should follow > the same path. > > > What prompted this was OFBIZ-3447, an old cosmetic formatting bug on the > ebaystore Export Product Listings page. Rather than fix the layout on a > page that is disabled by default and can no longer reach eBay, I'd rather > we retire the components. > > > I'll raise a Jira issue to remove both components - keeping the code in git > history for anyone who ever needs it - and follow the precedent of Mridul's > earlier removals. Objections, or reasons to keep them, are of course > welcome. > > > > Thanks and Regards > Anil Patel > CEO > HotWax Systems > http://www.hotwaxsystems.com >
