> > I tend to think that it can be very usefull in some situations like
> this
> > one:
> > <!--# include file="/dir/<DISPLAY PROPERTY="info:myFile">" -->
> > that's why I have implemented this kind of thing in my own
> > implementation...
>
> Yeah, but that means the file gets included _after_ the JSP is parsed
> and compiled, so you can't #include other .jsp script files.
No. The inclusion I have implemented is totally dynamic. You can include
another jsp. The reference implementation simply "copies" the content of
the file in place when I do really include another jsp (a bit like
RequestDispatcher.include())... The big advantage with that solution is
that if you modify the included jsp then it will be automatically be
recompiled when you request the page that includes it...
Yan
--
http://eowyn.fr.eu.org/~yan/ | [EMAIL PROTECTED]
SocialNet: Where people connect... http://www.socialnet.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
