|
Hello Soniya,
If you are not using the SOAPHeader or attachments or nested structures then there should not be any issues. But if you are planning to use SOAPHeader or attachments then sometimes it get trickier. If your web services use SOAP Headers or attachments then the WSDL emitted by Axis is often not correct. Axis does not display the SOAP Header information in WSDL, I tried all the possible ways for doc-lit type of service without any success. Also if your web service sends/receives the attachments MIME/DIME then the WSDL generated by Axis is incorrect.
Though there is acceptable workaround for these issues.
Hope this helps.
Thanks, Shrikant Wagh QA Lead, HPP/Eprofile, HP
For those who are interested in Web Services testing: ----------------------------------------------------- I found that WebServiceTester from Optimyz software is a very good tool for testing any types of web services, and I'm great fan of this tool. It supports all types of web services, and all simple and complex types and it very usable than any other tool in the market I ever used/evaluated. It automatically generates the SOAP requests and invokes the intended web services. It can perform functional, regression and load testing of web services. Result analysis and status reporting is just wonderful. I'll highly recommend this tool for testing web services, saves lots of time and efforts in testing web services. For more information visit http://www.optimyz.com.
DISCLAIMER ================================================================ THESE ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE INFORMATION PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE I/HP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
=================================================================
-----Original Message-----
Hi All,
I have been using Apache software for a long time and am very happy with it.
But my management has strong concern's about this. Their main question is "if we run into a really critical problem on client side, how do we support it?".
I have not seen anything in the newsgroups where people had major problems with the software.
Have anyone experienced any critical problems in production environment?
Any opinion on this question?
Thanks, Soniya |
Title: Message
- apache software Shah, Soniya M. [RA]
- Re: apache software __matthewHawthorne
- RE: apache software Galbreath, Mark A
- RE: apache software Shah, Soniya M. [RA]
- Wagh, Shrikant
