Hi Dasarath: > I presume you are running your client as a standalone > application-- correct? > the commit/rollback operations wait for the COMMITTED/ABORTED > messages from the > coordinator. However, a standalone application cannot receive > these messages. > So the solution is to run your client inside a container like > Tomcat where > kandula has been deployed. That's what I've done in my > example code. Whenever, > we send an async message to which we expect a reply, kandula > creates a dynamic > endpoint-- axis2 does this automatically but for now we have > to do it our > selves on axis1.x.
This could also be solved in 1.X by spinning up an instance of SimpleAxisServer in your application, right? --Glen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
