splitup of ebay component.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

splitup of ebay component.

hans_bakker
Hi follow OFBiz users.

as you have seen at the latest commits we have extended the ebay
component by using the Ebay API which allows an ofbiz user to (almost)
maintain all Ebay functions within OFBiz.

Up to now there was no overlap between the existing XML functions and
the new API functions, however there now will be.....

Uploading products in the existing ebay function does not allow
maintaining inventory within in Ebay, but the new upload function does
or does not allow it set by a flag, so there is overlap.

We plan further to duplicate all XML functions using the API interface.

So hereby we propose to rename the existing Ebay component to "EbayXml"
and create a new Ebay component called "EbayAPI" both in the specialized
directory.

comments or suggestions?

--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

Scott Gray-2
Hi Hans,

Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?

If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 28/01/2010, at 9:32 PM, Hans Bakker wrote:

> Hi follow OFBiz users.
>
> as you have seen at the latest commits we have extended the ebay
> component by using the Ebay API which allows an ofbiz user to (almost)
> maintain all Ebay functions within OFBiz.
>
> Up to now there was no overlap between the existing XML functions and
> the new API functions, however there now will be.....
>
> Uploading products in the existing ebay function does not allow
> maintaining inventory within in Ebay, but the new upload function does
> or does not allow it set by a flag, so there is overlap.
>
> We plan further to duplicate all XML functions using the API interface.
>
> So hereby we propose to rename the existing Ebay component to "EbayXml"
> and create a new Ebay component called "EbayAPI" both in the specialized
> directory.
>
> comments or suggestions?
>
> --
> Antwebsystems.com: Quality OFBiz services for competitive rates
>


