Hi All,
This is a great
thread.
Jean perhaps AntiPatterns will help you to see the problems and how to fix them. Another thing that your troubles say to me is that we need to get better at presenting the patterns in the first place. A Pattern needs to be focused so that it can be redily applied to a situation. All to often patterns are way to abstract to be of real use. One of the things that John Crupi (Core
J2EE Patterns guy) is trying to do is make patterns and specifically J2EE patterns more accessable in the form of what he calls 'Micro Architectures'. The final section of the second edition has a micro-architecture to integrate workflow into a J2EE app. The approach is almost a cook book, its really worth the read.
Another interesting point is that we often don't really grok some things until we look at it from another vantage point. Thus the value of expierence. If we build a big system we almost always get some things right and some things wrong. If we have and/or take the time to learn from what went well and what didn't we often learn it a lot better.
Best of luck Jean!
TTFN,<br /> <br />-bd-<br /> <br /><a href="http://www.amazon.com/exec/obidos/ASIN/0471449156/qid=1064343733/sr=2-1/ref=sr_2_1/002-8375300-3666449" target="_blank" rel="nofollow">Jakarta Pitfalls</a> | <a href="http://www.amazon.com/exec/obidos/tg/detail/-/0471146153/qid=1064343733/sr=1-2/ref=sr_1_2/002-8375300-3666449?v=glance&s=books" target="_blank" rel="nofollow">J2EE AntiPatterns</a> | <a href="http://www.amazon.com/exec/obidos/tg/detail/-/0471462071/qid=1064343733/sr=1-3/ref=sr_1_3/002-8375300-3666449?v=glance&s=books" target="_blank" rel="nofollow">Mastering JavaServer Faces</a> | <a href="http://bill.dudney.net/roller/page/bill" target="_blank" rel="nofollow">Blog</a> | <a href="http://www.jroller.com/page/BillDudney" target="_blank" rel="nofollow">Eclipse Blog</a> | <a href="http://www.sourcebeat.com/TitleAction.do?id=2" target="_blank" rel="nofollow">Eclipse 3 Live</a>