Hi 竹伟饶,
> 1. If the coordination protocol type is "PC".Then,How can I control > the participant to do some orders?(e.g. send completed message).Do I > must write the "participant.tellcompleted " code in class which > implements BAwPCParticipant( e.g.RentACarParticipant)? > Is there any other > method.Because I want to use the button on the web trigger the sending > of message "completed".Or, is there something like "proxy" API which can > help me control participant's order. The BAwPCParticipant class is already a proxy. It runs on the "client" (or service) and handles the communication to the coordinator. There is another way to deliver the Completed message: invoke the coordinator service directly and use the Completed operation specified by WS-BA. (This is exactly the same thing the BAwPCParticipant does when you invoke tellCompleted() ). > 2. I want ask something about your implement of BA.I think BA can > help sovle LongTime Bussiness activity.Then where can I see the function > of kandula solving the LongTime qustion.For example.For > example,Participant P1 will run 10 days in order to get the result.When > P1 get the result ,it will notify Participant P2 to de other task.Do the > Coordinator can implement the function--after P1 finish the job,nofity > P2 to do job? Kandula is a transaction manager and handles different transaction types, one of them being long running business transactions defined by WS-BusinessActivity. This is all on the "transaction" layer. What you describe are requirements that are on a different layer. Have a look at Orchestration and Choreography specifications - these do exactly what you describe. > 3.I always confuse the coordinator.Can you tell me what do the > coordinator cootdinate?If I don't using coordinator specification.Just > let the applicition the state.What is the difference distinguish using > kandula implement my application. I'm sorry, I don't quite understand your question. But I guess the following illustration might clear things up: In any WS-Transaction transaction scope there live three roles: - the Initiator, being the one who created the transaction - the Participants, being ressources or services that are called by the initiator - the Coordinator, being the entity that connects the parties. These entities use different protocols to communicate: Coordinator <-> Participants: WS-Coordination + WS-BusinessActivity Initiator <-> Coordinator: WS-Cooordination + WS-BusinessActivity-Iniatitor -hannes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
