Hi Jonathan, I forward your question to the list because you are not
subscribed. Please, subscribe to the list before sending mails to
the list. Thanks, Lars.

Here you'll find information about how to subscribe: 
                http://www.xmldb.org/projects.html

> From [EMAIL PROTECTED]  Mon Dec 10 21:26:06 2001
> Return-Path: <[EMAIL PROTECTED]>
> From: "Jonathan Borden" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Re: Namespaces and XUpdateQueryService
> Date: Mon, 10 Dec 2001 15:24:33 -0500
> Timothy M. Dean wrote:
> 
> > Hello all,
> >
> > I'm new to this list so my apologies if this question has been covered
> > already. I've been reading through the archives of this list looking for
> > information, but have not yet found what I'm looking for.
> >
> > I'm interested in understanding how XML namespaces are to be handled
> > when selecting nodes for update within the XUpdateQueryService specs.
> > I've read through the discussion a couple of months ago discussing
> > namespaces for the XPathQueryService, resulting in the addition of a
> > setNamespace method for that service. Don't the same issues with
> > namespaces apply when selecting a node for use with the
> > XUpdateQueryService?
> 
> An XUpdate is defined in an XML document (while an XPath is a string), so
> there should be no problem including the requisite prefix/namespace bindings
> on an element in the XUpdate document itself.
> 
> If I am missing something could you provide an example of what needs to be
> done?
> 
> Jonathan
--
______________________________________________________________________
Lars Martin                             mailto:[EMAIL PROTECTED]
SMB GmbH                                        http://www.smb-tec.com

----------------------------------------------------------------------
Post a message:         mailto:[EMAIL PROTECTED]
Unsubscribe:            mailto:[EMAIL PROTECTED]
Contact administrator:  mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
----------------------------------------------------------------------

Reply via email to