On Tue, 7 Jan 2003, James Bates wrote:
>
> Now I think there's no reason to not do both:
>
> - check XML:DB URL: if it contains a config-file path, use it
> (e.g. if the url is like
> xmldb:xindice-embed:/path-to-config-file://collection/path)
> - otherwise (url is like xmldb:xindice-embed://
Mark J. Stang wrote:
I think the bottom-line is that the embedded version of Xindice is available
to build stand-alone applications or other servers. As such, it is
valuable
to many members of the Xindice community. I am very disturbed that
you see a future where it doesn't exist. Like it is
I am ready to test the embedded version of this.
Mark
James Bates wrote:
> Thank you Vladimir, that clarifies things for me :)
>
> In the case of the embedded architecture there are no separate client
> and server processes, this is true.
>
> There is nonetheless still a logical architecture to
Thank you Vladimir, that clarifies things for me :)
In the case of the embedded architecture there are no separate client
and server processes, this is true.
There is nonetheless still a logical architecture to the application: Some
part of the application should set up the database "server" (whi
I must have missed the beginning of this discussion; sorry. Could you
remind me of the problem?
The question was "How can I configure the embed driver?"
In the XMLRPC driver, the system.xml configuration file is loaded by the
XindiceServlet and this config file is defined in the web.xml file.
Clean
Personally, I for one would have no current use for Xindice
were it not for the embedded version. Nor do I have any
current visions of future uses for anything but the embedded version.
I certainly hope this is not evidence of a movement to do away with the
embedded version...
I also support the em
