[
https://issues.apache.org/jira/browse/OFBIZ-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350018#comment-14350018 ]
Wai commented on OFBIZ-5949:
----------------------------
To answer your previous question, "...OOTB there are no "NEXT_DAY_AIR"..."
You are correct. That data is not loaded via any of the readers (seed,seed-initial,ext,...).
The "NEXT_DAY_AIR" data is located in applications/commonext/data/ShippingData.xml
The contents of this file is loaded during the creation of the product store when the simple method commonext/script/org/ofbiz/setup/SetupEvents.xml#createProductStoreWithDefaultSetting is called.
That explains why you would not be able to locate the corresponding entries containing "NEXT_DAY_AIR" during a fresh install. But once you create your first product store. The data in question will be initialized in the database.
> ofbizsetup create product store cause exception, remove use of temp file to load entity data
> --------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5949
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5949> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: Wai
> Assignee: Jacques Le Roux
> Attachments: OFBIZ-5949.patch
>
>
> The exception is caused by foreign key constraint violation between ShipmentCostEstimate and CarrierShipmentMethod entities.
> Currently, when creating a new product store using ofbizsetup component default data associated with the product store is loaded into the database using the following steps.
> 1. read default data from entity xml file and replace specific items in the read data and write to temp file.
> 2. use service=parseEntityXmlFile to load the processed file into database.
> The issue with this method is that the temp file can present a problem when ofbiz is operating in multitenant mode.
> The solution is to modify the relevant services so that no temp file needs generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)