I got it worked out. After doing some careful dumping of data from the request object and running the jsp through a syntax checker I got it to work. It seems that I had placed some spaces in the values that were in the request object along with some small issues with the jsp/html stuff. Once I got those items addressed, then it worked.
Thanks for the help and the ideal for the template. I think we might adopt it as a standard practice. David Boyd _____ This mailbox protected from junk email by Matador from MailFrontier, Inc. http://info.mailfrontier.com -----Original Message----- From: Michael Rothrock [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 4:42 PM To: Jetspeed Users List Subject: Re: Anyone using displaytag lib with jetspeed You've reached the limit of my knowledge. Hopefully someone who's been at it longer will step in at this point. -- Michael On 5/4/04 1:54 PM, "Boyd, David" <[EMAIL PROTECTED]> wrote: > Well, I pulled out the displaytag lib stuff, left in jstl items, and things > work, that is the doOwn method is called. So there is something strange > going on with the displaytag and working with it. > David Boyd > > _____ > > This mailbox protected from junk email by Matador > from MailFrontier, Inc. http://info.mailfrontier.com > > > > -----Original Message----- > From: Boyd, David [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 2:55 PM > To: 'Jetspeed Users List' > Subject: RE: Anyone using displaytag lib with jetspeed > > I understand the methods of testing. > > I have my doOwn action surrounded by try - catch statements. I have a > debugger statement at the top of the method, but that is not even being > called. I wrote in your template stuff to see if that would catch anything, > and it did not. Its like the doOwn action is being completely ignored now. > This was not the case before I put in the displaytag lib. And I am unable > to get the debugger to work correctly, so I am doing it the old fashion way > of placing in debug statements. What ever logic is catching the doOwn > action is just ignoring it and calling upon the buildnormalcontext. Now the > question is, what would cause this to happen. > > In the jsp page I capture the rundata and js_peid from the request object > and store as page scope vars. > > Now, if the user select a checkbox and selects the doAssign button, this > works. Selecting this action changes the default action of the form and > sets it to a different psml file completely. Not sure if that helps. > > I would really like to make use of the displaytag lib so that the page > developers can use that instead of all the java we have to give them. > > Any other ideals? > > David Boyd > > _____ > > This mailbox protected from junk email by Matador > from MailFrontier, Inc. http://info.mailfrontier.com > > > > -----Original Message----- > From: Michael Rothrock [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 1:28 PM > To: Jetspeed Users List > Subject: Re: Anyone using displaytag lib with jetspeed > > In retrospect, it seems we didn't give enough detail. > > If you look into the jetspeed code that dispatches events, you'll see that > it traps exceptions from the doXxx methods without logging them (at least, > thatıs what it did the last time I walked through it). Even if your method > threw an exception, it proceeds to call buildNormalContext. > > Through experience I, and apparently Gregory, have learned that this leads > to situations where your doXxx method doesn't appear to do anything, you > don't see any exceptions, and buildNormalContext is called normally. This > can be quite baffling. > > To avoid this, I am now in the habit of logging all events within my action > class using the boilerplate code I posted in an earlier message. As I > always see my errors in the log, this has saved me mountains of time. > > Gregory appears to have taken a different (but equally effective) route, > tracing into his doXxx method with a debugger when this behavior occurs, > capturing the exception details in the debugger itself. > > The bottom line is this: the most likely cause of the behavior you describe > is that your doOwn method is throwing an exception. You can use either of > the two methods we've described (try/catch or manual trace with a debugger) > to see if this is the case. > > -- Michael > > On 5/4/04 10:59 AM, "Boyd, David" <[EMAIL PROTECTED]> wrote: > >> I can display the check box just fine, and the name and value are set >> correctly. The issue is that when a user checks any of these boxes and > then >> selects the own button, the doOwn action is not called. The >> buildnormalcontext is called which seems to me that some type of refresh > is >> going. I did a dump of the request object and I see that the >> eventSubmit_doOwn is in the object. So, why would the action be bypassed? >> Do I need to set the action on the form, currently it is set to action=''? >> >> >> David Boyd >> >> _____ >> >> This mailbox protected from junk email by Matador >> from MailFrontier, Inc. http://info.mailfrontier.com >> >> >> >> -----Original Message----- >> From: Gregory Joseph [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, May 04, 2004 11:00 AM >> To: Jetspeed Users List >> Subject: RE: Anyone using displaytag lib with jetspeed >> >> Ha, the wonders of Jetspeed. >> In those case, all I've been able to do was plug in my debugger and step >> through until some exception is thrown (which is silently digested by >> jetspeed afterwards, which is why you don't know what's happening) >> >> But I don't remember any issue specific to displaytag regarding this. > Maybe, >> first, try to remove your checkboxes and see if it has something to do > with >> that? >> >> g >> >> >> -----Original Message----- >> From: Boyd, David [mailto:[EMAIL PROTECTED] >> Sent: Tue 5/4/04 17:47 >> To: 'Jetspeed Users List' >> Cc: >> Subject: RE: Anyone using displaytag lib with jetspeed >> No, I am in the process of using it but am having and issue with it and > was >> wondering if someone could help me out. >> >> What I have done is taken a protlet that worked, and replaced the embedded >> java code that built the html table with the displaytag taglib stuff. > Now, >> I have this checkbox that I have added to the display (just like in the >> orginal stuff). The user is allow to select a row in the table, and then >> select the own button to take ownership of the item. Now, before I added >> the display tag, things worked, the doOwn action was called and life was >> good. Now with the displaytag lib in place, the action is not called. >> >> Any ideal as to why? >> >> David Boyd >> >> _____ >> >> This mailbox protected from junk email by Matador >> from MailFrontier, Inc. http://info.mailfrontier.com >> >> >> >> -----Original Message----- >> From: Gregory Joseph [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, May 04, 2004 10:46 AM >> To: Jetspeed Users List >> Subject: RE: Anyone using displaytag lib with jetspeed >> >> >> I am. >> Is this for a survey? >> >> >> g >> >> -----Original Message----- >> From: Boyd, David [mailto:[EMAIL PROTECTED] >> Sent: Tue 5/4/04 17:38 >> To: Jetspeed Users List >> Cc: >> Subject: Anyone using displaytag lib with jetspeed >> Currently using Jetspeed 1.4b3 and was wondering if anyone out there is >> using displaytag (http://displaytag.sourceforge.net/ >> <http://displaytag.sourceforge.net/> ) tablib in there app. >> >> >> >> >> >> David Boyd >> >> _____ >> >> This mailbox protected from junk email by Matador >> from MailFrontier, Inc. http://info.mailfrontier.com >> <http://info.mailfrontier.com> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
