--- Gianugo Rabellino <[EMAIL PROTECTED]> wrote: > grenoml wrote: > > > 1. The 'context XML config file' came into being with the Tomcat > 4.1.x > > releases. For earlier Tomcat releases the user can just put the > > context mapping into the server.xml file or alternatively download > the > > release-identified war and rename it to Xindice.war. > > Ouch. This makes things worse to me. Look, there is *no way* for > Xindice > to work "out of the box" if the context map is not /Xindice: the path > is > harcoded in the XML-RPC client (see > org.apache.xindice.client.xmldb.xmlrpc.CollectionImpl.java), so the > presence of an /Xindice context is absolutely necessary. >
I'm not buying hardcoded. Why? Is it absolutely necessary to do it this way? In DatabaseImpl.java why couldn't you extract the context under which you are running and then provide that as an argument to CollectionImpl() to be used as the service location? That way whatever context you came up as would just work. Then you could have the 'drop and forget' no matter what name the WAR file has. In the documentation you could just refer to it as .../<your xindice context>/... with an example .../xindice-1.1/... > > Ciao, > > -- > Gianugo > Regards, Gerry Reno __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
