I'm no expert. The people writing Forte are, and based on
their expertise it is not simple. The only things I remember
(because are simple enough to understand :-) are:
- jspc compilers compile JSP->Java->CLASS
- this happens mostly at runtime
- the Java files are not kept (they usually contain the comments
  with original JSP lines and line numbers)
- the generated Java and CLASS file names are different
  in different JSPC-s (and even different versions of the same
  tool)
- if the JSP gets changed, the AppServer will recompile it,
  I'm not sure what might that do with debugging
  (new classloaders, etc.)

r.

> -----Original Message-----
> From: Mike Liu [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 27, 2001 11:10 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Eap-list] Feature Requests
> 
> 
> Tomcat would have been fine.  Popular ones like Weblogic are 
> good too.  But
> I agree that it might get too big.  Most jsp compilers 
> decorate the compiled
> source with line number and such.  So how about coming up 
> with some sort of
> parsing schemes to associate the actual JSP file with the 
> compiled java
> class?  If we can tell which line on the JSP is being 
> executed then that
> would be a good start.
> 
> 
> Thanks,
> Mike Liu
> 
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Christopher Cobb
> Sent: Tuesday, November 27, 2001 07:53 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Eap-list] Feature Requests
> 
> That's where Tomcat interation would be nice.  In JBuilder 5 
> you can hit
> CTRL-F9 on a JSP page and it appears to call Tomcat's jspc compiler to
> compile the page.  Even if you are not using Tomcat as a JSP 
> container,
> it would still be nice to be able to directly compile JSP 
> pages, even if
> you end up throwing away the generated class files.
> 
> "Nemec, Richard" wrote:
> 
> > Mike,(1) this feature might be very expensive. Every app. server has
> > its own JSP compiler andthere is no plain common mapping 
> between these
> > two. You can do something like thatin Forte, but that is one of
> > reasons why is it so HUGE.(2) You can do that. Menu: Code/Implement
> > methods... r.
> >
> >      -----Original Message-----
> >      From: Mike Liu [mailto:[EMAIL PROTECTED]]
> >      Sent: Monday, November 26, 2001 11:55 PM
> >      To: Eap-List@Intellij. Com
> >      Subject: [Eap-list] Feature Requests
> >
> >      Hi all,
> >
> >      Hopefully this is where I submit feature requests.Here's
> >      two:
> >
> >      1)JSP Debugging.On the actual JSP file, not the compiled
> >      servlet
> >
> >      2)"Implement methods" feature where it automatically creates
> >      the method signatures defined in the interface(s) for the
> >      class that implements these interface(s).
> >
> >      Any votes?
> >
> >      Thanks,
> >
> >      Mike Liu
> >
> 
> 
> _______________________________________________
> Eap-list mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-list
> 
> 
> _______________________________________________
> Eap-list mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-list
> 

_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list

Reply via email to