Dion,
Did we clear-up the differentiation of j:include and j:import?
I looked at the code some days ago and found simply no difference. Plus
the tag-doc for one of them is wrong.
Do I understand correctly that the following should be true:
- j:import includes the script at compilation time (special from the
script-parsing ?) or at least the first time it's read then caches it.
- j:include loads and runs the script but dumps it out right away after
thanks
Le 28 janv. 05, à 12:56, dion gillard (JIRA) a écrit :
[ http://issues.apache.org/jira/browse/JELLY-171?page=history ]
dion gillard closed JELLY-171:
--
Resolution: Duplicate
Dupe of JELLY-170
Nested scripts should be compiled and cached
Key: JELLY-171
URL: http://issues.apache.org/jira/browse/JELLY-171
Project: jelly
Type: Improvement
Components: core / taglib.core
Versions: 1.0
Environment: tomcat 5.0, Jelly 1.0 RC1
Reporter: Arnaud Masson
In the current version of jelly "import" tag, imported scripts are
always parsed and recompiled each time the containing script runs,
even if this script has already been compiled.
It isn't optimized if the compiled version of the main script must be
cached for multiple read, for instance a web page.
In a JSP context, all included pages are compiled when the main jsp
is compiled, so there is no performance penalty. That would be nice
to have the same thing in jelly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
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]