----- Original Message ----- From: "Sven Kuenzler" <[EMAIL PROTECTED]> To: "Philipp Meier" <[EMAIL PROTECTED]> Sent: Monday, April 08, 2002 10:11 AM Subject: Re: [Webwork-user] revised - next release features/requirements
> > > > On the other hand, my hope is to *get rid* of XSP using WW, so this is > quite > > > the opposite approach. > > > > But how will we then make the MVC thingy an HMVC thing? A kind of custom > > template language for XML? XSP lite? > > Something like that, yes. As I suggested, one could try to create a > SAXFilter with a functionality similar to WW's core jsp taglib. The other > possibilty would be a XSLT extension. But as I said, I'd like to have the > opportunity to reuse WW actions in C2. And integrating such an extension > with C2 is not feasible, neither conceptually nor technically. > > A third solution would be making a XSP view and a WebWork XSP taglib, as you > said. But first, you don't get XSP out of Cocoon (easily). Second, my > problem with XSP is that it's next to undebuggable. For those who don't > know XSP: It's basically a bunch of XSLT stylesheets creating Java code to > be compiled on the fly. Think of it as "JSP plus XML syntax minus JavaBean > support minus TLDs". (Not exactly precise, but you get the point). > > Sven.... > > _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
