> -----Original Message----- > From: Todd Densmore [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 5 March 2003 08:25 > To: '[EMAIL PROTECTED]' > Subject: RE: how to call a view? > > > label the transform with the view name, then call it by appending > @cocoon-view=(labelname) in the request
This doesn't REALLY answer my question ... or if it does, then I've failed to understand it, I'm sorry :-) What I'm trying to understand is how the 2 "alternative" methods of calling views really work (see my original message below). The documentation provides some hints about using file-extensions, or HTTP varies headers to select views, but it doesn't provide, for instance, a sitemap snippet. I am guessing that to call a view you MUST use "?cocoon-view=view-name" in the request URI, and if you want to call the view some other way then you also need another pipeline to convert it into a call using "?cocoon-view=view-name" Can anyone confirm or deny this? Cheers Con > > -----Original Message----- > From: Conal Tuohy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 04, 2003 2:22 PM > To: Cocoon Developers (E-mail) > Subject: FW: how to call a view? > > > I had no luck with this message on Cocoon Users ... I'm > wondering if anyone > here can answer this question about other ways to call a view? > > Thanks! > > -----Original Message----- > From: Conal Tuohy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 4 March 2003 20:01 > To: Cocoon Users (E-mail) > Subject: how to call a view? > > > I'm planning to implement a Lucene-based search, so I've been > reading up on > Views. > > It seems to me that a view can be selected just by adding > "?cocoon-view=some-view" to the URI. I've tried this and it's all OK. > > But the documentation hints that there's another way, which I > don't quite > understand (see bottom of > http://xml.apache.org/cocoon/userdocs/concepts/views.html): > > >Suggestions for further accessing views are: > > > >React on a "variant" HTTP header (nothing cocoon specific > >since the concept could be impelemented later on by other > >publishing frameworks). > > > >React on URI extension: for example http://host/path/file.view, > >that is something that can be done by configuring the sitemaps > >manually. (where http://host/path/index is the default > >resource, and index.content is the XML view of the content). > > "configuring the sitemaps manually"? Can anyone explain how these 2 > suggestions should be implemented? Would I need to have > something like this? > > <map:match pattern="**/*.*"> > <map:redirect-to uri="cocoon:/{1}/{2}?cocoon-view={3}"/> > </map:match> > > Cheers!!! > > Con > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
