<see below> > One of the reasons standards exist is to avoid vendor lock-in. > It is a good architecture goal to avoid vendor lock-in and > write code to > the specs/standard apis.
Absolutely. For the implementation, I would agree whole-heartedly. I guess where I'm missing the point is where you say ... > Wouldnt it be nice to be able to switch to Axis > without a huge amount of work (ie without changing a lot of your code) > because both the original SOAP engine you were using and Axis > implement > the SAAJ/JAX-RPC specs. Is it that Axis provides a communication style (message) that isn't part of the specs? If that's the case, then that is definitely an issue. I think my confusion is being compounded by an article I just read (http://www-106.ibm.com/developerworks/library/ws-castor/) that very strongly promotes this exact style. In fact, I was going to recommend it as a solution to the original question, but after reading the follow-up posts, I saw that that solution was being specifically discarded. Is it a non-standard solution? Are there interop issues with it? Or is it just the "axis" way of doing things and if one where to change to another implementation, they would need to rebuild based on that implementation's preferred methodology? Can you tell I like to ask questions? heh > It doesnt seem to me that web services are quite at this level of > maturity but that should be the goal. And a good one at that! Thanks, Gene
