Joe, I wrote a long email explaining my position and it got deleted...errrgg! Anyway, my point came down to a simple statement:
Struts needs to create a config file analagous to that of Cocoon's sitemap. My reasoning is as folllows: I see a webapp framework somewhat like message oriented middleware, but directed to the end client. It should be capable of handling various inputs on several different protocols. For example, handling POST requests from HTML browser or a SOAP requests from a BPEL-WS system...all while being able to validate input, initiate various processes, and finally generate a response. All this activity should be configurable based on the URL being requested at both the M and V levels of MVC. Finally, the Struts developer should be able to handle each request with any controller chain they choose and target several platforms. Cocoon manages this with the Forms framework...which is analogous in many ways to JSF. My skepticism arises from the constanly chagning face of the web, emerging protocols, and new target devices. I see no way that Cocoon forms or JSF renderkits can keep up with this change. In conclusion, it is a necessity to be able to plugin any new URL to a webserver and have it produce the desired view. I hope this makes sense and is not to broad of any answer. I more than happy to clarify. Comments appreciated, Julian --- Joe Germuska <[EMAIL PROTECTED]> wrote: > At 8:37 AM -0800 11/10/04, Julian wrote: > >Hi all, > > > >I am an avid user of Cocoon and really love the > >sitemap concept. I am wondering if the current > >direction of the struts-chain component is to only > >manage action chaining. IMHO, Struts is great as > a > >controller, but not nec. for the View in the MVC > >world. In other words, will it be possible to have > an > >analogous process to Coccon pipelines in Struts or > is > >it best to use the Cocoon plugin for "view" > >processing? I really enjoy how the seperation of > >concerns has been achieved with Cocoon, but for > >similar reasons, I cannot use Cocoon's Forms > paradigm > >or Java Server Faces yet. > > I don't think that there's any reason to limit > struts-chain to > "action chaining." There's no reason one couldn't > define view > processing chains as well. I don't know Cocoon well > enough to > explain how struts-chain would be used to make an > analogous process, > but it certainly sounds like something Struts Chain > could do. > > There's a lot of other discussion going on the user > list right now > about whether Struts needs a concept of a "view > controller" or not, > and if so, how one might implement it. > > Maybe you could articulate some of the shortcomings > you see in how > Struts fails "for the View in the MVC world" or what > you'd want to do > that it doesn't do now, in use-case terms. > > Joe > > PS as I was writing this, Don Brown responded, > pointing out correctly > that true pipelining won't be what Struts does, > since it's not using > SAX. However, you could probably approximate the > behavior by > chaining together commands which operate on the > context. > > -- > 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 ===== Live simply so others may simply live. -Ghandi Pluralitas non est ponenda sine neccesitate. "Entities should not be multiplied unneccesarily" -William of Occam __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
