Ali We are just in the process of updating and improving our SOAP/JMS support.
So we appreciate any advice you can give us. We will look at the username/password and connection pooling issues. If you have specific ideas on how we can implement some of this, we appreciate that too. Maybe you should join us over on axis-dev as this is becoming a code-focussed discussion! Paul On 7/3/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
Hi all, I haven't seen connection pool in the new JMS implementation. However, the current JMS implementation uses connectors within which vendor-specific pool is checked and created if found none. Also, as far as I've seen from the new JMS implementation code, each time a request is made - Initial context is created - Connection factory is retrieved from the JNDI - A new connection is created Are these, somehow, normal/expected behaviour? If yes, shouldn't we expect it become slower than the current implementation? Could someone please shed some light on JMS implementations? Regards, Ali Sadik Kumlali --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
