Am 09.07.10 08:23, schrieb Ganesh:
Mojarra renders for a form update or generally a form only the raw
html code and some helper functions included separately, we inline the
oamsubmit functions constantly blowing our page up. While this is not
bad for normal cases (still costs rendering performance), the oam
function adds on my side another 10-15% performance loss on dom
replacement level if a target is refreshed which causes them to be
rendered.
Do you see any chance to remove the oam stuff? Mojarra does a simple
type="submit" and only adds an onclick in the ajax case.
I have not looked deeply into the oamsubmit, afaik they mainly map the
corresponding commandButton/commandLink to the proper jsf version syntax
for the decode phase so that the actionEvent can be issued.
Also I think they take care about the scroll to functionality.
But I think oamSubmit can be moved into something on resource level just
like mojarra has done with mojarra.ab (which I think is something
similar) and then being included automatically.
I think the problem is no one has touched the code for ages.
>> Another performance shortcut Mojarra seems to take is on ViewScoped
>>beans, we restore the bean constantly at every ppr request which does
>>something on a viewscoped bean, mojarra seems to take a shortcut
>>here. You can see that by using a ViewScoped bean in myfaces the
>>deserialisation in the bean is called at every ajax request, in
>>mojarra it is not.
>I know page, request and session scope. Which one are you referring to?
Page Scoped beans, the page scoped beans are constantly savestated per
request, probably due to being able to preserve the history. Whether
this makes sense from a performance point of view is another question
(as well as it makes the entire aspect of dataset -service layer
handling way more difficult than it needs)
