Re, Yes you are true but I think I didn't explained myself. These questions may have been answered in the javadocs. I am sure you know (you that architects of OFBiz) why you decided to make a Container class and so on. So perhaps a little enhancement of javadoc on foundation classes to explain why and where to use it would be so nice.
I hope I do not look like too much arrogant with my questions on that thread "General questions"; I just expose the problems I was faced to. Regards, Cédric -----Message d'origine----- De : David E. Jones [mailto:[EMAIL PROTECTED] Envoyé : vendredi 9 février 2007 18:12 À : [email protected] Objet : Re: General questions On Feb 9, 2007, at 9:12 AM, PRONZATO Cedric RD-BIZZ-GRE wrote: > A related problem is how to do "framework" components, I mean > patterns. I think about my SMSC component, I base my code on the mail > container and questions arised: > - When do I have to make my own xml language (ie. MCA for the mail > container)? > - When do I have to make a Container? I guess the answer is if you > have to manage the lifetime (create/release connections, ...). > - When do I have to make an Engine? > - ... > > So I guess we can finish with the following statement: "How to > *use* is quite well documented but how to *make* is a bit less". Have you ever found such a document for anything? My usual approach is generally something like: 1. understand everything that exists, or research anything that is unclear 2. write something manually a number of times so you know what is always the same, and what varies 3. see if a paramerized tool would be helpful 4. apply a significant amount of "genius" 5. apply even more "sweat" to try stuff 6. create an incredible tool or service or however it is best implemented If there was a way to make creation deterministic, what would be the point of creativity? -David
