I was able to cobble together something that works...I used a TestContextInitializer class I found in the jdbc control test suites, but I will wait for your checkin.
thanks, steveh. On 12/7/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > Without writing the code to act as a control container, no. :) > > I've got this ready to go and just need a few minutes to run some > tests and get it committed. Should be able to do that later this > week. > > You'll see the commits@ mail when it goes in. > > Eddie > > > On 12/7/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > Thanks for the roadmap here. > > > > I am putting this tutorial together right now, and am at the JUnit step. > > > > Is there some way to complete this step without the JUnit test container > for > > controls? > > > > On 12/1/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > > > > > Steve-- > > > > > > Personally, I think that the Controls Tutorial will be more > > > descriptive if it focuses solely on the end-to-end process of writing > > > a Control. For example: > > > > > > - authoring the Control's source artifacts > > > - building the Control > > > - packaging the Control into a JAR file > > > - authoring a JUnit test for the Control > > > - testing the Control > > > > > > Today, most of the Controls Tutorial is about how to setup, build, and > > > deploy a NetUI-enabled web application. While we should certainly > > > have examples and documentation about how to use a Control from a Page > > > Flow, it's probably more interesting to focus on the end-to-end cycle > > > of building a Control JAR file. > > > > > > Note, this requires that I (finally!) commit the JUnit test > > > container for Controls. Believe it or not, I've got that "svn add"ed > > > locally and should have that done soon. Then, it's just a matter of > > > rewriting the tutorial. > > > > > > Thoughts? > > > > > > Eddie > > > > > > > > > > > > On 11/30/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > > > Hi Eddie and all: > > > > > > > > Eddie, yesterday you mentioned to me privately that you'd like to > see > > > the > > > > control tutorial not use a page flow as its > > > testing environment. Instead, > > > > the page flow should be replaced with some sort of unit testing. > > > > > > > > Could you say more about what you are looking for here? > > > > > > > > thanks, > > > > steveh. > > > > > > > > > > > > > > > > On 11/29/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi all: > > > > > > > > > > Seems like a good time to clean up and amend the 1.x docs. > > > > > > > > > > So here is a general call out for doc needs and wish lists for > Beehive > > > 1.x > > > > > . > > > > > > > > > > Are there any big, glaring problems with the current doc? > > > > > Any little issues that have fallen through the cracks? > > > > > > > > > > Please respond with what you would like to see in the Beehive > 1.xdocs. > > > > > > > > > > thanks, > > > > > Steve Hanson > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
