Topic
2 replies Latest Post - ‏2013-01-23T14:24:53Z by oldandtired
SystemAdmin
SystemAdmin
14225 Posts
ACCEPTED ANSWER

Pinned topic Extending UML-to-WSDL transformation to set message names

‏2012-11-07T16:17:53Z |
I am using RSA v8.0.4 to create WSDLs from our service models.
The current UML-to-WSDL transformation creates element, part, and message names by concatenating the service interface and message names as follows:

<wsdl:message name=
"ClaimInquiryfindClaimRequest"> <wsdl:part element=
"tns:ClaimInquiryfindClaimRequest1" name=
"parameters" /> </wsdl:message> ... <wsdl:portType name=
"ClaimInquiry"> <wsdl:operation name=
"findClaim"> <wsdl:input message=
"tns:ClaimInquiryfindClaimRequest" /> ...

To support our internal standards, we would like this to be just the designed message name:

<wsdl:message name=
"findClaimRequest"> <wsdl:part element=
"tns:findClaimRequest" name=
"parameters" /> </wsdl:message> ... <wsdl:portType name=
"ClaimInquiry"> <wsdl:operation name=
"findClaim"> <wsdl:input message=
"tns:findClaimRequest" /> ...

I have used examples in this forum to create a transform extension modifying the binding operation SOAPAction URI:

<ExtendTransform targetTransform=
"BindingOperationExtensionTransform"> <AddRule id=
"MyBindingOperationExtensionRule" /> </ExtendTransform>

What target and rule type should be used to make the above changes? Or is there a better approach?
Thanks for your help.
Updated on 2013-01-23T14:24:53Z at 2013-01-23T14:24:53Z by oldandtired
  • oldandtired
    oldandtired
    2 Posts
    ACCEPTED ANSWER

    Re: Extending UML-to-WSDL transformation to set message names

    ‏2013-01-23T14:23:56Z  in response to SystemAdmin
    Hi Mark,

    Did you solve your query? We have exactly the same issue and would love to hear if you've already got the solution.

    Thanks.

    Regards,

    Neil
  • oldandtired
    oldandtired
    2 Posts
    ACCEPTED ANSWER

    Re: Extending UML-to-WSDL transformation to set message names

    ‏2013-01-23T14:24:53Z  in response to SystemAdmin
    Hi Mark,

    Did you solve your query? We have exactly the same issue and would love to hear if you've already got the solution.

    Thanks.

    Regards,

    Neil