Re: MyFaces performance investigation from a client point of view

Hi, While 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

[jira] Commented: (EXTCDI-2) view access scope

[ https://issues.apache.org/jira/browse/EXTCDI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886640#action_12886640 ] Gerhard Petracek commented on EXTCDI-2: --- i've already renamed it to @ViewAccessScope

[jira] Issue Comment Edited: (EXTCDI-2) view access scope

[ https://issues.apache.org/jira/browse/EXTCDI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886640#action_12886640 ] Gerhard Petracek edited comment on EXTCDI-2 at 7/9/10 3:27 AM: ---

[jira] Commented: (MYFACES-2799) jsf.js cross form viewstate update

[ https://issues.apache.org/jira/browse/MYFACES-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886642#action_12886642 ] Werner Punz commented on MYFACES-2799: -- After sleeping over things, I do not want to

[jira] Updated: (MYFACES-2800) navigation-case/redirect/include-view-params is not picked up and has a wrong default value

[ https://issues.apache.org/jira/browse/MYFACES-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr updated MYFACES-2800: --- Status: Resolved (was: Patch Available) Fix Version/s: 2.0.1-SNAPSHOT

[jira] Issue Comment Edited: (MYFACES-2799) JSF 2.1: jsf.js viewstate handling does not entirely work out (bug filed on the spec tracker

[ https://issues.apache.org/jira/browse/MYFACES-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886642#action_12886642 ] Werner Punz edited comment on MYFACES-2799 at 7/9/10 4:36 AM:

Re: MyFaces performance investigation from a client point of view

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

Re: Mark issues for JSF 2.1

+1 for the first one as well, since I already have a few of such issues. Some of them can be solved on 2.0 level but not exposed (like our working queue handling) some of them really need a spec change (like the semi broken viewstate handling on protocol level) Werner Am 09.07.10 03:29,

[jira] Created: (MYFACES-2802) Remove CompositeComponentResourceTagHandler.ATTACHED_OBJECT_HADLERS_KEY from Attributes Map

Remove CompositeComponentResourceTagHandler.ATTACHED_OBJECT_HADLERS_KEY from Attributes Map --- Key: MYFACES-2802 URL: https://issues.apache.org/jira/browse/MYFACES-2802

Re: Mark issues for JSF 2.1

OK, great :) I just created the version 2.1.0 in the JIRA and already changed it on some issues. If you find any issues in the JIRA which are valid JSF 2.1 issues, please change the affected version to 2.1.0 on them. Thanks! Jakob 2010/7/9 Werner Punz werner.p...@gmail.com +1 for the first

Re: [GSOC] State saving performance improvements in MyFaces 2.0

Hello, I created a JIRA ticket with a patch that removes the CompositeComponentResourceTagH andler.ATTACHED_OBJECT_HADLERS_KEY from the component attributes map. Instead it creates a map with the attached object handlers indexed by the component reference. The JIRA ticket is:

[jira] Updated: (MYFACES-2802) Remove CompositeComponentResourceTagHandler.ATTACHED_OBJECT_HADLERS_KEY from Attributes Map

[ https://issues.apache.org/jira/browse/MYFACES-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petoi updated MYFACES-2802: -- Status: Patch Available (was: Open) Remove

Re: Mark issues for JSF 2.1

FYI: query to get 2.1.0 issues: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=10600version=12315190 Regards, Jakob 2010/7/9 Jakob Korherr jakob.korh...@gmail.com OK, great :) I just created the version 2.1.0 in the JIRA and already changed it on some issues. If

[jira] Reopened: (MYFACES-2791) render view params not working for EL expressions

[ https://issues.apache.org/jira/browse/MYFACES-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr reopened MYFACES-2791: Assignee: Jakob Korherr Actually I see the same issue on my machine when using

[jira] Resolved: (MYFACES-2791) render view params not working for EL expressions

[ https://issues.apache.org/jira/browse/MYFACES-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2791. Fix Version/s: 2.0.1-SNAPSHOT Resolution: Fixed render view params not working

[jira] Created: (TRINIDAD-1846) tp1055

tp1055 -- Key: TRINIDAD-1846 URL: https://issues.apache.org/jira/browse/TRINIDAD-1846 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.12-core Environment: any

[jira] Created: (EXTCDI-31) switch to geronimo validation API as default

switch to geronimo validation API as default Key: EXTCDI-31 URL: https://issues.apache.org/jira/browse/EXTCDI-31 Project: MyFaces CODI Issue Type: Improvement Affects Versions: 1.0.0-SNAPSHOT

[jira] Commented: (MYFACES-2792) Redirect with include-view-params in faces-config.xml

[ https://issues.apache.org/jira/browse/MYFACES-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12886700#action_12886700 ] Martin Marinschek commented on MYFACES-2792: ;) s*** happens! all the best,

[jira] Resolved: (EXTCDI-31) switch to geronimo validation API as default

[ https://issues.apache.org/jira/browse/EXTCDI-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved EXTCDI-31. - Fix Version/s: 1.0.0-SNAPSHOT Resolution: Fixed switch to geronimo validation API as

ValidatorHandler and wire all attributes set to the Validator instance

Hi, javadoc for javax.faces.view.facelets.ValidatorHandler contains this sentence: Will wire all attributes set to the Validator instance created/fetched. Based on that one our developer tried this: f:validator binding=#{aValidator} property=#{expression} / Expected result was to put a value

[jira] Created: (TRINIDAD-1847) processFlattenedChildren should treat UIPanel and UINamingContainer as FlattenedComponents

processFlattenedChildren should treat UIPanel and UINamingContainer as FlattenedComponents -- Key: TRINIDAD-1847 URL: https://issues.apache.org/jira/browse/TRINIDAD-1847

[jira] Updated: (TRINIDAD-1847) processFlattenedChildren should treat UIPanel and UINamingContainer as FlattenedComponents

[ https://issues.apache.org/jira/browse/TRINIDAD-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Starets updated TRINIDAD-1847: -- Status: Patch Available (was: Open) processFlattenedChildren should treat UIPanel and

[jira] Created: (MYFACES-2803) jsf.js multipart form request, multi transport method support

jsf.js multipart form request, multi transport method support - Key: MYFACES-2803 URL: https://issues.apache.org/jira/browse/MYFACES-2803 Project: MyFaces Core Issue Type:

Snapshot build down?

Hia if you look at the http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/core/myfaces-impl/2.0.1-SNAPSHOT/ the last build was from july the first. Is the nightly build down? Werner

[jira] Created: (TRINIDAD-1848) Session/PageFlowScope memory optimisation

Session/PageFlowScope memory optimisation - Key: TRINIDAD-1848 URL: https://issues.apache.org/jira/browse/TRINIDAD-1848 Project: MyFaces Trinidad Issue Type: Task Components: Documentation

Re: Snapshot build down?

http://people.apache.org/repo/m2-snapshot-repository is the _old_ snapshots repo which is currently being faded out. Not sure though about the status. Minotaur was really slow lately, so this is a good idea anyway. LieGrue, strub --- On Fri, 7/9/10, Werner Punz werner.p...@gmail.com wrote:

[jira] Resolved: (MYFACES-2804) LifecycleImpl _firstRequestProcessed should be marked as volatile

[ https://issues.apache.org/jira/browse/MYFACES-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2804. - Fix Version/s: 2.0.1-SNAPSHOT Resolution: Fixed LifecycleImpl

[jira] Created: (MYFACES-2804) LifecycleImpl _firstRequestProcessed should be marked as volatile

LifecycleImpl _firstRequestProcessed should be marked as volatile - Key: MYFACES-2804 URL: https://issues.apache.org/jira/browse/MYFACES-2804 Project: MyFaces Core Issue Type:

[jira] Created: (MYFACES-2805) Use synchronized blocks for ApplicationImpl _defaultValidatorsIds

Use synchronized blocks for ApplicationImpl _defaultValidatorsIds - Key: MYFACES-2805 URL: https://issues.apache.org/jira/browse/MYFACES-2805 Project: MyFaces Core Issue Type: