sob...sob... I guess what I was attempting appeared to be such a natural extension of the framework that I just assumed that it would be supported.
The way I was approaching my architecture was that almost all pages would be velocity pages. But a few pages would be in dsvl, such as a FAQ page, which is very regular and highly structured. DSVL seems perfect for transforming an xml faq document to html. As you can imagine, my frame.vm file includes other files like header.vm. I suppose that I could get around this by keeping a parallel copy of these files in dsvl, but this seems really awkward. I'm just wondering, if the <path> tag supported a type attribute, we could say something like ><view path="faq.xml"> > <transform type="dvsl"> > <path value="faq.dvsl"/> > <path value="frame.vm" type="document"/> > </transform> ></view> Do you think that this is how you would approach adding in this feature? Maybe, if this were only supported for the most "natural transformations", it would just fit into the current design. If it seems easy, can you point me to where in the source to focus for modifying? Anyway, thanks again, I really am having a good time with Maverick. Dan At 10:37 PM 4/8/02 -0700, Jeff Schnitzer wrote: > > From: Dan Finkelstein [mailto:[EMAIL PROTECTED]] > > > > As you might guess, I want the faq.xml file to be processed by dvsl >using > > faq.dsvl. Then I want the output processed by velocity using >frame.vm. > >I take it frame.vm is a document transform, expecting the previous >output to be $wrapped? > >At the moment, there is no way to do multiple transform types - only one ><transform> node is allowed. Thus you can do: > ><view path="faq.xml"> > <transform type="dvsl"> > <path value="faq.dvsl"/> > <path value="someother.dvsl"/> > </transform> ></view> > >*or* > ><view path="faq.xml"> > <transform type="document"> > <path value="frame.vm"/> > <path value="someother.vm"/> > </transform> ></view> > >But there is currently no way to run a dvsl transform and then run the >output through a document transform. > >Running multiple transform types together is actually a rather tricky >problem. The transforms would have to negotiate the optimal mechanism >to pass content - for instance, to pass from xslt to dvsl you would want >to pass DOM objects, but to go from dvsl to document you would want a >text stream. Xslt to xslt is most efficient with SAX events. > >Perhaps for Maverick 3.0 :-) > >Jeff Schnitzer >[EMAIL PROTECTED] > >_______________________________________________ >Mav-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/mav-user _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
