On Sun, May 8, 2011 at 1:26 PM, Afkham Azeez <az...@wso2.com> wrote: > The other problem is, even for user deployed services, when these > transports are enabled, the service will be marked faulty. The user cannot > use the UI to change the transports of faulty services. Think about some > service which does not support services.xml files.
If it's a user defined service then there should be some kind of a service descriptor to work with right? Axis2 services have the services.xml. Proxy services have a Synapse configuration file. Data services have a dbs file and so on. > In such a case, how would you selectively enable only certain transports, > when the deployment fails? I agree that this needs to be fixed at Axis2 level proper. But right now we have these two services always complaining about transports. No other admin service or hidden service has this problem. So I think we should fix these 2 services right away. Since they are built-in stuff user has no choice but to live with them. Thanks, Hiranya > > > On Sun, May 8, 2011 at 11:49 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote: > >> Hi Azeez, >> >> On Sun, May 8, 2011 at 11:43 AM, Afkham Azeez <az...@wso2.com> wrote: >> >>> >>> >>> On Sun, May 8, 2011 at 11:40 AM, Hiranya Jayathilaka >>> <hira...@wso2.com>wrote: >>> >>>> >>>> >>>> On Sun, May 8, 2011 at 11:36 AM, Afkham Azeez <az...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Sun, May 8, 2011 at 11:34 AM, Hiranya Jayathilaka <hira...@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. >>>>>> >>>>>> >>>>>> IIRC the idea was to make it configurable what 'all transports' mean. >>>>>> >>>>>> >>>>>> >>>>>>> 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. >>>>>>> >>>>>> >>>>>> Agreed. However I'm not too concerned about user defined services at >>>>>> this point. User knows through which transports a service needs to be >>>>>> exposed and he can use the features provided in our UI (service-mgt, >>>>>> transport-mgt) to configure the services to fit his exact needs. If a >>>>>> service needs to be exposed over a transport like VFS or mail, he can add >>>>>> the required parameters to the service. If he doesn't, service will only >>>>>> be >>>>>> exposed over HTTP/S which is not bad either. >>>>>> >>>>>> The problem is with our built-in admin services. User has no control >>>>>> over these. So trying to expose them over transports for which they are >>>>>> not >>>>>> configured isn't correct. >>>>>> >>>>> >>>>> Admin services are supposed to be exposed only via HTTPS. >>>>> >>>> >>>> I think these 2 particular services are just marked as hidden services >>>> (they don't show up in the UI). >>>> >>> >>> Is there any issue in making VFSTransport optional. Can't you keep it >>> commented out? >>> >> >> VFS transport is optional. It is commented out and not enabled by default, >> if that's what you mean. But the above warning shows up as soon as I enable >> it in the axis2.xml (or from the UI). And as I said it's not just for VFS. >> Happens for just about any transport (Mail, FIX etc). Most users will be >> concerned to see these unnecessary warnings in the log, particularly when >> they cannot really see these services in the system. >> >> Thanks, >> Hiranya >> >> >>> >>> >>>> >>>> Thanks, >>>> Hiranya >>>> >>>> >>>> >>>> >>>>> >>>>> >>>>>> >>>>>> Thanks, >>>>>> Hiranya >>>>>> >>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > 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
