A correction and suggestion.
>3) Call out the usage of the database control in the AddressBookWS >sample docs/description -- ie, it's intended to demonstrate both web >services AND use of controls. Database control is used in the EmployeeWS. The AddressBookWS is just a simple webservice. Suggestion.... I like to suggest we offer the unit test model we have done in the EmployeeWS as model for user to test their control implementations. Background... Axis has tools to generate the client side code, which can also generate unit test cases. The generated Unit test cases works fine for AddressBookWS but was not useful for the EmployeeWS. To call the employee web service you have to follow a sequence of activities (create table, add employee, modify, delete, drop tables) as such the generated unit test cases was not useful. We have created a custom unittest case for the EmployeeWS that is checked in to the distribution. We also have the cient-build.xml to run the unit tests ( Generate the classes based on WSDL, compile code and unit test case, and run the JUnit tests). I think the model we are using in this case would be useful for a control developer. Build file: EmployeeWS/WEB-INF/client-build.xml Client test case source code: EmployeeWS/WEB-INF/client-tests Let me know if you need more information. Daryoush -----Original Message----- From: Steve Hanson Sent: Thursday, November 04, 2004 11:03 AM To: Beehive Developers; Hoi Lam Subject: RE: Alpha docs suggestions These are all great ideas for the site. This week and next I will be polishing the site, and getting as much content as I can "up and live". If anyone out there wants to contribute samples blurbs/descriptions, please send them along. (Ken, I probably won't have time to implement your tutorial suggestion before ApacheCon.) -Steve H. -----Original Message----- From: Ken Tam Sent: Wednesday, November 03, 2004 10:32 PM To: Steve Hanson; Hoi Lam Cc: Beehive Developers Subject: Alpha docs suggestions Hey Steve, Just had some thoughts on things that could be useful to the alpha docs.. 1) Mentioning the "control project" model for using controls (perhaps as a 2nd controls tutorial?) -- ie, using the controls-blank template to create a controls JAR that is then importable in multiple webapps (WEB-INF/lib), and using this to help isolate business logic in controls from presentation logic in the webapp proper. 2) Call out the database control as an example of a reasonably rich control that does something useful and demonstrates how to use things like properties, events and resource management. Hoi, maybe you could provide some help for Steve here? 3) Call out the usage of the database control in the AddressBookWS sample docs/description -- ie, it's intended to demonstrate both web services AND use of controls.
