Aegis ignores mapping file attributes for services.

Aegis does not generate a WSDL for services correctly based on the informatin in the service aegis.xml file. For example, if I have the service interface:

public interface MyService {
Collection findSomething(Criteria c, OptionalSpecification os, Date startDate, Date endDate);
}

then Aegis will always map the first two parameters as "nillable" in the WSDL. The last two start and end date parameters are always listed as required in the WSDL. This happens regardless of the values specified in the .aegis.xml file.

I want to be able to specify in the .aegis.xml file for the service that the first parameter is not nillable, the second is nillable, the third is not nillable and the last is nillable (or some other variation thereof). At present this is not possible. I would expect, from the published documentation, that the MyService.aegis.xml file below would do the job but it does not:

<mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xfire.codehaus.org/schemas/1.0/mapping.xsd">
<mapping>
<method name="findSomething">
<parameter index="0" mappedName="criteria" nillable="false"/>
<parameter index="1" mappedName="optionalSpecification" nillable="true"/>
<parameter index="2" mappedName="startDate" nillable="false"/>
<parameter index="3" mappedName="endDate" nillable="true"/>
<return-type mappedName="foundThings"/>
</method>
</mapping>
</mappings>