On Mon, May 9, 2011 at 10:33 AM, Supun Kamburugamuva <su...@wso2.com> wrote:
> Are we going to implement the all transport concept for this release? > No this is not the time to introduce changes to Axis2. > If not it is better to make these two services exposed only in HTTP/S. > Anyway these two services cannot be exposed in any other transport so > having that in the services.xml is quite natural. > +1 Thanks, Hiranya > > Thanks, > Supun. > > On Sun, May 8, 2011 at 5:39 PM, Hiranya Jayathilaka <hira...@wso2.com> > wrote: > > Hi, > > > > On Sun, May 8, 2011 at 4:08 PM, Amila Suriarachchi <am...@wso2.com> > wrote: > >> > >> > >> On Sun, May 8, 2011 at 11:12 AM, Afkham Azeez <az...@wso2.com> wrote: > >>> > >>> We have discussed this extensively. The proper solution is to add a > >>> parameter to axis2.xml which specifies the behavior of the transports > >>> element not being present in the services.xml. Either this could mean, > >>> expose on all transports, or don't expose on any transports. If this is > >>> don't expose on any transport, the services.xml should declare the > >>> transports on which this service has to be exposed. In either case, the > >>> user's existing services will not simply work OOTB without some > changes. > >> > >> I think the correct solution is define the default export transports in > >> the axis2.xml. By default we make it http https and local. (we can use > the > >> same element in the services.xml) if some one wants to add another > transport > >> it has to declare in the services.xml. Need to do a disscussion at the > axis2 > >> level for this. > > > > +1 This is what I meant by making 'all transports' configurable. > Basically > > we should be able to define the default set of transports. > > > >> > >> For these two services we will make it only available with http/s since > >> other are not configured anyway. > > > > +1 > > Thanks, > > Hiranya > > > >> > >> thanks, > >> Amila. > >> > >> > >> > >>> > >>> _______________________________________________ > >>> Carbon-dev mailing list > >>> Carbon-dev@wso2.org > >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >>> > >> > >> > >> _______________________________________________ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > > > > > > > > -- > > Hiranya Jayathilaka > > Senior Software Engineer; > > WSO2 Inc.; http://wso2.org > > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > > > _______________________________________________ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > Supun Kamburugamuva > Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com > Member, Apache Software Foundation; http://www.apache.org > WSO2 Inc.; http://wso2.org > E-mail: su...@wso2.com; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
