--- Gianugo Rabellino <[EMAIL PROTECTED]> wrote: > grenoml wrote: > > >>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? > > As a *client*? :-) This information is available only on the server: > you > have absolutely no informations on where the server is running go > figure > about the context... > > > 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/... > > The XML:DB URI doesn't contain any context at all (URI start with > /db). > It's resolved internally by the XML-RPC driver. > > Ciao, > > -- > Gianugo Rabellino >
Ok, yes, client would not know this. Is there no way in which the context could be advertised by the server or discovered by the client? LDAP? Hardcoding the name just seems really rigid. Regards, Gerry Reno __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
