Nishant Joshi wrote:
Many thanks Simon, It was really very helpful to me and you have cleared
many questions
Now some more queations from my side (Again) :-)
First of all i'll explain what i have understood from your explanation...
Only Tuscany client is option for callback service. (though for other client
i have to right my own callback protocol)
From client side i have to pass callback uri and some other info to service
and service will feedback me on that uri, so my client is also exposing wsdl
and i have to put it into any server say Tomcat correct?
You don't need to do anything to make this happen. Tuscany contains an
embedded Web server (it can use either Tomcat or Jetty) so all this should
happen under the covers. The only thing you might need to watch out for
is port conflicts between the Web server you are using and the embedded
Web server that Tuscany is using.
I want to give a scenario...Say order service
client makes an order call(assume client is part of a larger system), and
doing some other activity.On service side it takes time to generate status.
Now on client side what i have done when my client need the result, i m
polling to check the status and wait till client get the result.But in
callback scenario client have some callback interface.
So should my client invoke method on same (client) side callback interface..
like polling(this is on client side only... no need to call service)... or
service will invoke my client by callback uri?
so my confusion is from client side what action should be taken, as in
polling, client is calling service, now service is callingback to client? so
how should client come to know about callback result?
I think this depends on what kind of client you have. If the client is
Java code running in a Tuscany environment, then it can set up an SCA
callback interface and Tuscany can call this interface directly to
provide the result.
If the client is not able to receive SCA callbacks directly, but is able
to run in a multi-threaded environment and receive asynchronous input,
then an SCA callback can be set up and this can drive the asynchronous
notification of the client.
If the client is not able to receive SCA callbacks directly and is only
able to run in a single-threaded environment, then it would need to do
polling as there is no way for it to receive asynchronous input.
Can you say more about the client environment that you are using? With
more details of this, I would be able to give a more specific answer.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
