Hi,
We should try to provider a better error/info message for this case if we can - as it can be confusing at first what name to use in the url. The implementation suggested would have to change if we wanted to add/override existing web method attributes (or others) already defined on a class. What does everyone think about such a feature?
Mark
BTW, I think we can provide some generic functionality for the exporter such that we can define things like
<property name="MethodAttributes">
<dictionary>
<entry key="FindAll" value="WebMethod(Description = 'Test', TransactionOption = TransactionOption.RequiresNew ), SoapDocumentMethod(Action="urn:myservice:finall")
"/>
</dictionary>
</property>
I'm sure it can be cleaned up even more XML wise, but using the expression evaluator and a simple parser for the value, we could probably implement this and then not be in a catchup game to regardnig all the attributes that can be used. This should be generally useful for WCF, EnterpriseServices, etc.. I'll post on the dev list - just wanted to get it out there.
Hi Mark,
we can already do that (see SpringAir example) :
<!-- Web service definitions -->
<object id="bookingAgentWebService" type="Spring.Web.Services.WebServiceExporter, Spring.Web">
<property name="TargetName" value="bookingAgent"/>
<property name="Name" value="BookingAgent"/>
<property name="Namespace" value="http://SpringAir/WebServices"/>
<property name="Description" value="SpringAir Booking Agent Web Service"/>
<property name="Methods">
<dictionary>
<entry key="SuggestFlights">
<object type="System.Web.Services.WebMethodAttribute, System.Web.Services">
<property name="Description" value="Gets those flight suggestions that are applicable for the supplied trip."/>
</object>
</entry>
<entry key="Book">
<object type="System.Web.Services.WebMethodAttribute, System.Web.Services">
<property name="Description" value="Goes ahead and actually books what up until this point has been a transient reservation."/>
</object>
</entry>
<entry key="GetAirportList">
<object type="System.Web.Services.WebMethodAttribute, System.Web.Services">
<property name="Description" value="Return a collection of all those airports that can be used for the purposes of booking."/>
</object>
</entry>
</dictionary>
</property>
</object>
But as you pointed out, we can make configuration less verbose and easier to read.
I was thinking to xsd schema configuration parser for that, we should get something like this :
<ws:exporter name="bookingAgentWebService" targetName="bookingAgent"
namespace="http://SpringAir/WebServices"
description="SpringAir Booking Agent Web Service">
<methods>
<entry key="SuggestFlights">
<ws:webMethod Description="Gets those flight suggestions that are applicable for the supplied trip."/>
</entry>
<entry key="Book">
<ws:webMethod Description="Goes ahead and actually books what up until this point has been a transient reservation."/>
</entry>
<entry key="GetAirportList">
<ws:webMethod Description="Return a collection of all those airports that can be used for the purposes of booking."/>
</entry>
</methods>
</ws:exporter>
Or with your example :
<entry key="FindAll">
<ws:webMethod Description="Test" TransactionOption="RequiresNew" />
<ws:soapDocumentMethod Action="urn:myservice:finall" />
</entry>
- Bruno