Re: ebay componet createShoppingCart

[BJ Freeman]

ok moved to dev list.
not so much as ebay but general external flow to get to a ProductStore.
if you are using an external website or interface, I would think it
proper to use the Website entity. This way the UI can be used to
construct which product store to use.
So what ever the external string is that Identifies the website would be
the websiteID.




Jacques Le Roux sent the following on 8/4/2008 3:25 AM:

> Hi BJ,
>
> I know, well... nothing... about ebay in OFBiz (sorry for that). Could
> you elaborate a bit more, please ? BTW should not be in dev ML ?
>
> Jacques
>
> From: "BJ Freeman" <[hidden email]>
>> I anyone have an objection to adding in the website to find the
>> productstoreID.
>>
>
>
>
>

[BJ Freeman]

oh and this would move some of the configuration data from properties to
the website entity.

BJ Freeman sent the following on 8/4/2008 3:42 AM:

> ok moved to dev list.
> not so much as ebay but general external flow to get to a ProductStore.
> if you are using an external website or interface, I would think it
> proper to use the Website entity. This way the UI can be used to
> construct which product store to use.
> So what ever the external string is that Identifies the website would be
> the websiteID.
>
>
>
>
> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>> Hi BJ,
>>
>> I know, well... nothing... about ebay in OFBiz (sorry for that). Could
>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>
>> Jacques
>>
>> From: "BJ Freeman" <[hidden email]>
>>> I anyone have an objection to adding in the website to find the
>>> productstoreID.
>>>
>>
>>
>>
>
>
>
>

[Jacques Le Roux]

Hi BJ,

I don't want to be rude, but it's sometimes really difficult to follow you. I'm sure you got an idea but please when I ask for more
information try to be less cryptic.

Could you explain in details what mean the 2 posts below. For instance
>> if you are using an external website or interface, I would think it
>> proper to use the Website entity. This way the UI can be used to
>> construct which product store to use.

I suppose you speak about the external application and it's UI, but not sure...

>> So what ever the external string is that Identifies the website would be
>> the websiteID.

No it's clearer, it's about the link between theexternal appli and OFBiz. But how is this in relation with OFBiz developement or
general use ? What do you try to communicate ? What is the goal to speak about that with us ?

> oh and this would move some of the configuration data from properties to
> the website entity.

What configuration data ? Is this intented to be generalised ? If so you need to bring us much more details. We are not reading on
your lips and even less in your mind ;o)

Thanks

Jacques

From: "BJ Freeman" <[hidden email]>

> oh and this would move some of the configuration data from properties to
> the website entity.
>
> BJ Freeman sent the following on 8/4/2008 3:42 AM:
>> ok moved to dev list.
>> not so much as ebay but general external flow to get to a ProductStore.
>> if you are using an external website or interface, I would think it
>> proper to use the Website entity. This way the UI can be used to
>> construct which product store to use.
>> So what ever the external string is that Identifies the website would be
>> the websiteID.
>>
>>
>>
>>
>> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>>> Hi BJ,
>>>
>>> I know, well... nothing... about ebay in OFBiz (sorry for that). Could
>>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>>
>>> Jacques
>>>
>>> From: "BJ Freeman" <[hidden email]>
>>>> I anyone have an objection to adding in the website to find the
>>>> productstoreID.
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>

[BJ Freeman]

my bad. It is the way I think.
let me try to make this clearer.
code that interacts with external websites or webservices, for sake of
better description, that are components, need someway to link that
website, or webservice to ofbiz.
in the case of ebay you have the sandbox and production  urls.

Typically for embedded webservices like UPS, this does not apply.
you also per ebay "site" have siteID token that would be used as the
websiteID.

Now for push and pull types like ebay this is not a real big thing,
however there are, like yahoo, realtime data that is sent or requested
where this is very important.

in getting orders from ebay
        List orders = readResponseFromEbay(response, locale,
(String)context.get("productStoreId"), delegator, errorMessage);
the ProductStoreID is used.
I am saying this should be a Website entity websiteID
so there is more flexibility to assign or change the productstore
assigned to a site.
the ProductStoreID can be gotten from the WebsiteID, which can be
maintained thru the UI.

