On Sunday, December 30, 2001, at 02:00 PM, Timothy M. Dean wrote:
I'm new to this "open source" thing ;) Can anyone tell me what precisely I
should be doing to submit my code changes? Do I simply do a CVS commit, or
are there additional/alternate steps that I should be following?
You create a patch against the CVS repository for all changed files. See http://xml.apache.org/source.html for some help.
I've completed these changes and gotten them tested so they work in my specific environment. The changes I made to the client side are completely within the Xindice XUpdateQueryServiceImpl class. In order to make use of them it is necessary to cast the more generic XUpdateQueryService instance to the Xindice-specific implementation.
Ok, let's see what it looks like and then we can probably change the interface itself.
These changes are also completed. Namespace maps that were defined by the
client API are being passed through to both the XPath implementation when
updating against a collection, and to the Lexus implementation when updating
against a single resource.
Excellent!
This part has yet to be completed. I will try to get the latest Lexus code
as soon as I am able and work on this change. Before I get too far along -
An opinion question: Assuming that an XAPI client application specifies one
or more namespaces via the setNamespace() method, and assuming that
namespace mappings are also defined within the XUpdate commands XML, which
namespace mappings should be given priority if the same namespace prefix is
mapped in two places? I am assuming that any namespaces that are defined
within the XUpdate modifications XML should take precedence over any
mappings defined by the API client - Any other opinions on this?
My opinion is the opposite. I see it as the namespace methods being the thing used closest to execution time so they should override the XML declared namespaces. Think about the XUpdate being stored on disk and then being brought into the program. In that scenario I'd definitely expect the methods to override. Also if you're programmatically generating the XUpdate, then you're probably not going to use both mechanisms anyway.
- Tim
Kimbro Staken XML Database Software, Consulting and Writing http://www.xmldatabases.org/
