On Thu, 2004-10-14 at 20:47, Joe Germuska wrote: > >Struts relies on Jakarta Commons stuff. So I think the pizza base > >is only good as the quality of the ingredients on top of it. > >Is there a way, for example, to get precise line error when, > >say the Digester cant intercept the struts-config.xml file, > >or when the underlying SAX XML Parser finds fault. > > I thought I remembered Howard Lewis Ship talking about factoring out > the code which provides this to Tapestry into a commons library, but > I don't see any signs of it.
Hmmm.... You may be thinking of HiveMind, which is the refactored IOC-type container that grew out of Tapestry. HiveMind is similar in focus to Spring, but follows an approach that is similar to Eclipse. (separation of configuration, services, with extension points). I believe you can get line information from the SAX Parser -- you can definitely get a lot of details from it. But to tell you the truth, personally whenever there is a configuration bug in the XML I don't have a hard time finding it. I think the information in the current stack trace is pretty informative. As for JSPs. That's a problem were not going to solve. When Tapestry refers to line precise error reporting, it really has more to do with views / components and misconfiguration of them. It is definitely a cool thing, but unfortunately JSP is an ass backwards template language. With that said, let me just go on record as saying I was intrigued with Tapestry. I definitely liked the mile high concepts they went after. (reminds me of ASP.NET). There is a lot i don't like about it. And there is stuff they are working on that may make it better (but auto binding of the Attributes like they do is nice in theory, but difficult in practice. Take a look at the IN/OUT/RESET workflow. In practice however, I hated using it. And in the end I boiled the difference down to top down compilation of component pages (tiles and jsf) to inside - out (tapestry). Personally I'm a top-down guy. (although struts can borrow some decorator ideas from site mesh -- with the request processor chain it could be possible to pretty easily make a StrutsMesh). I'm rambling... > > Of course, Tapestry is open source, and under the Apache license, so > if someone wanted to try to apply its methods to Digester (or to > Struts), either by factoring out or copying, that route is open. > > Joe > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn > back; I'll know I'm in the wrong place." > - Carlos Santana
