Ruwan I think what we do right now is the same that a vanilla Axis2 would do.. I am not sure if axis2 supports a ?info though, can we check on axis2-dev/user too?
thanks asankha Ruwan Linton wrote: > Hi all, > > For the moment if we browse to the service path (for example if we > have a proxy service named xxx, then this path is > http://{host}:{port}/soap/xxx), in other words if we do a GET request > on the service path synapse displays the service information as pure > HTML content. > > Rather than directly displaying these service information on the > service path what if we keep that path separate and use ?info filter > to retrieve the service information (i.e. > http://{host}:{port}/soap/xxx?info will display the service information) > > May be we can define a configuration point on which we can define what > will be available under the service path (it can be the service WSDL > or the service info or else any other thing, if you define a filter). > At the same time we can keep the ?wsdl, ?policy and the ?xsd like > filters also configurable so that one can define what each of these > would do. I think this adds better flexibility and control over the > GET request processing. > > WDYT? > > Thanks, > Ruwan > > -- > Ruwan Linton > http://www.wso2.org - "Oxygenating the Web Services Platform" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