The reason I suggest this as a best practices, is it allow allow content
to come into play for publishing to an external website, Like the format
(datafile) to export information, instead of being hard coded, or
sending pages to a website(not yet implemented, but in the planning stage).

This would also allow many website to be connected to a productStore, if
the user wished to have them that way.

There can be an association made for extra website data from the website
 entity. allowing data we put in properties to be stored and maybe even
encrypted.

hope this is clearer.



Jacques Le Roux sent the following on 8/4/2008 1:41 PM:

> Hi BJ,
>
> I don't want to be rude, but it's sometimes really difficult to follow
> you. I'm sure you got an idea but please when I ask for more
> information try to be less cryptic.
>
> Could you explain in details what mean the 2 posts below. For instance
>>> if you are using an external website or interface, I would think it
>>> proper to use the Website entity. This way the UI can be used to
>>> construct which product store to use.
>
> I suppose you speak about the external application and it's UI, but not
> sure...
>
>>> So what ever the external string is that Identifies the website would be
>>> the websiteID.
>
> No it's clearer, it's about the link between theexternal appli and
> OFBiz. But how is this in relation with OFBiz developement or
> general use ? What do you try to communicate ? What is the goal to speak
> about that with us ?
>
>> oh and this would move some of the configuration data from properties to
>> the website entity.
>
> What configuration data ? Is this intented to be generalised ? If so you
> need to bring us much more details. We are not reading on
> your lips and even less in your mind ;o)
>
> Thanks
>
> Jacques
>
> From: "BJ Freeman" <[hidden email]>
>> oh and this would move some of the configuration data from properties to
>> the website entity.
>>
>> BJ Freeman sent the following on 8/4/2008 3:42 AM:
>>> ok moved to dev list.
>>> not so much as ebay but general external flow to get to a ProductStore.
>>> if you are using an external website or interface, I would think it
>>> proper to use the Website entity. This way the UI can be used to
>>> construct which product store to use.
>>> So what ever the external string is that Identifies the website would be
>>> the websiteID.
>>>
>>>
>>>
>>>
>>> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>>>> Hi BJ,
>>>>
>>>> I know, well... nothing... about ebay in OFBiz (sorry for that). Could
>>>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>>>
>>>> Jacques
>>>>
>>>> From: "BJ Freeman" <[hidden email]>
>>>>> I anyone have an objection to adding in the website to find the
>>>>> productstoreID.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>

[Jacques Le Roux]

From: "BJ Freeman" <[hidden email]>

> my bad. It is the way I think.
> let me try to make this clearer.
> code that interacts with external websites or webservices, for sake of
> better description, that are components, need someway to link that
> website, or webservice to ofbiz.
> in the case of ebay you have the sandbox and production  urls.
>
> Typically for embedded webservices like UPS, this does not apply.
> you also per ebay "site" have siteID token that would be used as the
> websiteID.
>
> Now for push and pull types like ebay this is not a real big thing,
> however there are, like yahoo, realtime data that is sent or requested
> where this is very important.
>
> in getting orders from ebay
>        List orders = readResponseFromEbay(response, locale,
> (String)context.get("productStoreId"), delegator, errorMessage);
> the ProductStoreID is used.
> I am saying this should be a Website entity websiteID
> so there is more flexibility to assign or change the productstore
> assigned to a site.
> the ProductStoreID can be gotten from the WebsiteID, which can be
> maintained thru the UI.

Ha, now I see. I did not look into details, but from the top of my head ProductStore and WebSite are related hence you should be
able to do what you what in a side or the other. So where is the problem ?

> The reason I suggest this as a best practices, is it allow allow content
> to come into play for publishing to an external website, Like the format
> (datafile) to export information, instead of being hard coded,

Where is the format (datafile) to export information hardcoded ?

> sending pages to a website(not yet implemented, but in the planning stage).
>
> This would also allow many website to be connected to a productStore, if
> the user wished to have them that way.

But is this not yet possible ? https://localhost:8443/catalog/control/EditProductStoreWebSites?viewProductStoreId=9000

> There can be an association made for extra website data from the website
> entity. allowing data we put in properties to be stored and maybe even
> encrypted.

Can't you add an external Web site type and deal with it in the screen above and i other code needed (like createShoppingCart) ?

Jacques

