Use of "action" to link to actual java processor

["David RR Webber \(XML\)" <david@drrw.info>]

Team,

 

I'm doing integration right now using Hermes - and I wanted to have a way of controlling the processing of message types directly from the CPA - to the java handler that processes the content.

 

It occurs to me I could extend the use of the tp:action attribute in the action binding to be the actual name of the java handler - since its just text anyway - the the two can be equivalent - e.g. human readable - machine executable.

 

What do people think here?  Is this total blasphemy - or is this acceptable extension?  Or is there a better way of doing this elsewhere in the CPA?

 

Given that the CPA is private this is something that two participants can share - and especially if they are sharing open source such as Hermes.

 

Thanks, DW

 

Encl: example CPA fragment -

 

      <tp:CanSend>
          <tp:ThisPartyActionBinding tp:id="companyA_ABID1"
            tp:action="Purchase_Order_Request_Action()"
            tp:packageId="CompanyA_Packaging">
            <tp:ChannelId>asyncChannelA1</tp:ChannelId>
          </tp:ThisPartyActionBinding>
          <tp:OtherPartyActionBinding>
            companyB_ABID1
          </tp:OtherPartyActionBinding>
        </tp:CanSend>
        <tp:CanReceive>
          <tp:ThisPartyActionBinding tp:id="companyA_ABID7"
            tp:action="Purchase_Order_Confirmation_Action()"
            tp:packageId="CompanyA_Packaging">
          ...
        </tp:CanReceive>