XFire

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1-RC1
• Fix Version/s: 1.1
• Component/s: None
• Labels:

  None

It seems I am dedicated WsGen taks tester

Anyway, generated methods have arguments a bit different than it should.
String ObjectRef is present everywhere, and argument names and order are not right. It seems that WsGenTask doesn't follow WSDL "instructions" for operation arguments given in <message> tags, such as :

<message name='IpChargingManager_createChargingSession'>
<part name='appChargingSession' type='csxsd:IpAppChargingSessionRef' />
<part name='sessionDescription' type='osaxsd:TpString' />
<part name='merchantAccount' type='csxsd:TpMerchantAccountID' />
<part name='user' type='osaxsd:TpAddress' />
<part name='correlationID' type='csxsd:TpCorrelationID' />
</message>

Generated arguments ahould be part names as visible above.

I attached WSDL, and one example class generated by Axis (it's OK there) and XFire.

1. 

   cs.wsdl

   08/May/06 1:28 AM

   103 kB

   Vjeran Marcinko

2. 

   IpChargingManager-Axis.java

   08/May/06 1:28 AM

   2 kB

   Vjeran Marcinko

3. 

   IpChargingManager-XFire.java

   08/May/06 1:28 AM

   4 kB

   Vjeran Marcinko

• Assignee:

  Dan Diephouse

  Reporter:

  Vjeran Marcinko

• Created:

  08/May/06 1:28 AM

  Updated:

  09/May/06 3:13 PM

  Resolved:

  09/May/06 3:13 PM