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

Bob Morley commented on OFBIZ-3700:
-----------------------------------

Adrian -- I am working through a production run and ran into a slight glitch 
related to this.  The ProductionRun class has a quantity on it defined as a 
BigDecimal.  In the store() method on this class, it uses this to set the value 
on the WorkEffortGoodStandard.  In our source, this entities 
"estimatedQuantity" field is a java double which causes a big fat stack trace 
(but does do the conversion).  My hope is you will include 
WorkEffortGoodStandard in your conversion efforts.

Also -- take a look at getProductProduced which figures out how many products 
will be produced for this production run (by getting the WorkEffortGoodStandard 
product to be delivered).  This qty is originally set in createProductionRun by 
the production run's desired quantity.  However, when store() is called it does 
not update the qty on the ProductionRun -- just the underlying 
WorkEffortGoodStandard value.  It seems to me we should consider having it 
update the ProductionRun's work effort "quantityToProduce" as well.

> Convert WorkEffort (and related entities) quantities from Double -> BigDecimal
> ------------------------------------------------------------------------------
>
>                 Key: OFBIZ-3700
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3700
>             Project: OFBiz
>          Issue Type: Bug
>          Components: workeffort
>    Affects Versions: SVN trunk
>            Reporter: Bob Morley
>            Assignee: Adrian Crum
>            Priority: Minor
>             Fix For: SVN trunk
>
>
> It appears that this entity was missed from the BigDecimal conversion.  Ran 
> into this when ProductionRunServices was attempting to create a WorkEffort 
> (it is passing the quantity to produce as a BigDecimal).  A different bug in 
> OFBIZ-3699 was causing an auto-convert of the field from BigDecimal to Double 
> (which was allowing ProductionRuns to be created).  At any rate, we should 
> convert this entity and any other quantity related entities in the WorkEffort 
> component.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to