On Fri, 2008-03-07 at 12:52 +0530, Samisa Abeysinghe wrote: > People just want to try the wsdl serving and know how to do that with a > service. I do not think it is a good idea to add more features to > existing samples and take away the key message out of the samples. As an > example so SOAP 1.1 we have a seperate sample, so does rest. We can > easily add those to one sample and make is a "one stop shop" sample. > However the idea is to "KISS", and not to clutter the samples with > overloaded information. > > Samples are for absolute beginners, not to those who want to do more. > For those who want to d more, there are docs and header files to figure > things out.
Absolutely +1 . > > Samisa... > > Senaka Fernando wrote: > > Hi Samisa, > > > > We have the necessary resources to get started with the Calculator sample. > > I will change the wsdl location etc. and get this organized. Afterwards, I > > will document this on the Axis2/C Manual. > > > > But, I strongly believe that it would be better to have WSDLs for atleast > > these samples, > > > > 1. Echo (this is the most primitive "does it work well?" test) > > 2. Mtom (to test interoperability users may need this) > > 3. Notify (the only OUT-ONLY sample we have) > > > > math/sg_math may not be necessary, but, they are the only services left out. > > > > Regards, > > Senaka > > > > > >> It is a good idea to have a sample that shows how to do that. However, I > >> do not think that we have to demo this for all samples. We can just have > >> one sample that shows hot to do that. > >> > >> Samisa... > >> > >> Senaka Fernando wrote: > >> > >>> Hi devs, > >>> > >>> Axis2/C supports contract first approach IIRC. Thus, it would be better > >>> if > >>> we could provide WSDLs for each sample service. This is necessary as > >>> there > >>> are users who use Axis2/C server side with various other clients. It > >>> also > >>> will broaden our capabilities in interop testing. > >>> > >>> Once this is done, we have to make sure that we provide the static .wsdl > >>> path for each sample in the corresponding services.xml. This should be > >>> more or less similar to how we setup the policy files of the secpolicy > >>> samples in Rampart/C if you are familiar. > >>> > >>> I'm looking forward to document the use of a static .wsdl file for each > >>> service sample, and before that could be done it is better if we could > >>> make $subject available. > >>> > >>> Hope to see these before the next release. > >>> > >>> Regards, > >>> Senaka > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >>> > >>> > >> -- > >> Samisa Abeysinghe > >> Software Architect; WSO2 Inc. > >> > >> http://www.wso2.com/ - "Oxygenating the Web Service Platform." > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
