On Fri, 2004-10-15 at 00:22, Joe Germuska wrote: > >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). > > No, I know about HiveMind, although I must admit that it seems like a > lot of overhead for a lightweight container. So far, Spring is > serving my purposes for dependency injection pretty well...
agreed. > >With that said, let me just go on record as saying I was intrigued with > >Tapestry. > > We should definitely learn all the lessons we can from Tapestry, and > all the other controllers out there. Easier for me to say than to > do, although I have looked at WebWork a little bit. WebWorks reminds me of Struts. In fact, with small adjustments, struts can behave like WebWorks (I'm not suggesting it should ;-) > >(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). > > What would StrutsMesh do that couldn't just be done with SiteMesh? I > have only looked at SiteMesh a little, but it seems like it should be > able to fit in anyway. I haven't put much thought into it. More so, I was using chain as a solution in search of a problem. But with that said.... SiteMesh decorator pattern utilizes request filters, which follows a very similar pattern to Chain (with exceptions). I thought it would be an interesting experiment with Chains to take SiteMesh and apply it to a template processing like velocity templates. I have some very email centric applications and this would be very handy for maintaining a consistent look and feel, and for applying users preferences (html -or- plain/text etc). As for StrutsMesh, I know that SiteMesh can just be used with filters, but if you could apply site mesh decorators at different stages in a custom request process you may be able to do some cool things utilizing info stored in the Request Context. For example, maybe using tiles definitions to decorate sections, or form validation results to decorate with error messages instead of tags. Just a thought... haven't really had time to play it out. The biggest bang for the buck of a StrutsMesh type thing, IMO, would be an abstraction of SiteMesh from the servlet container (assuming Struts chain is moving that way some day). This leads back to my original thoughts, about using SiteMesh + Chain to do "offline" template decoration. And just to be clear... I have no idea if SiteMesh is already capable of this type thing. From what I saw it was Filter focused. Please correct me if I'm wrong. - Mike > -- > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
