axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Gordie <Alan_Gor...@payformance.com>
Subject RE: Patch for AxisServlet.java for browsing services/operations/p arams
Date Thu, 04 Apr 2002 16:56:21 GMT
Steve,

I agree.

> * add support for generating WSIL (need a "published" attribute at the
> ServiceDesc level...also in WSDD)

The "published" attribute that I mentioned will allow you to suppress
browser-based browsing and WSIL listing of individual services.  This will
most likely be an optional parameter in the WSDD entry for each service.

 <service name="PrintService" provider="java:RPC">
  <parameter name="allowedMethods" value="printFromFileToSCPJAsynch"/>
  <parameter name="className"
value="com.payformance.nps.soap.services.PrintService"/>
  <parameter name="published" value="false"/>  
 </service>  

I propose that we also add parameters to the globalConfiguration in the
server-config.wsdd file for controlling the visibility of the publishing
mechanisms.

 <globalConfiguration>
  <parameter name="WSIL.enabled" value="false"/>
  <parameter name="serviceManager.enabled" value="false"/>
  ...

Later, as the security components evolve, we could tie this to ACL's for
fine-grained control.

Comments?

Alan

-----Original Message-----
From: Steve Loughran [mailto:steve_l@iseran.com]
Sent: Thursday, April 04, 2002 11:18 AM
To: axis-dev@xml.apache.org
Subject: Re: Patch for AxisServlet.java for browsing
services/operations/params



----- Original Message -----
From: "Alan Gordie" <Alan_Gordie@payformance.com>
To: <axis-dev@xml.apache.org>
Sent: Thursday, April 04, 2002 6:17 AM
Subject: RE: Patch for AxisServlet.java for browsing
services/operations/params


> Ivelin,
>
> Thanks for the kind words.
>
> Yes, I am working towards a dynamically generated operation invocation
> mechanism via browser for testing, etc.  However, that is still a long way
> off.  Unlike .Net's consumer page, which works using an HTTP adapter, I'm
> planning to dynamically create a Call object within the servlet based on
> interaction with the user ultimately ending with invocation of that Call
> against the service via SOAP.
>
> If you have any specific suggestions or requests for features in this
area,
> please post them here and I'll be more than happy to add them to the list.

one suggestion: make it easy to turn off.

while this stuff is great for testing, in production i want to make it hard
for people to find what entry points I have, and I dont want GET based
wrappers around SOAP calls.

-steve

Mime
View raw message