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 chinthakae@gmail.com
 designates 64.233.170.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:reply-to:from:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole;
        b=fDRGdIIHrl8jWmeehe4ywVF0882YdTrNo+sFwB6VkaRyWs6aRKCN65Et9AhRpZEnFpth1zt9GEij4G9yH5VU2Hp4A8EZJUakS6J1rYX7Dv9PcAlZMi+3h9Ry6gwAhObZIroR9p+BWlW1dBdfBIolOI0JmzwLt2y3mJXA7fwh3Gs=
Message-ID: <00d601c56104$146a2030$0400000a@extremem>
Reply-To: "Eran Chinthaka" <chinthakae@gmail.com>
From: "Eran Chinthaka" <chinthakae@gmail.com>
To: "Venkat Reddy" <vreddyp@gmail.com>,
	<axis-dev@ws.apache.org>,
	"Ajith Ranabahu" <ajith.ranabahu@gmail.com>
References: <57023d13050520042760afe748@mail.gmail.com>
 <008401c560dd$ca4510d0$0400000a@extremem>
 <f43ea579050524213843785d08@mail.gmail.com>
 <fadf6631050524223466c7472e@mail.gmail.com>
Subject: Re: [Axis2] Proposal for adding a method in OMElement API.
Date: Wed, 25 May 2005 14:27:57 +0600
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Hi Venkat and all,

>Okay - the usecase we have is the following method in SAAJ API on
>javax.xml.soap.SOAPElement:

>boolean removeNamespaceDeclaration(java.lang.String prefix)

>We can't implement this without the undelying OM design catering to such 
>needs.

>So here goes my +1 for implmenting this method on OMElement.

>Regarding the uniqueness of prefix, i dont think it is an issue,
>because every element has its own hashmap object for namespaces, and
>for one prefix, there can be only one namespace in the scope, so
>removal such namespace will not affect other elements or other
>namespaces, i guess.

Every element has a namespace map. But if a child is using a namespace 
declared in the parent, that child is pointing to the parent for that. So if 
we remove the namespace from the parent, we have some trouble.

I agree that u need a method like this for SAAJ impl. But how can we 
compromise ?

>When in doubt, lets vote :-)

Is it a joke ? ;) ;).

Regards,
- Chinthaka

>- Venkat


On 5/25/05, Ajith Ranabahu <ajith.ranabahu@gmail.com> wrote:
> Hi all,
> Well since our OMElementImpl keeps its own list of namespaces adding /
> declaring a namespace would affect that Element only. if the reference is
> removed from the parent I don't see a problem with the children since they
> keep their own reference to the particular namespace. We ask for a 
> mandatory
> namespace at creation, rememebr ?
> The only thing that will not be elegant is the serialization.(I don't see 
> a
> problem though. The serializer handles it right and generates a 
> sematically
> valid XML. That generated XML is not elegant)
> So even though a non-used namspace does no harm (except serializing it on
> the declared element making the XML ugly)  we can techinically remove it
> without a problem.
>
> On 5/25/05, Eran Chinthaka <chinthakae@gmail.com> wrote:
> > Hi Jaya and all,
> >
> > I still find difficult to give you a method to remove namespaces.
> >
> > Namespaces, once defined in an element, that will be used by all of its
> > children. So if we try to remove a namespace, that will be a total mess.
> > Isn't it ?
> >
> > So I'm in doubt to give *any* of the methods to remove namespaces .....
> >
> > Regards,
> > Chinthaka
> >
> >
>
>
>
> -- 
> Ajith Ranabahu