Hi Deepal,
On Fri, Jan 27, 2012 at 7:29 PM, Deepal jayasinghe <[email protected]>wrote: > On 1/27/2012 4:43 AM, Sameera Jayasoma wrote: > > Hi Devs, > > Axis2 throws exceptions when the specified transport of a service is not > available. And the service becomes faulty as well. If this service has > specified multiple transports and these other transports are available, > Axis2 should expose the service in other transports, without simply failing > the deployment. > > e.g 1. Service Foo has specified http and https transports. > > <transports> > <transport>https</transport> > <transport>http</transport> > </transports> > > Now We configured Axis2 only with Http transport. When we deploy the > service Foo in Axis2, the default behavior of Axis2 is to fail the service > deployment saying "Https transport is not available.". But my suggestion > is, we should deploy the service Foo in Http transport and display a WARN > message to notify that this service will not be exposed in Https. > > e.g 2. Service Bar has specified https and jms transports. > > <transports> > <transport>https</transport> > <transport>jms</transport> > </transports> > > We configured Axis2 only with Http transport. Now this service cannot be > exposed in either Https or jms. Hence Axis2 should fail the deployment of > the service Bar. > > Thanks, > Sameera. > > [1] https://issues.apache.org/jira/browse/AXIS2-5234 > > What happens if none of the transports are available ? are you still going > to deploy the service ?. > This scenario is explained in the second example. There I've specified https and jms, but both these transports are not available in Axis2. In such situations, we fail the service deployment. Thanks, Sameera. > > > Deepal > -- Sameera Jayasoma Technical Lead WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://tech.jayasoma.org
