Re: [Carbon-dev] QueueService and MessageQueue
On Mon, May 9, 2011 at 10:39 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Mon, May 9, 2011 at 10:33 AM, Supun Kamburugamuva su...@wso2.comwrote: 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. This fix is committed. These services are exposed only in HTTP/S now. Thank you. +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 -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] QueueService and MessageQueue
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. 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
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 11:34 AM, Hiranya Jayathilaka hira...@wso2.comwrote: 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. 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
Re: [Carbon-dev] QueueService and MessageQueue
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.comwrote: 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). 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
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 11:40 AM, Hiranya Jayathilaka hira...@wso2.comwrote: 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.comwrote: 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? 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
Re: [Carbon-dev] QueueService and MessageQueue
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. In such a case, how would you selectively enable only certain transports, when the deployment fails? On Sun, May 8, 2011 at 11:49 AM, Hiranya Jayathilaka hira...@wso2.comwrote: 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.comwrote: 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.comwrote: 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;
Re: [Carbon-dev] QueueService and MessageQueue
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.comwrote: 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.comwrote: 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.;
Re: [Carbon-dev] QueueService and MessageQueue
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. For these two services we will make it only available with http/s since other are not configured anyway. 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
Re: [Carbon-dev] QueueService and MessageQueue
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 For these two services we will make it only available with http/s since other are not configured anyway. +1 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 -- *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
Re: [Carbon-dev] QueueService and MessageQueue
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
Re: [Carbon-dev] QueueService and MessageQueue
Are we going to implement the all transport concept for this release? 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. 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
Re: [Carbon-dev] QueueService and MessageQueue
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
[Carbon-dev] QueueService and MessageQueue
Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service Thanks -- 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
Re: [Carbon-dev] QueueService and MessageQueue
Hi, On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: SQS is composed of these two services. Message box component provides these services. thank you. [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service Thanks -- 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 -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] QueueService and MessageQueue
On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service The reason is we have not limited the transport to https unlike in other admin services. If you remove that you should get this error with other Admin services as well. thanks, Amila. Thanks -- 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 12:02 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, May 7, 2011 at 10:59 PM, Amila Suriarachchi am...@wso2.comwrote: On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service The reason is we have not limited the transport to https unlike in other admin services. So then I guess it's a bug, isn't it? We have fixed all other services (Version, HelloWorld etc) by exposing them over HTTP/S only. No! What if users deploy their own services? Their services will automatically be marked as faulty, and none of their services will work OOTB. Why don't we make VFSTransport optional? Thanks, Hiranya If you remove that you should get this error with other Admin services as well. thanks, Amila. Thanks -- 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 ___ 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
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 12:08 AM, Afkham Azeez az...@wso2.com wrote: On Sun, May 8, 2011 at 12:02 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, May 7, 2011 at 10:59 PM, Amila Suriarachchi am...@wso2.comwrote: On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service The reason is we have not limited the transport to https unlike in other admin services. So then I guess it's a bug, isn't it? We have fixed all other services (Version, HelloWorld etc) by exposing them over HTTP/S only. No! What if users deploy their own services? Their services will automatically be marked as faulty, and none of their services will work OOTB. Why don't we make VFSTransport optional? +1. We want SQS services expose what ever available transport since it is not just a service used for Admin Console. Yes, it won't work with transports like SMTP, JMS, VFS without having explicit parameters set. In that sense one can argue every one suppose to specify all the transports that service can actually work with. But as Azeez pointed out normally Axis2 service authers don't specify those and hence all those services are marked as faulty. So making VFSTransport optional would be better solution. thanks, Amila. thanks, Amila. Thanks, Hiranya If you remove that you should get this error with other Admin services as well. thanks, Amila. Thanks -- 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 ___ 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 7:43 AM, Amila Suriarachchi am...@wso2.com wrote: On Sun, May 8, 2011 at 12:08 AM, Afkham Azeez az...@wso2.com wrote: On Sun, May 8, 2011 at 12:02 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, May 7, 2011 at 10:59 PM, Amila Suriarachchi am...@wso2.comwrote: On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service The reason is we have not limited the transport to https unlike in other admin services. So then I guess it's a bug, isn't it? We have fixed all other services (Version, HelloWorld etc) by exposing them over HTTP/S only. No! What if users deploy their own services? Their services will automatically be marked as faulty, and none of their services will work OOTB. Why don't we make VFSTransport optional? +1. We want SQS services expose what ever available transport since it is not just a service used for Admin Console. Yes, it won't work with transports like SMTP, JMS, VFS without having explicit parameters set. In that sense one can argue every one suppose to specify all the transports that service can actually work with. But as Azeez pointed out normally Axis2 service authers don't specify those and hence all those services are marked as faulty. So making VFSTransport optional would be better solution. And how do we do that? By default Axis2 exposes services over all available transports. If a particular transport is not configured for a service, above warnings are shown. I think service also gets marked as faulty in this case, but other active transport bindings continue to work (they don't malfunction as Azeez has mentioned). You will see this behavior in all the releases we have done so far and I don't think this can be fixed without some serious changes to Axis2. Also please note that problem is not just about VFS. It is in fact about all the transports you have mentioned above. So clearly these 2 services are not working with any transport other than HTTP/S. Since the services are not shown in the UI, user cannot really change this behavior for these services either. So IMO better to restrict these services to HTTP/S. Thanks, Hiranya thanks, Amila. thanks, Amila. Thanks, Hiranya If you remove that you should get this error with other Admin services as well. thanks, Amila. Thanks -- 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 ___ 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org
Re: [Carbon-dev] QueueService and MessageQueue
On Sun, May 8, 2011 at 10:13 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sun, May 8, 2011 at 7:43 AM, Amila Suriarachchi am...@wso2.com wrote: On Sun, May 8, 2011 at 12:08 AM, Afkham Azeez az...@wso2.com wrote: On Sun, May 8, 2011 at 12:02 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, May 7, 2011 at 10:59 PM, Amila Suriarachchi am...@wso2.comwrote: On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, Can somebody please explain what QueueService and MessageQueue are? These services shout whenever I enable some transport in the ESB: [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to configure the service QueueService for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the vfs transport for the service QueueService, because it is not configured properly for the service [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to configure the service MessageQueue for the VFS transport: Service doesn't have configuration information for transport vfs. This service is being marked as faulty and will not be available over the VFS transport. [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the vfs transport for the service MessageQueue, because it is not configured properly for the service The reason is we have not limited the transport to https unlike in other admin services. So then I guess it's a bug, isn't it? We have fixed all other services (Version, HelloWorld etc) by exposing them over HTTP/S only. No! What if users deploy their own services? Their services will automatically be marked as faulty, and none of their services will work OOTB. Why don't we make VFSTransport optional? +1. We want SQS services expose what ever available transport since it is not just a service used for Admin Console. Yes, it won't work with transports like SMTP, JMS, VFS without having explicit parameters set. In that sense one can argue every one suppose to specify all the transports that service can actually work with. But as Azeez pointed out normally Axis2 service authers don't specify those and hence all those services are marked as faulty. So making VFSTransport optional would be better solution. And how do we do that? By default Axis2 exposes services over all available transports. If a particular transport is not configured for a service, above warnings are shown. I think service also gets marked as faulty in this case, but other active transport bindings continue to work (they don't malfunction as Azeez has mentioned). You will see this behavior in all the releases we have done so far and I don't think this can be fixed without some serious changes to Axis2. I think making services as faulty happens at the base transport module. So we may be able to check a parameter to make a service faulty. Also please note that problem is not just about VFS. It is in fact about all the transports you have mentioned above. So clearly these 2 services are not working with any transport other than HTTP/S. Since the services are not shown in the UI, user cannot really change this behavior for these services either. So IMO better to restrict these services to HTTP/S. yes we can make this service only for http/https. But that is not the problem. Is it correct make services, which have not configured to these transport faulty? thanks, Amila. Thanks, Hiranya thanks, Amila. thanks, Amila. Thanks, Hiranya If you remove that you should get this error with other Admin services as well. thanks, Amila. Thanks -- 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 ___ 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:
Re: [Carbon-dev] QueueService and MessageQueue
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. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
