[mgrouch]

So far I have this proposal to prevent double submission

http://jira.jboss.org/jira/browse/RF-710

Also it could be used on any Ajax request to prevent concurrent
ajax requests when there is ajax activity alread.

What do you think?
Thanks

[amitev]

In shale project there is a component that prevents double submits (shale token).

[denis-karpov]

About double requests....

I used for a long time the solution that I have proposed to Gavin
http://jira.jboss.org/jira/browse/JBSEAM-183
Gavin by some reasons did not accept it in to Seam. I did not catch exactly why. As I understand it concerns clustering. I do not know about clustering, but on single server it works reliably 100%.

Denis.

[mgrouch]

Here is a link to additional performance discussion thread

Topics discussed there include

EL performance, impact of reflection,
impact of Seam interception, using outjection,
impact of Seam lookups for annotations,
comparison with JSP

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118762

Thanks

[asookazian]

I don't think I saw this one yet:

don't code heavy logic or db access code (opening db connections are expensive) in getXXX() methods that are called from JSF EL (e.g. methods called from render or value attributes).

It's possible that your getXXX() methods may be called several times (unbeknownst to you until you use the debugger) when the JSF is rendering.

Apparently, there is nothing in the JSF spec that states the getXXX() methods must be called only once per rendering of the JSF page.

[lisaanm]

Hi,
I came across a performance tip for JSF/JSP pages and would like to confirm it.

Here is what they say:
JSF/JSP tags should be in one line.

Example:

BEFORE

<h:form>
 <h:inputText value="SEAM Rocks!!!!">
</h:form>

AFTER

<h:form> <h:inputText value="SEAM Rocks!!!!"> </h:form>

Eventhough tough to read JSF/JSP pages, but for production i think its OK.

Any comments about this.

Thanks

[pmuir]

Have you got a source for that? It seems like FUD to me.