> hope this is clearer.
>
>
>
> Jacques Le Roux sent the following on 8/4/2008 1:41 PM:
>> Hi BJ,
>>
>> I don't want to be rude, but it's sometimes really difficult to follow
>> you. I'm sure you got an idea but please when I ask for more
>> information try to be less cryptic.
>>
>> Could you explain in details what mean the 2 posts below. For instance
>>>> if you are using an external website or interface, I would think it
>>>> proper to use the Website entity. This way the UI can be used to
>>>> construct which product store to use.
>>
>> I suppose you speak about the external application and it's UI, but not
>> sure...
>>
>>>> So what ever the external string is that Identifies the website would be
>>>> the websiteID.
>>
>> No it's clearer, it's about the link between theexternal appli and
>> OFBiz. But how is this in relation with OFBiz developement or
>> general use ? What do you try to communicate ? What is the goal to speak
>> about that with us ?
>>
>>> oh and this would move some of the configuration data from properties to
>>> the website entity.
>>
>> What configuration data ? Is this intented to be generalised ? If so you
>> need to bring us much more details. We are not reading on
>> your lips and even less in your mind ;o)
>>
>> Thanks
>>
>> Jacques
>>
>> From: "BJ Freeman" <[hidden email]>
>>> oh and this would move some of the configuration data from properties to
>>> the website entity.
>>>
>>> BJ Freeman sent the following on 8/4/2008 3:42 AM:
>>>> ok moved to dev list.
>>>> not so much as ebay but general external flow to get to a ProductStore.
>>>> if you are using an external website or interface, I would think it
>>>> proper to use the Website entity. This way the UI can be used to
>>>> construct which product store to use.
>>>> So what ever the external string is that Identifies the website would be
>>>> the websiteID.
>>>>
>>>>
>>>>
>>>>
>>>> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>>>>> Hi BJ,
>>>>>
>>>>> I know, well... nothing... about ebay in OFBiz (sorry for that). Could
>>>>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>>>>
>>>>> Jacques
>>>>>
>>>>> From: "BJ Freeman" <[hidden email]>
>>>>>> I anyone have an objection to adding in the website to find the
>>>>>> productstoreID.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>

[BJ Freeman]

Jacques Le Roux sent the following on 8/9/2008 11:27 AM:

> From: "BJ Freeman" <[hidden email]>
>> my bad. It is the way I think.
>> let me try to make this clearer.
>> code that interacts with external websites or webservices, for sake of
>> better description, that are components, need someway to link that
>> website, or webservice to ofbiz.
>> in the case of ebay you have the sandbox and production  urls.
>>
>> Typically for embedded webservices like UPS, this does not apply.
>> you also per ebay "site" have siteID token that would be used as the
>> websiteID.
>>
>> Now for push and pull types like ebay this is not a real big thing,
>> however there are, like yahoo, realtime data that is sent or requested
>> where this is very important.
>>
>> in getting orders from ebay
>>        List orders = readResponseFromEbay(response, locale,
>> (String)context.get("productStoreId"), delegator, errorMessage);
>> the ProductStoreID is used.
>> I am saying this should be a Website entity websiteID
>> so there is more flexibility to assign or change the productstore
>> assigned to a site.
>> the ProductStoreID can be gotten from the WebsiteID, which can be
>> maintained thru the UI.
>
> Ha, now I see. I did not look into details, but from the top of my head
> ProductStore and WebSite are related hence you should be able to do what
> you what in a side or the other. So where is the problem ?
>

I am trying to set a best practices for the work I am doing.

>> The reason I suggest this as a best practices, is it allow allow content
>> to come into play for publishing to an external website, Like the format
>> (datafile) to export information, instead of being hard coded,
>
> Where is the format (datafile) to export information hardcoded ?
Not done yet, in my head.
for instance you have a website Z and it takes FTP upload of Y format.
so using the content component, this can be defined.
Yes there are more entities to consider and code.
it is a future thing but want to leave a hook so it can be done.
>
>> sending pages to a website(not yet implemented, but in the planning
>> stage).
>>
>> This would also allow many website to be connected to a productStore, if
>> the user wished to have them that way.
>
> But is this not yet possible ?
> https://localhost:8443/catalog/control/EditProductStoreWebSites?viewProductStoreId=9000
Click on websites
https://localhost:8443/catalog/control/EditProductStoreWebSites?viewProductStoreId=9000
see
https://issues.apache.org/jira/browse/OFBIZ-1899
>
>
>> There can be an association made for extra website data from the website
>> entity. allowing data we put in properties to be stored and maybe even
>> encrypted.
>
> Can't you add an external Web site type and deal with it in the screen
> above and i other code needed (like createShoppingCart) ?
yes there is a lot of other coded needed but this is the foundation so
the code can be done.
this is how I handle the yahoo interface where a store owner an have
many websites (stores) and setup them up thru the
websites->productstores using the UI.

