Cathal said: > We are currently deploying axis2 in Websphere 6.1. We wish to use the jms > transport. However axis2 fails to start because it uses forbidden api's.
I don't have an answer, but I am very interested in hearing about how best to do this - I posted a similar query on 30 Jan. > Initial research shows the following possibilities: > 1) Use MDB's (not ideal) > 2) Change the axis2 code itself and make a synchronous MessageConsumer.receive call and poll for messages A third option: 3) Run axis2server.bat as a separate process outside of the app server. We're going to explore the performance/scalability implications of this option, but it certainly doesn't seem the most elegant of solutions. -- George --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
