[
http://jira.codehaus.org/browse/XFIRE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87959
]
Kevan Dunsmore commented on XFIRE-764:
--------------------------------------
That's useful information but it still leaves the same problem. User object
types also are ignored in service mappings and are always set to be nillable.
That means that if I follow your instructions I'll have a single method
parameter that can be nillable which is incorrect. Following my example from
above, I'd have something like this:
public interface MyService {
Collection findSomething(MyServiceFindSomethingParameterConglomerate
parameters);
}
<mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://xfire.codehaus.org/schemas/1.0
http://xfire.codehaus.org/schemas/1.0/mapping.xsd";>
<mapping>
<method name="findSomething">
<parameter index="0" mappedName="parameters" nillable="false"/>
<return-type mappedName="foundThings"/>
</method>
</mapping>
</mappings>
Which will still generate a WSDL saying that "parameters" may be null.
Do we have any ETA on a fix for this? I appreciate the work that you guys do
(XFire is cool) but this does seem like a pretty big hole to me since it always
results in WSDLs that are incorrect.
> Aegis ignores mapping file attributes for services.
> ---------------------------------------------------
>
> Key: XFIRE-764
> URL: http://jira.codehaus.org/browse/XFIRE-764
> Project: XFire
> Issue Type: Bug
> Components: Aegis Module
> Affects Versions: 1.2.2
> Reporter: Kevan Dunsmore
> Assigned To: Tomasz Sztelak
> Priority: Critical
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
