[ http://jira.codehaus.org/browse/XFIRE-388?page=all ]
Dan Diephouse closed XFIRE-388:
-------------------------------
Resolution: Fixed
All fixed in SVN. I will try to get out a build soon.
> WsGen task generates operation arguments wrongly
> ------------------------------------------------
>
> Key: XFIRE-388
> URL: http://jira.codehaus.org/browse/XFIRE-388
> Project: XFire
> Type: Bug
> Versions: 1.1-RC1
> Reporter: Vjeran Marcinko
> Assignee: Dan Diephouse
> Fix For: 1.1
> Attachments: IpChargingManager-Axis.java, IpChargingManager-XFire.java,
> cs.wsdl
>
>
> 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.
--
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