>
> Jacques
>
>
>> hope this is clearer.
>>
>>
>>
>> Jacques Le Roux sent the following on 8/4/2008 1:41 PM:
>>> Hi BJ,
>>>
>>> I don't want to be rude, but it's sometimes really difficult to follow
>>> you. I'm sure you got an idea but please when I ask for more
>>> information try to be less cryptic.
>>>
>>> Could you explain in details what mean the 2 posts below. For instance
>>>>> if you are using an external website or interface, I would think it
>>>>> proper to use the Website entity. This way the UI can be used to
>>>>> construct which product store to use.
>>>
>>> I suppose you speak about the external application and it's UI, but not
>>> sure...
>>>
>>>>> So what ever the external string is that Identifies the website
>>>>> would be
>>>>> the websiteID.
>>>
>>> No it's clearer, it's about the link between theexternal appli and
>>> OFBiz. But how is this in relation with OFBiz developement or
>>> general use ? What do you try to communicate ? What is the goal to speak
>>> about that with us ?
>>>
>>>> oh and this would move some of the configuration data from
>>>> properties to
>>>> the website entity.
>>>
>>> What configuration data ? Is this intented to be generalised ? If so you
>>> need to bring us much more details. We are not reading on
>>> your lips and even less in your mind ;o)
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>>> From: "BJ Freeman" <[hidden email]>
>>>> oh and this would move some of the configuration data from
>>>> properties to
>>>> the website entity.
>>>>
>>>> BJ Freeman sent the following on 8/4/2008 3:42 AM:
>>>>> ok moved to dev list.
>>>>> not so much as ebay but general external flow to get to a
>>>>> ProductStore.
>>>>> if you are using an external website or interface, I would think it
>>>>> proper to use the Website entity. This way the UI can be used to
>>>>> construct which product store to use.
>>>>> So what ever the external string is that Identifies the website
>>>>> would be
>>>>> the websiteID.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>>>>>> Hi BJ,
>>>>>>
>>>>>> I know, well... nothing... about ebay in OFBiz (sorry for that).
>>>>>> Could
>>>>>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>> From: "BJ Freeman" <[hidden email]>
>>>>>>> I anyone have an objection to adding in the website to find the
>>>>>>> productstoreID.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>

[Jacques Le Roux]

Ha yes, I have already read some lines in OFBIZ-1899, I see now.

Jacques

