Hey folks, I'm wondering if someone can point me in the right direction. I've not really developed web services much other then the intro axis2 code generation/simple comms back and forth. Ok here's the task I have. I have to deal with a messaging protocol that looks like this:
request->my web service ack<-my web service response<-my web service The request,ack, and response are standardized xml messages from a defined protocol that I have to work with. What I have working right now is the request and ack response (standard in/out messaging) via axis2 and standard HTTP. What I'm trying to figure out is how to design my response. I'm going to have a lot of inbound messages so I will need to make this a multithreaded app. I'm thinking of having a thread pool to handle the inbound messages (need to research this more) and send responses to the originating WS (messages contain the response address) as I process them. The response has be to be sent within 30 seconds, which should be ok as there it is simple processing/persistance. What I'm wondering is if there's a response transport solution via axis2 or should use a standard http sender object? Does my design sound alright or is there something built in to axis2 that will make my life easier? Thanks in advance for any feedback and please send me links to good articles and tutorials if you have them or find them. many thanks, Eric -- View this message in context: http://www.nabble.com/Axis2-newb-tf4339167.html#a12360295 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
