On 2/13/02 7:55 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote: > > On 2/13/02 7:35 AM, "Ted Husted" <[EMAIL PROTECTED]> wrote: > >> >> It's important to remember that I am not concerned only with Velocity, >> but with all presentation layers, including JSTL, XLST, et cetera. If >> people want work work on a Velocity-specific solution, that's their >> perogative. If people want to collaborate on a shared API object, even >> better. > > I agree 100%. I just don't think it necessarily has to be a single API > object, but more like a definition about where things will be that all users > can get to. If it can be decoupled from the Servlet API, so much the > better, I think. >
I consider my ability to quickly disagree with myself a *strength* :) I can see that a single object is nice. However, my issues as a hopeful customer are, just so its clear o Concern : That the requirements of a broad audience like Vel, JSTL, XSLT will result in compromises in the API object that a resource contract would avoid o Hope : that access to this object/contract can be abstracted away from the Servlet API so Struts can be used outside of a webapp. Upon reflection, this level of abstraction may require a single API object :) geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting My inner cowboy needs to yodel. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