> Jacques Le Roux sent the following on 8/9/2008 11:27 AM:
>> From: "BJ Freeman" <[hidden email]>
>>> my bad. It is the way I think.
>>> let me try to make this clearer.
>>> code that interacts with external websites or webservices, for sake of
>>> better description, that are components, need someway to link that
>>> website, or webservice to ofbiz.
>>> in the case of ebay you have the sandbox and production  urls.
>>>
>>> Typically for embedded webservices like UPS, this does not apply.
>>> you also per ebay "site" have siteID token that would be used as the
>>> websiteID.
>>>
>>> Now for push and pull types like ebay this is not a real big thing,
>>> however there are, like yahoo, realtime data that is sent or requested
>>> where this is very important.
>>>
>>> in getting orders from ebay
>>>        List orders = readResponseFromEbay(response, locale,
>>> (String)context.get("productStoreId"), delegator, errorMessage);
>>> the ProductStoreID is used.
>>> I am saying this should be a Website entity websiteID
>>> so there is more flexibility to assign or change the productstore
>>> assigned to a site.
>>> the ProductStoreID can be gotten from the WebsiteID, which can be
>>> maintained thru the UI.
>>
>> Ha, now I see. I did not look into details, but from the top of my head
>> ProductStore and WebSite are related hence you should be able to do what
>> you what in a side or the other. So where is the problem ?
>>
> I am trying to set a best practices for the work I am doing.
>
>>> The reason I suggest this as a best practices, is it allow allow content
>>> to come into play for publishing to an external website, Like the format
>>> (datafile) to export information, instead of being hard coded,
>>
>> Where is the format (datafile) to export information hardcoded ?
> Not done yet, in my head.
> for instance you have a website Z and it takes FTP upload of Y format.
> so using the content component, this can be defined.
> Yes there are more entities to consider and code.
> it is a future thing but want to leave a hook so it can be done.
>>
>>> sending pages to a website(not yet implemented, but in the planning
>>> stage).
>>>
>>> This would also allow many website to be connected to a productStore, if
>>> the user wished to have them that way.
>>
>> But is this not yet possible ?
>> https://localhost:8443/catalog/control/EditProductStoreWebSites?viewProductStoreId=9000
> Click on websites
> https://localhost:8443/catalog/control/EditProductStoreWebSites?viewProductStoreId=9000
> see
> https://issues.apache.org/jira/browse/OFBIZ-1899
>>
>>
>>> There can be an association made for extra website data from the website
>>> entity. allowing data we put in properties to be stored and maybe even
>>> encrypted.
>>
>> Can't you add an external Web site type and deal with it in the screen
>> above and i other code needed (like createShoppingCart) ?
> yes there is a lot of other coded needed but this is the foundation so
> the code can be done.
> this is how I handle the yahoo interface where a store owner an have
> many websites (stores) and setup them up thru the
> websites->productstores using the UI.
>
>>
>> Jacques
>>
>>
>>> hope this is clearer.
>>>
>>>
>>>
>>> Jacques Le Roux sent the following on 8/4/2008 1:41 PM:
>>>> Hi BJ,
>>>>
>>>> I don't want to be rude, but it's sometimes really difficult to follow
>>>> you. I'm sure you got an idea but please when I ask for more
>>>> information try to be less cryptic.
>>>>
>>>> Could you explain in details what mean the 2 posts below. For instance
>>>>>> if you are using an external website or interface, I would think it
>>>>>> proper to use the Website entity. This way the UI can be used to
>>>>>> construct which product store to use.
>>>>
>>>> I suppose you speak about the external application and it's UI, but not
>>>> sure...
>>>>
>>>>>> So what ever the external string is that Identifies the website
>>>>>> would be
>>>>>> the websiteID.
>>>>
>>>> No it's clearer, it's about the link between theexternal appli and
>>>> OFBiz. But how is this in relation with OFBiz developement or
>>>> general use ? What do you try to communicate ? What is the goal to speak
>>>> about that with us ?
>>>>
>>>>> oh and this would move some of the configuration data from
>>>>> properties to
>>>>> the website entity.
>>>>
>>>> What configuration data ? Is this intented to be generalised ? If so you
>>>> need to bring us much more details. We are not reading on
>>>> your lips and even less in your mind ;o)
>>>>
>>>> Thanks
>>>>
>>>> Jacques
>>>>
>>>> From: "BJ Freeman" <[hidden email]>
>>>>> oh and this would move some of the configuration data from
>>>>> properties to
>>>>> the website entity.
>>>>>
>>>>> BJ Freeman sent the following on 8/4/2008 3:42 AM:
>>>>>> ok moved to dev list.
>>>>>> not so much as ebay but general external flow to get to a
>>>>>> ProductStore.
>>>>>> if you are using an external website or interface, I would think it
>>>>>> proper to use the Website entity. This way the UI can be used to
>>>>>> construct which product store to use.
>>>>>> So what ever the external string is that Identifies the website
>>>>>> would be
>>>>>> the websiteID.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jacques Le Roux sent the following on 8/4/2008 3:25 AM:
>>>>>>> Hi BJ,
>>>>>>>
>>>>>>> I know, well... nothing... about ebay in OFBiz (sorry for that).
>>>>>>> Could
>>>>>>> you elaborate a bit more, please ? BTW should not be in dev ML ?
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>> From: "BJ Freeman" <[hidden email]>
>>>>>>>> I anyone have an objection to adding in the website to find the
>>>>>>>> productstoreID.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>