Asankha and all synapse-devs, It seems like the axis2 community is neutral about this. AFAIK, axis2 does not display anything if you browse to the exact service path using a browser (GET request on service path), and their also having a ?info filter and it displays the service information.
I think it is better to go with the ?info filter to display the service information for synapse. If no body objects I will take it as confirmed. Now the problem is what do we display on the service path if the user has not specified any thing (I am going to add a configuration point where the user can configure what to display on the service path, it can be wsdl, service info or any thing that exists as a filter). Axis2 does not handle this request; and the web container on which axis2 is deployed (eg: tomcat) throws an error on browsing to the service path which is not acceptable at least for synapse :) IMHO. WDYT? Shall we take it as service information or else wsdl? Thanks, Ruwan On 12/11/07, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Hi axis2 folks, > > We (synapse-dev) is in the process of doing some refactoring on the GET > request processors. For the moment we do provide a service information html > page on doing a GET request on the service path and discussing to add a > ?info filter for that and keep the original service path for any other thing > (may be we can provide a configuration point so that user can configure that > path to provide the wsdl of the service instead) > > What is the behavior of the axis2 in this service path navigation through a > browser (or else doing a GET request over the service path) and what do you > guys think about this improvement? > > Thanks, > Ruwan > > On Dec 10, 2007 11:52 PM, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > > > 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] > > > > > > > -- > Ruwan Linton > http://www.wso2.org - "Oxygenating the Web Services Platform" > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
