Hi Devs, Currently we keep the servlet transport configuration in the transports.xml file and the other transport configurations in the axis2.xml. We also persist transport configurations to the registry which makes it very confusing and tedious for an average user to understand and manipulate transport settings. We can reduce the complexity by putting service transport configurations in a separate file and not persisting any transport configurations to the registry. Any changes made via the UI will be serialized back to the file. I think it makes sense to have transport configs in a place where it is easy to manually inspect and modify.
May be to keep things clean we can put the servlet transport config in a file named console.xml and put service transport configs in the transports.xml. This will require some changes to the Carbon core. This is just an idea I got while looking at how Carbon is presently organized. WDYT? Thanks -- Hiranya Jayathilaka 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
