Maybe even easier, keep the specific log on a reasonnable period. Then remove duplicate log lines and fix in code. This will not
ensure no points are missing but it should help
Jacques
From: "Jacques Le Roux" <[EMAIL PROTECTED]>
Yes, I suggested to create a separate log for that (easier) and to check it
daily on the demo server
Jacques
From: "Adrian Crum" <[EMAIL PROTECTED]>
We could add a warning message to the EntityCondition classes (like the one on line 411 of GenericEntity.java), then start
checking the logs for the warning messages.
-Adrian
Scott Gray wrote:
Thanks Adrian, I understand the implications now.
So what's the next step, should we add type checking to the
EntityConditions and then perhaps only enforce the correct types on
some volunteer machines until we can fix a good portion of the problem
code and then move it to the trunk?
Regards
Scott
2008/10/15 Adrian Crum <[EMAIL PROTECTED]>:
Scott Gray wrote:
Ok it makes more sense to me now, conversion needs to take place at a
level where the relevant information is still available so doing it on
a low level isn't really an option (even though that's been allowed to
happen up until now). I guess I was having trouble understanding why
we needed to do all this work when everything had been running fine,
but I see now that it wasn't really running that fine.
To be precise, some things in OFBiz have not been running fine since
September 2006 - https://issues.apache.org/jira/browse/OFBIZ-221.
-Adrian
