Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of amilasuriarachchi@gmail.com
 designates 72.14.202.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=jkMtHQS7MqNs5DCLNWkb2E3kyVdVAT7jNFUnwQauBMp4bPEDjK3/hc0AsnzqolyjOMLtA2/mTqvBzPZeKMxgTxk3Ti937yEQFwFyxPAIjIUDAJAo/MhFo508SSH+8R8FFhgaETXu45e9mpjzjVy3Ht4Dx0BiTn7YSanjLm3E8VA=
Message-ID: <60708f4b0712172315i682dcd83n855790b05b64e57f@mail.gmail.com>
Date: Tue, 18 Dec 2007 12:45:00 +0530
From: "Amila Suriarachchi" <amilasuriarachchi@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [AXIS2] Adding security phase to OutFaultFlow
In-Reply-To: <47676685.1050702@thoughtcraft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10915_2662450.1197962100443"
References: <9e2fff830712120429x51ec7c93nfc6888f3d1219e14@mail.gmail.com>
	 <9e2fff830712120431t20c14ef1j7cb48f2447ebee9d@mail.gmail.com>
	 <475FDD79.6020305@thoughtcraft.com>
	 <60708f4b0712120545o7ccc1c66xa7337904f8d9ced@mail.gmail.com>
	 <559c463d0712122130ma64decfv544d7cb946c5a60e@mail.gmail.com>
	 <9abd5e730712140201u2d18aacer9c1dd7c62280cff3@mail.gmail.com>
	 <60708f4b0712172028o37a07c76l9717441f357b24f3@mail.gmail.com>
	 <47674F98.8020801@thoughtcraft.com>
	 <60708f4b0712172210s69be5c7ckc982487d54c77a50@mail.gmail.com>
	 <47676685.1050702@thoughtcraft.com>

------=_Part_10915_2662450.1197962100443
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Dec 18, 2007 11:49 AM, Glen Daniels <glen@thoughtcraft.com> wrote:

> Hi Amila:
>
> Amila Suriarachchi wrote:
> >     So it seems like you could get the same effect for now by explaining
> in
> >     the Rampart documentation how to change the axis2.xml in the correct
> way
> >     - or even including a sample.
> >
> >     Make sense?  (note I'm not saying -1, just trying to understand)
> >
> > yes I got your point.  But rampart  trunk depends on the Axis2-SNAPSHOT
> > and they need to change the
> > axis2 default xml in order to pass the test cases.
> > When we do a change locally we need to commit it to the repository soon.
> > These test cases can not be committed util we change the axis2 default
> xml.
>
> Hm - really?  Why can't Rampart simply use a custom axis2.xml with the
> new Phase at the root of their test repository?


Then they have to update their axis2.xml when ever Axis2 does. But at least
that is how(using axis2 kernal default xml) they have done it. Idea of
keeping a axis2-SNAPSHOT dependency is to keep the rampart trunk
sync with axis2 trunk.
But I can not understand why you ask rampart people to do a big change while
they could it with a simple
axis2 change. There is no harm to axis2 with this change isn't it?

thanks,
Amila.

>
>
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

------=_Part_10915_2662450.1197962100443
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><br><div class="gmail_quote">On Dec 18, 2007 11:49 AM, Glen Daniels &lt;<a href="mailto:glen@thoughtcraft.com">glen@thoughtcraft.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Amila:<br><div class="Ih2E3d"><br>Amila Suriarachchi wrote:<br>&gt; &nbsp; &nbsp; So it seems like you could get the same effect for now by explaining in<br>&gt; &nbsp; &nbsp; the Rampart documentation how to change the axis2.xml in the correct way
<br>&gt; &nbsp; &nbsp; - or even including a sample.<br>&gt;<br>&gt; &nbsp; &nbsp; Make sense? &nbsp;(note I&#39;m not saying -1, just trying to understand)<br>&gt;<br>&gt; yes I got your point. &nbsp;But rampart &nbsp;trunk depends on the Axis2-SNAPSHOT<br>
&gt; and they need to change the<br>&gt; axis2 default xml in order to pass the test cases.<br>&gt; When we do a change locally we need to commit it to the repository soon.<br>&gt; These test cases can not be committed util we change the axis2 default xml.
<br><br></div>Hm - really? &nbsp;Why can&#39;t Rampart simply use a custom axis2.xml with the<br>new Phase at the root of their test repository?</blockquote><div><br>Then they have to update their axis2.xml when ever Axis2 does. But at least that is how(using axis2 kernal default xml) they have done it. Idea of keeping a axis2-SNAPSHOT dependency is to keep the rampart trunk
<br>sync with axis2 trunk. <br>But I can not understand why you ask rampart people to do a big change while they could it with a simple <br>axis2 change. There is no harm to axis2 with this change isn&#39;t it?<br><br>thanks,
<br>Amila.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class="Ih2E3d"><br>--Glen<br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a href="mailto:axis-dev-unsubscribe@ws.apache.org">axis-dev-unsubscribe@ws.apache.org</a><br></div><div><div></div><div class="Wj3C7c">For additional commands, e-mail: <a href="mailto:axis-dev-help@ws.apache.org">
axis-dev-help@ws.apache.org</a><br><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Amila Suriarachchi,<br>WSO2 Inc.

------=_Part_10915_2662450.1197962100443--