Following points are covered in this implementation:
1) Send item shipped request from OFBiz to Google in a collection instead of sending multiple request for each item shipped.
2) Also show limitation messages for Google orders, while updating manual adjustments from order detail page.
Thanks Pranay / Arun for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@834385 13f79535-47bb-0310-9956-ffa450edef68
When we creates return for orders placed through Google Checkout then correct refunded amount does not go to Google Checkout.
Thanks Pranay / Arun for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@832680 13f79535-47bb-0310-9956-ffa450edef68
Reported by Hans on Dev mailing list. Thanks Hans.
There are two reason of choosing "Co" pattern for the entities.
1) I haven't seen any such pattern in OFBiz to define entity in which you have three or more capital letter coming in b/w.
Like for General Ledger, GlAccount is used OOTB.
2) In database it will split the table name to Google_C_O_Shipping_Method if we keep the name GoogleCOShippingMethod.
So it looks like you have some new word starting with "C" and another new word starting with "O"
But if we keep the name GoogleCoShippingMethod then it will split the name into "Google_Co_Shipping_Method"
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@781689 13f79535-47bb-0310-9956-ffa450edef68
1) Added the UI's for the configuration entities introduced in previous commit.
This will help to avoid the restarting of server. (Previously values were maintained in the property files)
2) Renamed those two configuration entities to more closely follow the GoogleCheckout naming pattern.
The idea behind renaming of entity is that in future we can have other feature coming from Google so at that time GoogleConfiguration entity will be bit confusing.IMO this entities are introduced before few days(1 or 2 days) and I am sure no one is using these entities in Production so we will be safe by this change in the initial phase of google checkout.
Thanks to myself :)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@780501 13f79535-47bb-0310-9956-ffa450edef68
2. enhanced the create order code
3. finished implementation of cancel, capture and ship notifications (Order Processing API to Google)
4. implemented order state change notification
5. added place holders for other notification messages
6. added controller event for processing incoming messages (/googlecheckout/control/handleMessage)
7. added new entity to map shipping methods to support w/ google and link them to internal shipping methods
8. added ecas to prevent certain order changes which cannot be support by Google (adding items, changng quanities)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@780153 13f79535-47bb-0310-9956-ffa450edef68
For using this feature you may need to create Merchant Account in the Google Checkout area.
We can disable this links if anyone think otherwise but the idea of keeping these links on ecommerce is that the End User knows that this feature also exists in OFBiz and could use it accordingly.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@779910 13f79535-47bb-0310-9956-ffa450edef68
For more details please have a look on the jira issue: OFBIZ-2545 (Create Order and Party information using google notification)
This is collaborative effort from Andrew Zeneski, Vivek Mishra, Arun Patidar, Anurag Singh Sengar & Me.
Thanks guys for giving a good head start to this feature.
More exciting features are coming soon in this area, so please stay tuned.
Thanks !
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@779907 13f79535-47bb-0310-9956-ffa450edef68
For more details please see jira issue: OFBIZ-2538 (Create a service to establish a connection with Google Checkout server)
Thanks Anurag for your contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@779514 13f79535-47bb-0310-9956-ffa450edef68