I agree, it is important to make sure the WSDL->JCX mapping functionality is fully tested.
Looking at the ExtensionMaker class in the webservice control it appears that it is using wsm to load and provide the model for the the wsdl, it then emits the jcx by traversing that model. Are there currently any tests in wsm which verify the parsing of the wsdl and the resulting model are correct? It seems like those tests should be part of the wsm drt suite. At this point I would lean towards creating some of our own WSDLs for testing as opposed to getting some big complex ones from the web. I'll do a bit of work on this and see what I can come up with. - Chad On 6/7/05, Daryoush Mehrtash <[EMAIL PROTECTED]> wrote: > We needed this yesterday :) > > Service control performs two main functions. Generates JCX based on > WSDL, and use the WSDL and JCX interface to communicate with the > service. > > I think the first test in service control should cover the JCX > generation. The idea is that if the JCX that the service control > generates is correct, we are a long way there to be able to work with > the service. Understanding the WSDL is the main complexity in service > control. > > For JCX-generation phase of the testing we should not rely on the > wsm-samples like web services. We have two choices either create > complex WSDLs by hand that cover complex cases, or alternatively select > a set of diverse WSDLs from the existing services and make sure the JCX > file is accurate. The test should generate the JCX for each of the > wsdls and the validation should validate the JCX method signatures, not > to send a message to it, just validate the JCX signature. > > Once we are confident that we have good handle on WSDL->JCX mapping then > we should look at the messages where we need a running server. For this > the wsm-sample would be a good starting point. > > Daryoush > > > > -----Original Message----- > > From: Chad Schoettger [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 07, 2005 11:29 AM > > To: Beehive Developers > > Subject: The web services system-control test suite > > > > I was looking at the webservice system-control's suite of tests and > > noticed that there is only minimal code/feature coverage. I thought > > I'd spend some time adding additional tests to try to get more > > complete code/feature coverage for this control. > > > > I was thinking of adding a bunch of new webservices and corresponding > > webservice controls to ensure that the control can work with the full > > range of possible WSDL settings (such as encoding styles, message > > formatting styles, parameter styles as well as parameter modes, etc). > > > > The test webservices may end up looking something like some of the > > samples in the ws-samples area but specifically used for testing the > > service control. > > > > Does anyone on this list have any thoughts on other additional tests > > which should go into a test suite for the webservice control? > > > > - Chad > > >
