I agree that JSP pages are a good tool to demonstrate the ease of control integration. But from testing perspective, where you need programmatic interface, the JSP model won't work.
I think a unit test strategy is important in the blanks templates. After you install the blank control template, you should be able to view a JSP page that calls the control, and also be able run a unit test to verify the control from a test case. The test case is right now missing from the controls blank template and should be added. But the current model is rather complex. The current model is to use page flow to create an action for each test case. Each test case action returns the result of the test as a string of success or failure. On the client side the test code starts up the server, and sends the URL of the action to the server and examines the result string. To create a new test case you need to create a new action and client side call to the action. I would much prefer the JUnit container, but short of that, a web service model would greatly simplify access to the control, and thus would make the unit testing a lot more intuitive. daryoush -----Original Message----- From: Kyle Marvin Sent: Friday, October 29, 2004 7:21 AM To: Beehive Developers Subject: RE: Blank controls app template checked in You can use Controls inside a JSP page by simply using the <jsp:useBean> tag... I think this is probably the simplest newbie way to play around with a control in the servlet container. The Controls tutorial shows how to do this, I believe. Don't think it gets any easier to understand than that :) To be clear though, the point of the template is not as a sample... it is a build.xml template for how to build a jar that contains controls, not how to use them. > > As an alternative to the page flow, I like to suggest that > the templates > use web services as their interface to the outside world. > From vantage > point of a newbie, it would be good examples of how to use a > control in > servlet container, and the web service being based on a standard would > be easier to understand than the page flow. > > Daryoush >
