[
https://issues.apache.org/jira/browse/OFBIZ-11955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182330#comment-17182330
]
Jacques Le Roux commented on OFBIZ-11955:
-----------------------------------------
bq. it gives quite a few depreciation warnings with openjdk 11
For now we only support Java 9
bq. in your pictures, i can't see micro widget 3, that should have been loaded
from the xml.
As explained I loaded the file using webtools/import. It loaded 73 entities.
All that depend on the file content and seems consistent if you count the lins
in the files after removing the ASL2 header and some wrapped lines, like
{noformat}
<InventoryItem facilityId="WebStoreWarehouse" locationSeqId="TLTLTLUL03"
datetimeReceived="2008-08-01 08:00:00.000"
inventoryItemId="9004"
inventoryItemTypeId="NON_SERIAL_INV_ITEM" productId="WG3-1111"
ownerPartyId="Company" currencyUomId="USD" unitCost="4.5"/>
<InventoryItem facilityId="WebStoreWarehouse" locationSeqId="TLTLTLLL03"
datetimeReceived="2008-08-01 08:00:00.000"
inventoryItemId="9005"
inventoryItemTypeId="NON_SERIAL_INV_ITEM" productId="WG3-1111"
ownerPartyId="Company" currencyUomId="USD" unitCost="4.5"/>
{noformat}
You may check yourself. Are you sure of your DB content? Else try with another
set. If you use Derby you can save the DB at runtime\data\derby somewhere else
and create a new fresh one using gradlew loadAll, and then import your own
data...
> display/selection of unit of measure is broken
> ----------------------------------------------
>
> Key: OFBIZ-11955
> URL: https://issues.apache.org/jira/browse/OFBIZ-11955
> Project: OFBiz
> Issue Type: Bug
> Components: ecommerce, order
> Affects Versions: Release Branch 17.12, Trunk
> Reporter: Alex Bodnaru
> Priority: Major
> Attachments: Image 002.png, Image 002.png, Image damned.png,
> Image1.png, image-2020-08-22-13-00-44-947.png,
> image-2020-08-22-13-00-57-856.png, image-2020-08-22-13-03-22-775.png,
> image-2020-08-22-13-04-07-722.png, variantinfojs-data.xml
>
>
> checkAmtReq and getVariantPrice are broken for similar reasons, too.
> the display and selection of alternative uom elements occur in multiple
> forms, one for each product: whether detailed or in summary. thus, they
> should be marked by names and classes, not by ids, that are unique in the
> entire document.
> the bug did not manifest in demo data, since only one product has alternative
> packaging.
> i did duplicate wg-1111* products and arranged their relations. is, btw, a
> way to export product trees in order to share them?
> the fix does span the framework and ecommerce repositories.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
