I have been trying to get off of this list - can anyone help? I followed all the directions (three lines with email address) and it doesn't work...
----- Original Message ----- From: "John Yu" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, April 21, 2002 8:06 PM Subject: Fwd: RE: Re: Not Locating JSPs > Hi Brian, > > When Camino can't parse a JSP, it won't be shown on the tree and Camino > treats those 'faulty' JSPs as if they don't exist. > > "Refresh" refreshes the tree and the Storyboard from memory, not from the > files. Therefore, 'faulty' JSPs aren't re-read and Camino doesn't report > any further parse error. > > In your case, Camino reports logoff.jsp has an unmatched and redundant </a> > close tag at line 36. Besides, there's a limitation in the current version > of Camino that there must be a space before the "%>" markup of the taglib > declarations. > > Once you remove the redundant </a>, add the space to the taglib declaration > and "Reload" (not "Refresh") the project, you should see the logoff.jsp > displayed. > > regards, > -- > John > > > At 08:14 am 19-04-2002 -0400, you wrote: > >John, > > > >Thanks for the quick response back. I realize that my initial input was > >vague and apologize. Here are the answers to your questions: > > > >1. Windows 2000 SP2 > >2. Yes, all JSPs use the ".jsp" extension. > >3. Yes, Camio does not locate JSPs that are in the same directory. For > >example, a directory $DOCROOT/security has three JSPs: logon.jsp, > >logoff.jsp, maintenance.jsp. Only the logon and maintenance JSPs are > >added to the DOCROOT of the project. The logoff.jsp is always > >missed. This happens in several other places too. > >4. No error dialog box was displayed. > >5. When the project is initially loaded, there are a large number of > >parse errors. However, when I "refresh" the project, these errors go > >away. I am only left with ? items that appear to be valid--except for > >"/logoff.do: Forward name = 'success' target '/jsp/security/logoff.jsp' is > >not found." > > > >It appears that additional tag libraries (all Jakarta based and included > >in the project properties) are not referenced during the initial parse of > >the JSPs. Only the base Struts taglibs are used during the initial > >parse. Refreshing the project allows the analyze process to remove these > >false errors? Thats my guess as to why these parse errors go away with a > >"refresh". > > > >Attached is the camino.log file as requested. I am also attaching the > >logoff.jsp page to see if that offers you a clue into what is happening. > > > >Thanks again John. > > > >Brian > > -- > John Yu Scioworks Technologies > e: [EMAIL PROTECTED] w: +(65) 873 5989 > w: http://www.scioworks.com m: +(65) 9782 9610 > > Scioworks Camino - "Rapid WebApp Assembly for Struts" > > === > To subscribe/unsubscribe, visit http://list.scioworks.com:8081/guest/RemoteListSummary/camino_user > === To subscribe/unsubscribe, visit http://list.scioworks.com:8081/guest/RemoteListSummary/camino_user
