On Sun, Apr 07, 2002 at 11:04:06AM +0200, Sven Kuenzler wrote: > Well, I am using it. At the moment, it's only part of a small prototype > application, though. We also have a somewhat larger webwork app which could > benefit from xsl views someday. > To achieve this, it would be necessary to get the "H" of HMVC into the xslt > dispatcher. I don't know whether such a thing was discussed when designing > the current XSLT stuff:, but I was thinking of a SAXFilter that reproduces > the basic webwork:tags such as property, bean and action. Of course, this > would introduce an additional step to serve a request. The dispatcher would > read some XML document and basically work like the "classic" WW taglib stuff > and then apply the stylesheet.
I did not get your point here. XSLT is currently integrated as a view layer - not as a dispatcher. A drawback of the implementation is that there is currently no way to call an action from a stylesheet like it is possible with the webwork:action tag. But this should be easy using xslt extensions. On the other hand one should consider using XSP and special XSP logicsheets. I crawled the xsp sources sime time ago but it didn't seem trivial to me to extract the xsp stuff to be used stand alone in a "view servlet" for webwork. To integrate more of the cocoon stuff with webwork would carry the idea to excess. -billy. -- Meisterbohne Söflinger Straße 100 Tel: +49-731-399 499-0 eLösungen 89077 Ulm Fax: +49-731-399 499-0 _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
