Hi Dan, On Mon, 2004-09-20 at 23:45, [EMAIL PROTECTED] wrote:
> > First of all let me apologize for the delayed response. No problem, I am doing (too) many different things in parallel and wouldn't have been able to catch up if you'd been faster to answer! > Seems that > xmlns="http://www.w3.org/1999/xhtml"; from affiche.xsl + affiche.xsl > used as view + no epilogue results in an exception from Saxon. This > much I know after a protracted debug session... > > Wrt to your question - I set up your search page locally and after > looking at it I began to wonder if an answer to the question above is > what you really needed. So - > > a.) Attached is a zip that contains a modified version of your xmlfr > search page. I don't see any attachment. It has probably be either forgotten or removed by the list server! > The mods are > i.) Removed this particular bit of ugliness : > select="document(concat('http://localhost:8280/xmlfr- > orbeon/lucene/rss', $requestQuery))/rdf:RDF" > ii.) Minor mods to make it work locally. While these should be > obvious in a diff they are also cataloged in readme.html > > b.) The short answer to the 'query string' question is 'no'. > More info on this below. > > c.) We are going to post a follow up to this message. Attached will be > something cleaned up a bit more than what I am sending this time. > > Now the aforemetioned 'more info'. The Presentation Server is really > focused on moving XML documents, passed as parameters, through > pipelines. So when there is any data you want, e.g. request > parameters, the first question should be 'What generator can grab > that data and put in the pipeline as a document?' > > Of course in some cases, xforms instance for example, the document > is already provided so a generator is not needed. > > Since this mail thread started in the context of xslt processing, > I'll add a little more data about that. In the case of the > xslt processor can access the parameters with a uri of > the form oxf:{parameter name}. However when the xslt processor > is used the page flow pipeline this feature isn't very useful > as the only inputs are oxf:data, which is just the document > that is being processed, and config, which is the stylesheet. > > I mention all of this because it when I saw how you were trying > to work with the request parameters it looked a little unnatural > for a Presentation Server based app. Thanks. Eric (looking forward to seeing the attachment!) -- Did you know it? Python has now a Relax NG (partial) implementation. http://advogato.org/proj/xvif/ ------------------------------------------------------------------------ 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
