Hi devs, According to the current design of Axis2, faulty services are detected only by the relevant deployer. In order improve the faulty services handling, I need to maintain more information about the faulty services such as, exact error, axis service object. This information is needed when deploying faulty services as "normal" services. With the current desing, this change has to be implemented in every deployer which uses services.xml file or any other descriptor to engage modules or add specific transports. So I think the best option whould be to do this in a single place. WDYT?
Thanks Sameera On Wed, Mar 11, 2009 at 8:59 AM, Sameera Jayasoma < [email protected]> wrote: > Hi devs, > > Current behavior of Axis2 does not allows a faulty service to become a > "normal" service. If a service becomes faulty, it remains there forever. > There is no way for a faulty service become a "normal" service, even after > its dependencies are available. > > Axis2 service becomes faulty if, > > the referenced Axis2 module is not available, > the referenced transport is not available, > there are classloading issues, > the services descriptor file has errors in it, etc.. > > For an example, Service X is added as a faulty service because the > referenced module M has not been deployed at that time. But after the module > M is deployed, service X cannot be considered as faulty anymore. Hence the > service X should be deployed as a "normal" service. This kind of scenarios > can occur when we run Axis2 in an OSGi environment. Services and modules can > come as an OSGi bundles and one can't really predict the order of these > bundles. > > I would like to improve the faulty services handling aspect in Axis2 to > cope with these situations. > > Thanks > Sameera > -- Sameera Jayasoma Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://tech.jayasoma.org
