On Tue, 2004-09-21 at 12:07, [EMAIL PROTECTED] wrote: > On Tue, 21 Sep 2004 10:39:45 +0200, "Eric van der Vlist" > <[EMAIL PROTECTED]> said: > > First, XMLfr being dedicated to XML, I want to serve XHTML (not HTML) > > documents (thus my xmlns="http://www.w3.org/1999/xhtml"; in affiche.xsl > > and the fact that I am using the XML serializer in cherche.xpl). I am > > wondering if the Saxon crash you are seing with cherche2.xpl isn't due > > to the fact that you are using the transformation to output HTML. > > Ah if only life were that simple.. No there is something weird with > Xalan and assignment to default namespace. It ends up generating > a SAX event that Saxon later chokes on. Still don't have all the > details. > Do know that given the 'right' set of circumstances even a superflous > xmlns='foo-namespace' would result in an exception.
What's weird is that with my current cherche.xpl here, I don't have eny exception (as you can see by yourself since http://beta.xmlfr.org/orbeon/lucene/cherche is proxied to this page). > Btw, wrt to serving up xhtml... We noticed you weren't using the > epilogue. Is this the reason why? I am not using epilogue yet since there is some magic I need to understand first :-) but that would be the way to go for sure. > > Second, I'd like to use the technique I have described as "style-free > > stylesheets" http://www.xml.com/pub/a/2000/07/26/xslt/xsltstyle.html and > > give the ability to the creators of the pages to define the content of > > their pages using building blocks defined in the page flows and > > pipelines. > > > > That's why, instead of aggregating the search result and the page > > template in the pipeline definition, I'd like to pull the search result > > into the page template in the XSLT transformation. > > > > Technically, that may seem not a big deal but in one case the creator or > > editor of a web page needs to modify the pipeline and in the other case > > he has just to edit his/her page. > > Heh, you had me wondering if I sent the wrong file... However I checked > I sent the correct thing. > > Unfortunately this leaves me a bit confused. Isn't the latter > ( editor just needs to edit his page ) still the case after my mods? > That is, I made no changes to cherche.xhtml. No, but you've changed affiche.xsl in such a way that it needs to be applied on an aggregate containing all the information that will be used in the page. If I want to add another information source in my page (let's say with the latest news on XMLfr) I need to update both the page and the definition of the pipeline so that this information source is added to the aggregate. If instead of that I use the document function in my XSLT stylesheet to pull the information (though http or better through an enhanced oxf protocol) I am able to add the information without having to update the definition of the pipeline. IMO, this feature isn't only a trick in Cocoon to deal with the fact that their pipelines are linear, it can be really convenient in some cases. You can see it as "pull vs push". The fact to aggregate stuff in the pipeline definition is like pushing information in your pages, whereas the fact to include information when needed in a page template is like pulling information from the definition of the page. I tend to prefer the "pull" approach as more flexible but that's probably quite subjective. > Btw, it is very good that you sent that link. The follow up I > referred to before was to include an attachment that would show > how to do things the 'Presentation Server' way. After reading > the article I am pretty sure that the 'Presentation Server' > way and 'Eric's Way' are different ways of achieving common > goals. Yes, I think so. > _very_ roughly the mapping is something like > > XML content files (10% presentation + 90% data) --> model > + XML specific layout (10% data + 90% presentation) --> view > + XML generic layout (100% presentation) --> epilogue > + XSLT file (90% logic + 10% presentation) --> epilogue > ------------------------------------------------- > (X)HTML. > > Where model, view, and epilogue are pipelines > and part of the larger pipeline > > model --> view --> epilogue > > and the model brings some collection of xml documents > into pipeline, the view takes care of any page > specific presentation, and the epilogue takes > care of general site presentation. I think that the main difference is that pull/push approach : is that enough to pull information from your pages or do you have to explicitly push them in your pipeline definitions. > Hopefully tomorrow someone here can put together > that followup. > > > > > I could generate the pipeline definition dynamically from the layout > > page (ie, seeing that the author wants to include a search result, > > create the pipeline that does the aggregation), but wouldn't it be quite > > heavy? > > Am not quite sure what you mean here, but hold off on the > explanation until after we have sent out that next message. Just a couple of sentences :) ... If I want to keep my cherche.xhtml and not require that the author of this page has to take the pain of defining which data needs to be aggregated before being submitted to the XSLT transformation, I can create the pipeline dynamically through a XSLT transformation that will look which information is used in cherche.xhtml. In other words, I could write a XSLT transformation that would transform my cherche.xhtml into cherche.xpl. > > > > Being able to access to the output of a pipeline in my XSLT > > transformation would be soooo much simpler :) ... > > > > But then we wouldn't have had this conversation. :) Sure! Eric -- Tired of typing XML tags? http://wikiml.org ------------------------------------------------------------------------ Eric van der Vlist http://xmlfr.org http://dyomedea.com (ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax (W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema ------------------------------------------------------------------------ ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
