On Oct 25, 2007, at 5:16 PM, Adrian Crum wrote:
Andrew,I understand what the method does. The point I'm trying to make is this: It is not needed and it provides a way to introduce inconsistent data into the project.I understand the method solves a problem for a particular client, but it's not a good thing to include in the project.There is a discussion on Jira about this: https://issues.apache.org/jira/browse/OFBIZ-1361
Yes, and Adrian you seem to have missed my point there, or maybe you disagree with me?
The framework is NOT around to force stuff. Here is what I wrote there: ===================================================While I agree that this should be the best practice, there is a big difference in the framework between what we "allow" and what we "recommend".
There is lots of stuff you _can_ do with the framework that is really not a good idea, thought some might disagree. Things that we recommend should be documented in the Best Practices Guide. Other things we don't want to make more difficult, IMO, that this is important because of the comment about disagreement above. There are pretty much always good reasons why we do things the way we recommend in the framework, but those recommendations have evolved over time and will continue to evolve as well, and not allowing things we don't recommend stifles this and limits opportunity to progress and improve.
That is of course a generality, and there is a clear best practice here that should be documented and it probably won't ever change, but I'm still against forcing on a matter of principle.
===================================================If you have an issue with that, let's discuss that directly, and if necessary vote on it. That seems to be the difference of opinion, so let's resolve it... now.
-David
smime.p7s
Description: S/MIME cryptographic signature
