[ 
https://issues.apache.org/jira/browse/OFBIZ-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814965#comment-13814965
 ] 

Christian Carlow commented on OFBIZ-5389:
-----------------------------------------

My assumptions in the previous post were incorrect.  The 
loadType2ProductInProductDimension eca action isn't what causes the product 
cache to update.  It appears to get updated in the "updateProduct" 
simple-method when store-value is called.

Does anyone know if minilang store-value contains logic that updates cache that 
is excluded in create-value?  

This is the only eeca I found for Product when being stored:
    <eca entity="Product" operation="store" event="return">
        <condition field-name="autoCreateKeywords" operator="not-equals" 
value="N"/>
        <action service="indexProductKeywords" mode="sync"/>
    </eca>

I cleared all the logic from "indexProductKeywords" simple-method and product 
was still found so it seem to be something within store-value.

> Error adding newly created virtual product to purchase order
> ------------------------------------------------------------
>
>                 Key: OFBIZ-5389
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5389
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: SVN trunk
>            Reporter: Christian Carlow
>         Attachments: ProductServices.java.diff
>
>
> A "Problems getting the product entity" error occurs when adding a newly 
> created "Variant Tree Generation" virtual product is added to a purchase 
> order.  
> The feature selections are not rendered because the variant products list is 
> created from cache in which the newly created product hasn't yet been added.
> Cache searches seem somewhat ubiquitous throughout the purchase orders.  Does 
> anyone know if this was intentional for some reason which would require the 
> user to clear cache before the new products register for use?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to