Hi Jacopo,

Yes I think so. I'm not quite sure, but I saw an error like that while tracking 
another (not related) issue that finally David fixed
at r915644. This error spoke about an Id not a fromDate that David fixed. But I just can't reproduce it (I can't remember how I got it). I never saw that before

Jacques

From: "Jacopo Cappellato" <jacopo.cappell...@hotwaxmedia.com>
If you go here:

https://localhost:8443/manufacturing/control/EditCalendarWeek?calendarWeekId=DEFAULT

and try to update the values on the screen you get the following error in the 
log:

=-=-=-=-=-=-=-=-= Database type warning GenericEntity.set =-=-=-=-=-=-=-=-= In 
entity field [TechDataCalendarWeek.mondayCapacity]
set the value passed in [java.math.BigDecimal] is not compatible with the Java 
type of the field [Double]
Exception: java.lang.Exception
Message: Location of database type warning
---- stack trace ---------------------------------------------------------------
java.lang.Exception: Location of database type warning
org.ofbiz.entity.GenericEntity.set(GenericEntity.java:422)
org.ofbiz.entity.GenericEntity.set(GenericEntity.java:368)
org.ofbiz.entity.GenericEntity.setAllFields(GenericEntity.java:885)
org.ofbiz.entity.GenericEntity.setNonPKFields(GenericEntity.java:841)
org.ofbiz.minilang.method.entityops.SetNonpkFields.exec(SetNonpkFields.java:81)
org.ofbiz.minilang.SimpleMethod.runSubOps(SimpleMethod.java:920)
org.ofbiz.minilang.SimpleMethod.exec(SimpleMethod.java:739)
org.ofbiz.minilang.SimpleMethod.runSimpleMethod(SimpleMethod.java:160)
org.ofbiz.minilang.SimpleMethod.runSimpleService(SimpleMethod.java:142)
org.ofbiz.minilang.SimpleServiceEngine.serviceInvoker(SimpleServiceEngine.java:78)
org.ofbiz.minilang.SimpleServiceEngine.runSync(SimpleServiceEngine.java:53)
org.ofbiz.service.ModelServiceReader$GenericInvokerImpl.runSync(ModelServiceReader.java:747)
applications.manufacturing.servicedef.services_95$calendar_46$xml_35$updateCalendarWeek.runSync(file:applications/manufacturing/servicedef/services_calendar.xml#updateCalendarWeek:68)

Is it possible it is caused by recent changes to the conversion framework?

Thanks

Jacopo



Reply via email to