Rick Reumann wrote:

Some comments below...

Michael McGrady wrote the following on 9/13/2004 5:40 PM:

Thanks for your comments below. It has helped clarify things. Your approach is pretty nice but in the above how would you be able to use this same Action for regular links? It seems like you have tied this Action to requiring use of hte ImageTagUtil which doesn't make too much sense for when you'd want to get to this action class from a standard link?


Hi, Rick,

We are getting someplace here, I think. I don't use this Action at all. I just made this little class up to show what I was talking about. Tying the solution to these things just ruins performance and flexibility. Decoupling, I have always thought, is like Aaron Nitzovitch's theory of "over protection" in chess. If you have too much protection on a square, then none of the pieces involved is critical and so all are free to operate as offensive weapons. What I am trying to say is that I use a Facade, which means that the Facade is the standard interface for all the differing page operations we were discussing. I don't try to use an Action or any other particular solution outside the Facade to do this. The <crackwillow:image/>, <crackwillow:file/>, <crackwillow:link/> , ... , etc. tag is the Facade. I am trying to advocate that the correct solution for a generic approach is a Facade represented by a taglib covering all the options that are relevant. This Facade is not even wedded to struts. I do use struts, but that is not necessary. That is but a "component" of the mix behind the Facade. That's what I do. Now, can you expand on what you do with MappedLookupAction?

I suspect we are working on differing attempts at "generic apporaches". Mine is related to what is written on the JSP page and yours, I think, is related to finding a generic approach with struts actions. Exactly what you are doing is not clear to me.

By the way, did you see the post by Craig on MappedLookupAction today?

Michael McGrady


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to