John, I believe what David was saying was that the reason that the
service name is not in there by default is that, then, in the default
instance, the DHL service would be invoked without proper information.
I ran into the same problem with UPS - and asked the same question, but
it was decided that the demo data would contain information that would
show how these processes work, but would not work for each of the
different carrier options out of the box. It should be spelled out
clearly in the production setup guide - and if it's not - then we should
correct it there.
Any additional thoughts?
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
John Martin wrote:
Hi Dave,
I'm not quite sure what you mean. If you mean that setting the
serviceName to call the API's wouldn't work properly. That is correct
do to the missing access keys but the way that the service (at least
DHL) is written, it will log an error and I believe even display that
shipping properties need to be configured. For someone starting out,
this is already explained in the guide and easy to configure.
If we don't set the serviceName correctly, most new users will have no
means to set the entity attribute. It is not a visible field in the
EditProductStoreShipSetup form.
My recommendation is to set the attribute for all of the carriers.
USPS is prepopulated correctly. I don't see/understand why we
wouldn't do the same for DHL and UPS.
I've included the patch in the jira issue:
https://issues.apache.org/jira/browse/OFBIZ-328
Thanks, John
