Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of freeman.fang@gmail.com
 designates 209.85.161.169 as permitted sender)
Message-Id: <5D17ECAE-6C01-41D5-B00F-B4C38B15C1FF@gmail.com>
From: Freeman Fang <freeman.fang@gmail.com>
To: dev@cxf.apache.org
In-Reply-To: <1316694690798-4829980.post@n5.nabble.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-3--912492167
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Remove the CXF MTOSI examples?
Date: Thu, 22 Sep 2011 21:12:04 +0800
References: <1316622382805-4826982.post@n5.nabble.com>
 <CAM1wwhSaXbkn9nD0zM9fSM0aN8B0+exw-dVyguhZfhFeWnTn-Q@mail.gmail.com>
 <1316626135195-4827176.post@n5.nabble.com>
 <33978D3A-6517-4AAF-9EC9-92F4B7FD8136@gmail.com>
 <1316694690798-4829980.post@n5.nabble.com>

--Apple-Mail-3--912492167
Content-Type: text/plain;
	charset=UTF-8;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

Hi Glen,

That's not my company concern,  just my personal point of view :-)
Okay, ensure we still have those MTOSI example in SVN should be enough.

Freeman
On 2011-9-22, at =E4=B8=8B=E5=8D=888:31, Glen Mazza wrote:

> No, if we're keeping it in the source distribution we should keep it =20=

> in both.
> This example is either Good or Not Good, and, on that basis, it =20
> should be
> either included with both or excluded with both.  (I understand your =20=

> company
> has a customer requirement to Mavenize all unmavenized binary =20
> distribution
> samples that would be solved by having MTOSI only in the source
> distribution, but I have a larger concern of removing unused examples,
> period--one that would also take care of your concern :)  Of course, =20=

> it
> would always be available in the SVN archives for anybody still =20
> interested
> in it.
>
> In my view, again, none of us here have sufficient knowledge about =20
> MTOSI to
> be able to authoritatively document it, so it is irresponsible for =20
> us to
> keep an example showing how to use it--authoritative documentation =20
> can be
> the role only of the MTOSI team.  ("Professionally maintaining a MTOSI
> sample in our distribution" is probably an oxymoron.)  Indeed, for =20
> any third
> party web service X, how to use X can only be defined on X.com.  Any
> third-party web service (or in this case, standard) too inactive or
> uninterested to document how their own stuff works, that's a warning =20=

> signal
> that we should be steering clear of it rather than trying to =20
> document it for
> them and include examples for it.
>
> Glen
>
>
>
> Freeman-2 wrote:
>>
>> +1 to exclude it from binary kit, just keep them in svn and src kit.
>>
>> Freeman
>> On 2011-9-22, at =E4=B8=8A=E5=8D=881:28, Glen Mazza wrote:
>>
>>> Nuking appears appropriate.  If MTOSI's WSDL's are well designed, no
>>> special
>>> example for it would be needed (either our already existing Java-
>>> first or
>>> WSDL-first samples would suffice.)  If they're not and need special
>>> tweaks,
>>> it's the responsibility of the MTOSI team (assuming such a team
>>> exists) to
>>> document on their own website how to get their non-standard WSDLs to
>>> work
>>> with JAX-WS implementations, not vice-versa.
>>>
>>>
>>> --
>>> View this message in context:
>>> =
http://cxf.547215.n5.nabble.com/Remove-the-CXF-MTOSI-examples-tp4826982p48=
27176.html
>>> Sent from the cxf-dev mailing list archive at Nabble.com.
>>
>> ---------------------------------------------
>> Freeman Fang
>>
>> FuseSource
>> Email:ffang@fusesource.com
>> Web: fusesource.com
>> Twitter: freemanfang
>> Blog: http://freemanfang.blogspot.com
>>
>
>
> --
> View this message in context: =
http://cxf.547215.n5.nabble.com/Remove-the-CXF-MTOSI-examples-tp4826982p48=
29980.html
> Sent from the cxf-dev mailing list archive at Nabble.com.

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com


--Apple-Mail-3--912492167--