In message <[EMAIL PROTECTED]>, Vladimir R. Bossicard
<[EMAIL PROTECTED]> writes
>> If you want to create a WAR file, so as to include Xindice within
>>Cocoon, for example, then you need to do something entirely different,
>>which is not described anywhere on the site that I could find.
>
>The problem is that we have currently two versions:
>- 1.0: official version; for end-users
>- 1.1b: development version; for developers
Vladimir,
I appreciate the distinction you are making here. However, although I
see myself as an end-user, I failed to find a way to do what I want to
do without getting into the CVS and source compilation thing. This is
what I want to do (surely nothing unusual):
- use Cocoon as my XML-XSLT-capable middleware;
- use Xindice as my native XML database sitting in the background;
- use XSLT to accomplish as much as possible of my system logic
First off, I couldn't find a way to install Xindice within Cocoon
without building a WAR file. Is there a way to do this?
Second, I want to call up data from Xindice from within my XSLT
stylesheets. I have managed (after a great deal of trial and error) to
set up my Cocoon environment so that it will return XML from Xindice in
response to an XPath query. However, I can't do much with this because
I have found no documentation on the query parameters that you can use
in an HTTP request through port 4080. My expressions with an XPath
obviously get converted to an HTTP request of the form:
http://localhost:4080/db/object/ceramics#//BRIEF-DESCRIPTION
where /object/ceramics is the collection and //BRIEF-DESCRIPTION is the
XPath expression, but else can you do? Am I only able to do this at all
because I have installed the Xindice-http-0.8 add-on?
>And if he has an interest in seeing the project moving forward, he can:
>- write some documentation (we have a wiki-page [1] so that _everyone_
>can contribute)
I would be happy to describe how I managed to set up Xindice so I can
use it through the document() function in my XSLT stylesheets, if that
really is worth doing (i.e. hasn't already been done before).
Best wishes,
Richard Light
--
Richard Light
SGML/XML and Museum Information Consultancy
[EMAIL PROTECTED]
