Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (hermes.apache.org: domain of hemapani@gmail.com designates
 64.233.184.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=D1Usm+M97JE/du8fe/nvGIsRU1y5f7qDRiiEJDL7/k8UmKk7hjoKMYzqbU8fFiw/QeLjoK+4DmyBjRqeNDDLZ6kccY9ND0SqkF3GKJ+urjbpNrTE/c67Q+di2htB/4qbiqjAg2Bq2r1oSXhfh1JGhqMuSFdz5qWHtMlyXXuYAjk=
Message-ID: <f8de7ee04120919264b2fd626@mail.gmail.com>
Date: Fri, 10 Dec 2004 09:26:19 +0600
From: Srinath Perera <hemapani@gmail.com>
Reply-To: Srinath Perera <hemapani@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [Axis2][OM] Simpler way to get NameSpace
In-Reply-To: <03ae01c4de62$70ff0920$83604109@LANKABOOK>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <f8de7ee04120819532d4fd04d@mail.gmail.com>
	 <f8de7ee04120820246bcca7b5@mail.gmail.com>
	 <41B7DE6E.2040705@cs.indiana.edu>
	 <f8de7ee041208213115efeb76@mail.gmail.com>
	 <41B7EEA7.1010103@cs.indiana.edu>
	 <01c001c4ddc1$11dd7810$49464109@LANKABOOK>
	 <41B837AA.3030905@cs.indiana.edu>
	 <010b01c4de07$fecc5d80$83604109@LANKABOOK>
	 <f8de7ee04120918127d09ab07@mail.gmail.com>
	 <03ae01c4de62$70ff0920$83604109@LANKABOOK>

On Fri, 10 Dec 2004 08:46:23 +0600, Sanjiva Weerawarana
<sanjiva@opensource.lk> wrote:
> "Srinath Perera" <hemapani@gmail.com> writes:
> >
> > +1, this is what I have in my mind :) No OMNamespace for common case!
> >  shall we change  String getNamespaceName () -> String getNamespaceURI ()
> 
> No .. "namespace name" is the right name for that! I agree common
> usage is namespace URI but that's not the right term.
> 
> > > Why do we have OmElement.resolveNamespace (uri, prefix) right now?
> > > What purpose does that serve?
> > I think this is to obtain the OMNamespace object that declared with
> > (uri, prefix) pair.
> 
> Well yes :-) but what good is it? In what scenarios do you look up
> a namespace declaration when you already know the namespace name
> and prefix?
+1 accepted :) I actually do not like OMNamespace no where in the API
(it is ok to have it in the impl hidden from the user) I was under the
impression that it is needed for building the OM e.g. Ajith say
>This is used during building. Once you say resolve namespace it
>returns the closest correct namespace object. it may be the
>decalaration in the same element or in one of its parents. It is
>actually a way of finding the namespace "object".
But we can give the prefix andnamespace Name and let the Impl resolve
the Namesapce object if he likes to so I am plus +1 for remove resolve
Namesapce