JBossDeveloper

In the case of web services transactions, the JBoss Transaction XTS component has a context handler, com.arjuna.mw.wst.client.JaxWSHeaderContextProcessor, so there is nothing for me to write. On the other hand, if I use Smooks, it is not so obvious how to define the smooks-handler. I want to add something like the following:

<wscoor:CoordinationContextType xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
<wscoor:Identifier>urn:7f000001:cfcd:483f0ffb:2e20</wscoor:Identifier>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsba/AtomicOutcome</wscoor:CoordinationType>
<wscoor:RegistrationService>
<wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/xts/soap/RegistrationCoordinator</wsa:Address>
<wsa:ReferenceParameters xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj">7f000001:cfcd:483f0ffb:2e20</wsarj:InstanceIdentifier>
</wsa:ReferenceParameters>
</wscoor:RegistrationService>
</wscoor:CoordinationContextType>

where the content is dynamic (and can be found in the ESB Message).

Thanks, I will look for your updates in a couple weeks.

I am having a bit of a problem getting my quickstart to run. My problem is in the parameter mapping. It is not clear to me what the WISE SOAP Client expects. There appears to be an expectation that there will be a params map (as with the standard version of SOAPClient action). When is a SmooksRequestMapper required? Looking at the code it appears it defaults to null if you don't have one, But when I don't configure one I get IllegalArgumentExceptions wrong number of parameters.

Thanks,

Jeff

"maeste" wrote:
I know there is a lack in development cycle, wise action would need a configurations generator utility. I hope I could work on it soon.

Can we look at integrating your current code into the trunk for the upcoming release? Is there anything that you need to tidy up as it currently stands?

I have committed my quickstart webservice_wstransaction_ba to your workspace. It has a custom action "RequestMapper", that puts the parameters for the ws invocation into a map. After I committed it I realized my error. With the original soapclient, it used OGNL, and my mapper specified:

 requestMap.put("bookSeats.how_many", reservation.getRestaurantSeats());

 requestMap.put("how_many", reservation.getRestaurantSeats());

<property name="custom-handlers" value="com.arjuna.mw.wst.client.JaxWSHeaderContextProcessor" />

I have a requirement to add SOAP header as shown below, while making a SOAP call using SOAPClient action. My problem is all the information I need to build the header is located in the jboss-esb.properties file and in the parameter map. Parameter map object for building the SOAP Body doesn't contain this information. My question is how I should make this happen using SOAPClient action. I looked at the given examples and it looks like there is a provision for smooksHandler config to create SOAP Headers but not getting any clue.

<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Header>
    <UserAuthInfo xmlns="http://realpage.com/webservices">
      <UserName>string</UserName>
      <Password>string</Password>
      <SiteID>xxxxx</SiteID>
      <PmcID>xxxxx</PmcID>
    </UserAuthInfo>
  </soap:Header>

I am also using SOAPClient. I dont want hardcoded parameters in jboss-esb.xml. I need to update header (like SOAPAction) programatically.

Did you solve this problem?

Regards

Sukhdev