Sorry, I misunderstood what you wrote -- I didn't realize you were
outputting the string in a comment as well.
However, unless you've tested with an actual timing filter around your
request/response, it still may not be the issue.
The issue could be the web browser itself rendering the page (which
seems more likely than a JSF issue -- JSF should simply be outputting
the raw text stream in both cases).
The other potential issue might be the processing of the response via
the extensions filter, so that would be another area to have a timing
test.
On 3/19/07, Des qsdqsd <[EMAIL PROTECTED]> wrote:
>actually, getHtmlcontent only returns a very long string fetched from the
database. Debugging show that it's not where the >problem lies, this is
quick, the problem lies within the jsf machinery that happens after ...
another argument for that opinion is the following :
if I comment out the result of the getHtmlcontent in the jsf page :
*** mypage ***
<div>
<f:verbatim>
<!--
#{mybean.htmlcontent}
-->
</f:verbatim>
</div>
*** /mypage ***
.. everything is quick and ok : except that in the result html page, the
content of the bean is inside comments of course...
________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.
