[Javascript] struts form using javascript code

[David Lovering]

I actually tried to invoke the thing, and the errors which resulted are consistant with the ones I cited.  Terminology aside (and nobody accuses M$oft of being particularly lucid), when I clicked "Add", it couldn't find the needed reference, and similarly for the Delete key.  Somehow the code stream is broken sufficiently that these references aren't getting included.  As you say, it may not be all that big a deal to fix -- providing that we can put our finger(s) on the part that is interfering with the calls.

-- Dave Lovering
  ----- Original Message ----- 
  From: Chris Tifer 
  To: [JavaScript List] 
  Sent: Wednesday, March 03, 2004 7:12 AM
  Subject: Re: [Javascript] struts form using javascript code


  > the first "gotchas" I found are in the omission of an 
  > include for the driver_new.jsp, the unreferenced 
  > object/function attached to the "Delete" key, 
  > and the non-displayability of the driverDisplay.do file.

  From what I gather, there should be no include to a driver_new.asp. The only reference I see to that is where it tries to direct your browser to it if you click Add.  Also, getCheckedItems() is the function called by the Delete key. It's just down on the bottom.  

  What do you mean by non-displayability also?

  I don't see a bag of worms per se, just a slight error.

  Chris Tifer
  http://emailajoke.com



  ----- Original Message ----- 
    From: David Lovering 
    To: [JavaScript List] 
    Sent: Tuesday, March 02, 2004 7:16 PM
    Subject: Re: [Javascript] struts form using javascript code


    Well, aside from some excitingly dreadful formatting, the first "gotchas" I found are in the omission of an include for the driver_new.jsp, the unreferenced object/function attached to the "Delete" key, and the non-displayability of the driverDisplay.do file.

    I think perhaps we should try to break this down and address each issue individually, rather than diving in and swimming about in all directions.  

    Perhaps "Job #1" should be to check that the various necessary browser functions are enabled, and that all the core code modules are within reach.  After that, I'd look into each individual module and analyze it from an input/output standpoint, and make sure that it is canonically structured, has a front-end exception filter to remove "bad" inputs, and correctly acts on valid data to produce desired output code.

    This is such a bag of worms, I'm not sure where else to start.

    -- Dave Lovering


------------------------------------------------------------------------------


  _______________________________________________
  Javascript mailing list
  Javascript at LaTech.edu
  https://lists.LaTech.edu/mailman/listinfo/javascript
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.evolt.org/pipermail/javascript/attachments/20040303/6f409c35/attachment.htm>