BJ: when there is an error, the control servlet looks for an error path in <param-name>allowedPaths</param-name>
it does not find one throwing an exception which buries the orginal error.
instead of changing the code it is just easier to add the /error: path.
then the real error gets reported correctly.
JLR: This will maybe help to better understand some errors on demo servers, and can't hurt
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@954135 13f79535-47bb-0310-9956-ffa450edef68
<copyright>Copyright 2001-.* The Apache Software Foundation</copyright>
<copyright><year>.*</year><holder>Apache Foundation</holder></copyright>
<copyright><year>.*</year><holder>Apache Foundation.</holder></copyright>
<owner>Copyright 2001-.* The Apache Software Foundation</owner>
Less to update every year!
Thanks to BJ 1st effort at "update files from 2009 to 2010" (https://issues.apache.org/jira/browse/OFBIZ-3783) - OFBIZ-3783
Note: there are been a lot of efforts in 2009: there are plenty of data dated from this year!
I hope I did not broke anything (should not, but of course I did not try all changes...) Anyway, this can be easily reverted...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@948846 13f79535-47bb-0310-9956-ffa450edef68
certain other things. Earlier this service was returning an empty map for a purchase order and a vendor return. On order detail page action
block there is a check on this map and if the map comes out to be empty the system does not show the options to create return for the
purchase order. Similary if you create a vendor return directly from the Return Header screen and try to add items on the Return Item screen
using an order Id, this display a message "No returnable items found for order"
Also the method sendItemsShipped in the service sendGoogleShipRequest was throwing a NPE because the code try to pull a product through
ItemIssuance > OrderItem > Product
In the vendor return of type refund the items are issued to the return shipment and a purchase return invoice is generated and hence the process
is not linked to any Order. Adding a condition on the ECA so that this service is not invoked.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@940851 13f79535-47bb-0310-9956-ffa450edef68
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/specialpurpose@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/specialpurpose@832680 13f79535-47bb-0310-9956-ffa450edef68
I saw five +1 vote on thread "Proposal for change in entity "GoogleCoShippingMethod"" and considering that this entity was recently introduced so this change will not create any problem.
Thanks Pranay for raising this issue as a proposal infront of community.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@820993 13f79535-47bb-0310-9956-ffa450edef68
I was planning to wait longer, but I can't wait more. I have added a lot of small trivial changes in this patch and they are blocking me to go further on other issues...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@813307 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/specialpurpose@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/specialpurpose@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/specialpurpose@780153 13f79535-47bb-0310-9956-ffa450edef68