Yes, I was thinking of my initial resuscitation as a starting place for a dedicated JdbcControl sample, which would evolve going forward. I will take you list above as a good roadmap for sample.
I never thought of going 'out of container' with a jdbc control, and have a bunch of questions. What does that mean from an app architecture point of view? By 'out of container' do you mean out of the web container, but in a Java container? Why would a user want to take the control out the container? On 12/7/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > Steve-- > > Having that sample would be great, though we've also got JdbcControl > samples in the Petstore which basically demonstrate the same things. > > Might be more interesting to have a focused JdbcControl sample that > runs outside of the container and demonstrates things like calling > stored procedures, custom ResultSet mapping, SQL escapes, stored > functions, etc. We could even use Derby to demonstrate all of that. > Could also demonstrate out-of-container testing, etc. > > Probably more didactic than another web application. > > If the system-controls/samples/jdbc sample were brought back, your > list would be a good place to start in addition to moving it into the > trunk/samples directory. > > Thoughts? > > Eddie > > > > On 12/7/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > Hey all: > > > > There are some samples at /trunk/system-controls/samples that could use > some > > resuscitation. > > > > Does anyone object to me fixing up the database control? > > > > Seems to me a fix up requires the following: > > > > (1) Change the directory structure to match the current netui-blank > > structure > > (2) Change the .jpf file extensions to .java. > > (3) Write doc for the sample > > (4) Edit build.dist to ship the sample > > > > Am I missing anything else? > > > > -Steve Hanson > > > > >