smime.p7s (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

Florin Popa
Hi,

For our project we developed already most of the Ebay related
functionalities based on EbayAPI. Indeed there are few particular things
like the way we keep track of the products sent to ebay as well as the
set of attributes which could be published along with a product.
If anyone interested I can offer that part of the source code.

regards,
 Florin

> Hi Hans,
>
> Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?
>
> If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 28/01/2010, at 9:32 PM, Hans Bakker wrote:
>
>  
>> Hi follow OFBiz users.
>>
>> as you have seen at the latest commits we have extended the ebay
>> component by using the Ebay API which allows an ofbiz user to (almost)
>> maintain all Ebay functions within OFBiz.
>>
>> Up to now there was no overlap between the existing XML functions and
>> the new API functions, however there now will be.....
>>
>> Uploading products in the existing ebay function does not allow
>> maintaining inventory within in Ebay, but the new upload function does
>> or does not allow it set by a flag, so there is overlap.
>>
>> We plan further to duplicate all XML functions using the API interface.
>>
>> So hereby we propose to rename the existing Ebay component to "EbayXml"
>> and create a new Ebay component called "EbayAPI" both in the specialized
>> directory.
>>
>> comments or suggestions?
>>
>> --
>> Antwebsystems.com: Quality OFBiz services for competitive rates
>>
>>    
>
>  

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

hans_bakker
In reply to this post by Scott Gray-2
Yes Scott I agree with you the names are not good.

We do think however we need both components. For simple stores the
current ebay component can still be interesting.

The main difference is in the functionality, the new component is much
more advanced....

so the name: Ebay Advanced or Ebay professional?

thanks for your reply

Regards,
Hans

On Thu, 2010-01-28 at 21:50 -0700, Scott Gray wrote:

> Hi Hans,
>
> Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?
>
> If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 28/01/2010, at 9:32 PM, Hans Bakker wrote:
>
> > Hi follow OFBiz users.
> >
> > as you have seen at the latest commits we have extended the ebay
> > component by using the Ebay API which allows an ofbiz user to (almost)
> > maintain all Ebay functions within OFBiz.
> >
> > Up to now there was no overlap between the existing XML functions and
> > the new API functions, however there now will be.....
> >
> > Uploading products in the existing ebay function does not allow
> > maintaining inventory within in Ebay, but the new upload function does
> > or does not allow it set by a flag, so there is overlap.
> >
> > We plan further to duplicate all XML functions using the API interface.
> >
> > So hereby we propose to rename the existing Ebay component to "EbayXml"
> > and create a new Ebay component called "EbayAPI" both in the specialized
> > directory.
> >
> > comments or suggestions?
> >
> > --
> > Antwebsystems.com: Quality OFBiz services for competitive rates
> >
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

hans_bakker
In reply to this post by Florin Popa
Please contribute and attach it to an Jira issue! perhaps we can include
it in the Ofbiz distribution? Did you have a lokk what is recently
added?


Regards,
hans

On Fri, 2010-01-29 at 09:45 +0200, Florin Popa wrote:

> Hi,
>
> For our project we developed already most of the Ebay related
> functionalities based on EbayAPI. Indeed there are few particular things
> like the way we keep track of the products sent to ebay as well as the
> set of attributes which could be published along with a product.
> If anyone interested I can offer that part of the source code.
>
> regards,
>  Florin
> > Hi Hans,
> >
> > Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?
> >
> > If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?
> >
> > Regards
> > Scott
> >
> > HotWax Media
> > http://www.hotwaxmedia.com
> >
> > On 28/01/2010, at 9:32 PM, Hans Bakker wrote:
> >
> >  
> >> Hi follow OFBiz users.
> >>
> >> as you have seen at the latest commits we have extended the ebay
> >> component by using the Ebay API which allows an ofbiz user to (almost)
> >> maintain all Ebay functions within OFBiz.
> >>
> >> Up to now there was no overlap between the existing XML functions and
> >> the new API functions, however there now will be.....
> >>
> >> Uploading products in the existing ebay function does not allow
> >> maintaining inventory within in Ebay, but the new upload function does
> >> or does not allow it set by a flag, so there is overlap.
> >>
> >> We plan further to duplicate all XML functions using the API interface.
> >>
> >> So hereby we propose to rename the existing Ebay component to "EbayXml"
> >> and create a new Ebay component called "EbayAPI" both in the specialized
> >> directory.
> >>
> >> comments or suggestions?
> >>
> >> --
> >> Antwebsystems.com: Quality OFBiz services for competitive rates
> >>
> >>    
> >
> >  
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

hans_bakker
In reply to this post by Scott Gray-2
Another suggested name: Ebay Store

On Thu, 2010-01-28 at 21:50 -0700, Scott Gray wrote:

> Hi Hans,
>
> Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?
>
> If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 28/01/2010, at 9:32 PM, Hans Bakker wrote:
>
> > Hi follow OFBiz users.
> >
> > as you have seen at the latest commits we have extended the ebay
> > component by using the Ebay API which allows an ofbiz user to (almost)
> > maintain all Ebay functions within OFBiz.
> >
> > Up to now there was no overlap between the existing XML functions and
> > the new API functions, however there now will be.....
> >
> > Uploading products in the existing ebay function does not allow
> > maintaining inventory within in Ebay, but the new upload function does
> > or does not allow it set by a flag, so there is overlap.
> >
> > We plan further to duplicate all XML functions using the API interface.
> >
> > So hereby we propose to rename the existing Ebay component to "EbayXml"
> > and create a new Ebay component called "EbayAPI" both in the specialized
> > directory.
> >
> > comments or suggestions?
> >
> > --
> > Antwebsystems.com: Quality OFBiz services for competitive rates
> >
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

Florin Popa
In reply to this post by hans_bakker
Did it as https://issues.apache.org/jira/browse/OFBIZ-3435

> Please contribute and attach it to an Jira issue! perhaps we can include
> it in the Ofbiz distribution? Did you have a lokk what is recently
> added?
>
>
> Regards,
> hans
>
> On Fri, 2010-01-29 at 09:45 +0200, Florin Popa wrote:
>  
>> Hi,
>>
>> For our project we developed already most of the Ebay related
>> functionalities based on EbayAPI. Indeed there are few particular things
>> like the way we keep track of the products sent to ebay as well as the
>> set of attributes which could be published along with a product.
>> If anyone interested I can offer that part of the source code.
>>
>> regards,
>>  Florin
>>    
>>> Hi Hans,
>>>
>>> Is there any reason that you know of for us to retain the XML interface at all?  If the "API" is better then shouldn't we just use it alone?
>>>
>>> If we end up keeping both we might need better names, XML vs. API doesn't mean much (I mean the XML interface is also an API) or is this how eBay describes them?
>>>
>>> Regards
>>> Scott
>>>
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> On 28/01/2010, at 9:32 PM, Hans Bakker wrote:
>>>
>>>  
>>>      
>>>> Hi follow OFBiz users.
>>>>
>>>> as you have seen at the latest commits we have extended the ebay
>>>> component by using the Ebay API which allows an ofbiz user to (almost)
>>>> maintain all Ebay functions within OFBiz.
>>>>
>>>> Up to now there was no overlap between the existing XML functions and
>>>> the new API functions, however there now will be.....
>>>>
>>>> Uploading products in the existing ebay function does not allow
>>>> maintaining inventory within in Ebay, but the new upload function does
>>>> or does not allow it set by a flag, so there is overlap.
>>>>
>>>> We plan further to duplicate all XML functions using the API interface.
>>>>
>>>> So hereby we propose to rename the existing Ebay component to "EbayXml"
>>>> and create a new Ebay component called "EbayAPI" both in the specialized
>>>> directory.
>>>>
>>>> comments or suggestions?
>>>>
>>>> --
>>>> Antwebsystems.com: Quality OFBiz services for competitive rates
>>>>
>>>>    
>>>>        
>>>  
>>>      

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

hans_bakker
Excellent thanks we will have a look at it.....

On Fri, 2010-01-29 at 10:40 +0200, Florin Popa wrote:
> https://issues.apache.org/jira/browse/OFBIZ-3435
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: splitup of ebay component.

BJ Freeman
In reply to this post by hans_bakker
when I added to Ebay, I used generic calls that other ofbiz application
could hook into. then at a lower level added my functionality.
By keeping the services at the ofbiz level the same don't have to keep
changing other application, unless they want to use the new functionality.
the also works for backward compatibility.
So the xml or api is transparent to the rest of ofbiz



Hans Bakker sent the following on 1/28/2010 8:32 PM:

> Hi follow OFBiz users.
>
> as you have seen at the latest commits we have extended the ebay
> component by using the Ebay API which allows an ofbiz user to (almost)
> maintain all Ebay functions within OFBiz.
>
> Up to now there was no overlap between the existing XML functions and
> the new API functions, however there now will be.....
>
> Uploading products in the existing ebay function does not allow
> maintaining inventory within in Ebay, but the new upload function does
> or does not allow it set by a flag, so there is overlap.
>
> We plan further to duplicate all XML functions using the API interface.
>
> So hereby we propose to rename the existing Ebay component to "EbayXml"
> and create a new Ebay component called "EbayAPI" both in the specialized
> directory.
>
> comments or suggestions?
>