Thanks for the feedback Indika. I have added a simple fix to this problem in the trunk. In the long run I think we should provide some JMX support for managing proxy services.
Thanks, Hiranya On Tue, Mar 30, 2010 at 8:26 PM, indika kumara <[email protected]>wrote: > I believe it is wrong to deploy an incorrect service ... so , the proxy > should not be deployed ....with new hot deployment support , user can > redeploy at later without restating the server ... or we may be able to > provide JMX MBean to manually redeploy the proxy without restating the > server. May be nice to have a few life cycle states for a proxy ... > > Thanks > Indika > > On Tue, Mar 30, 2010 at 1:16 PM, Hiranya Jayathilaka <[email protected] > > wrote: > >> Hi Devs, >> >> Synapse proxy services currently support a parameter named >> 'enablePublishWSDLSafeMode' which allows a proxy service to be loaded >> despite the availability of the WSDL. This parameter causes a dummy Axis >> service to be created with the default 'mediate' operation if the specified >> WSDL cannot be found for a proxy. IMO we should change this behavior to >> simply ignore the faulty proxy service and proceed with the startup. In >> other words it should not deploy the proxy service at all. Otherwise the >> clients will see it as the service interface being changed. WDYT? >> >> Thanks >> -- >> Hiranya Jayathilaka >> Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
