[jira] Resolved: (EXTSCRIPT-88) cleanup the faclet-config handling
[ https://issues.apache.org/jira/browse/EXTSCRIPT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-88. -- Resolution: Fixed cleanup the faclet-config handling -- Key: EXTSCRIPT-88 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-88 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor We have to add local facelet configs to our jsf 1.2 and jsf 2.0 modules to enable auto handling of our component tags from the core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (EXTSCRIPT-88) cleanup the faclet-config handling
[ https://issues.apache.org/jira/browse/EXTSCRIPT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842962#action_12842962 ] Werner Punz commented on EXTSCRIPT-88: -- done cleanup the faclet-config handling -- Key: EXTSCRIPT-88 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-88 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor We have to add local facelet configs to our jsf 1.2 and jsf 2.0 modules to enable auto handling of our component tags from the core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (EXTSCRIPT-88) cleanup the faclet-config handling
[ https://issues.apache.org/jira/browse/EXTSCRIPT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz reopened EXTSCRIPT-88: -- cleanup the faclet-config handling -- Key: EXTSCRIPT-88 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-88 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor We have to add local facelet configs to our jsf 1.2 and jsf 2.0 modules to enable auto handling of our component tags from the core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-88) cleanup the faclet-config handling
[ https://issues.apache.org/jira/browse/EXTSCRIPT-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-88. -- Resolution: Fixed cleanup the faclet-config handling -- Key: EXTSCRIPT-88 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-88 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor We have to add local facelet configs to our jsf 1.2 and jsf 2.0 modules to enable auto handling of our component tags from the core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTSCRIPT-90) introduce meta bundles
introduce meta bundles -- Key: EXTSCRIPT-90 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-90 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor Introduce meta bundles which bundle the core + 1.2 + java6 , and core + 2.0 and java6 into one single jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
Hey Martin, the app-engine stuff is already part of myfaces2. The HTML5 RenderKit is not yet implemented and will be done under the umbrella of GSoc. -Matthias On Tue, Mar 9, 2010 at 4:37 AM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Martin, There have been some proposals for GSoC. One is the app engine support (which is also available by now for MyFaces 2.0, but too small for a whole GSoC project) and the other one is a HTML 5 renderkit (or component set). Ali Ok is really interested in doing those two. In fact, he already did the first one (see [1] and [2]) and he created a google code project for the HTML 5 renderkit (see [3] and [4] for details). Furthermore Matthias Wessendorf said that he is interested in mentoring this. Regards, Jakob [1] https://issues.apache.org/jira/browse/MYFACES-2504 [2] https://issues.apache.org/jira/browse/MYFACES-2559 [3] http://code.google.com/p/myfaces-html5-starter/ [4] http://old.nabble.com/-GSOC--HTML5-Renderkit-Start-up-td27748075.html 2010/3/9 Martin Marinschek mmarinsc...@apache.org Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (MYFACES-2592) UIViewParameter.decode() should set the submitted value only if it is not null
[ https://issues.apache.org/jira/browse/MYFACES-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2592. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 UIViewParameter.decode() should set the submitted value only if it is not null -- Key: MYFACES-2592 URL: https://issues.apache.org/jira/browse/MYFACES-2592 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Reporter: Jakob Korherr Assignee: Jakob Korherr Fix For: 2.0.0-beta-3 Otherwise the latest non null value would be overwritten if the parameter is absent in a request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTSCRIPT-91) TagHandlers
TagHandlers --- Key: EXTSCRIPT-91 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-91 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor Investigate whethere there are extension points in facelets which allow the dynamisation of custom tag handlers -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACESTEST-3) Add configuration resource for Myfaces 1.2 to ConfigParser
[ https://issues.apache.org/jira/browse/MYFACESTEST-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr updated MYFACESTEST-3: Resolution: Fixed Status: Resolved (was: Patch Available) Add configuration resource for Myfaces 1.2 to ConfigParser -- Key: MYFACESTEST-3 URL: https://issues.apache.org/jira/browse/MYFACESTEST-3 Project: Apache MyFaces Test Issue Type: Task Reporter: Rudy De Busscher Assignee: Jakob Korherr Attachments: myfacestest-3.patch The configuration resource for MyFaces 1.2 is not yet defined in the class ConfigParser (test12 module) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
Hi Martin, Google App Engine support is not a GSOC proposal anymore. We discussed about this project and after determining it is too small to be a GSOC project, I've done this with the help of the community. About other project: There is not much progress on HTML5 components project; I save it to GSOC period. I am currently getting ready for my proposal about this project. The Google Code project is to get feedback from community and determine what do implement. Greetings, Ali On Tue, Mar 9, 2010 at 2:45 PM, Martin Marinschek mmarinsc...@apache.orgwrote: Hi Jakob, how do I see that these are Google SoC proposals? Also, Google SoC must be about stuff which has not already been implemented... best regards, Martin On 3/9/10, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Martin, There have been some proposals for GSoC. One is the app engine support (which is also available by now for MyFaces 2.0, but too small for a whole GSoC project) and the other one is a HTML 5 renderkit (or component set). Ali Ok is really interested in doing those two. In fact, he already did the first one (see [1] and [2]) and he created a google code project for the HTML 5 renderkit (see [3] and [4] for details). Furthermore Matthias Wessendorf said that he is interested in mentoring this. Regards, Jakob [1] https://issues.apache.org/jira/browse/MYFACES-2504 [2] https://issues.apache.org/jira/browse/MYFACES-2559 [3] http://code.google.com/p/myfaces-html5-starter/ [4] http://old.nabble.com/-GSOC--HTML5-Renderkit-Start-up-td27748075.html 2010/3/9 Martin Marinschek mmarinsc...@apache.org Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr
Re: Google SoC
Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (MYFACES-2592) UIViewParameter.decode() should set the submitted value only if it is not null
UIViewParameter.decode() should set the submitted value only if it is not null -- Key: MYFACES-2592 URL: https://issues.apache.org/jira/browse/MYFACES-2592 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Reporter: Jakob Korherr Assignee: Jakob Korherr Otherwise the latest non null value would be overwritten if the parameter is absent in a request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Google Summer of Code
Hi, here is a wiki page, that has some more information on the GSoC program: http://cwiki.apache.org/confluence/display/COMDEVxSITE/GSoC So, once the ASF has been accepted (to be announced on March 18th), students can apply for it, starting on March 29th. -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (MYFACES-2563) Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2
[ https://issues.apache.org/jira/browse/MYFACES-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2563. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 Trinidad 1.2.x generates on POSTBACK a NullPointerException on MyFAces2 --- Key: MYFACES-2563 URL: https://issues.apache.org/jira/browse/MYFACES-2563 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta Reporter: Matthias Weßendorf Assignee: Jakob Korherr Fix For: 2.0.0-beta-3 tr:commandButton. a click generates this: SEVERE: An exception occurred javax.faces.FacesException: java.lang.NullPointerException at org.apache.myfaces.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241) at org.apache.myfaces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:157) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:88) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148) at org.apache.myfaces.trinidaddemo.webapp.RedirectFilter.doFilter(RedirectFilter.java:97) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520) Caused by: java.lang.NullPointerException at org.apache.myfaces.application.ViewHandlerImpl.getViewParameterList(ViewHandlerImpl.java:297) at org.apache.myfaces.application.ViewHandlerImpl.getRedirectURL(ViewHandlerImpl.java:119) at javax.faces.application.ViewHandlerWrapper.getRedirectURL(ViewHandlerWrapper.java:121) at org.apache.myfaces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:92) at org.apache.myfaces.trinidadinternal.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:49) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:125) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190) at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:878) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:234) at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1190) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:611) at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:35) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:138) ... 26 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-90) introduce meta bundles
[ https://issues.apache.org/jira/browse/EXTSCRIPT-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-90. -- Resolution: Fixed introduce meta bundles -- Key: EXTSCRIPT-90 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-90 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz Priority: Minor Introduce meta bundles which bundle the core + 1.2 + java6 , and core + 2.0 and java6 into one single jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2592) UIViewParameter.decode() should set the submitted value only if it is not null
[ https://issues.apache.org/jira/browse/MYFACES-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843074#action_12843074 ] Jakob Korherr commented on MYFACES-2592: the related thread from the mailing list: http://www.mail-archive.com/us...@myfaces.apache.org/msg55074.html UIViewParameter.decode() should set the submitted value only if it is not null -- Key: MYFACES-2592 URL: https://issues.apache.org/jira/browse/MYFACES-2592 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Reporter: Jakob Korherr Assignee: Jakob Korherr Otherwise the latest non null value would be overwritten if the parameter is absent in a request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [GSoC] HTML 5 RenderKit
Hi, Ok, I will update the pages and the wiki ASAP. Regards, Ali On Tue, Mar 9, 2010 at 3:43 PM, Matthias Wessendorf mat...@apache.orgwrote: Hi, as mentioned before ([1]) an HTML5 renderkit could be a neat MyFaces project for the Google Summer of Code program. A student (Ali Ok) already showed interested (see [1]). Ali created already some google code project to prototype HTML5 stuff in vanilla Facelet XHTML fragments (see [2] and [3]). However the real work has not started!! I think now it is time to write a wiki based on previous discussions and the quick tryouts. I create a pretty empty wiki page (see [4]) to collect ideas and write-up some summary. For the actual implementation/code: We can't use the prototyping project ([2]). Instead we have to go through the ASF process (dev@ mailing list, JIRA, patch, etc.) Ali: Can you update the project ([2]) to make clear that this is only for prototyping? Not the real implementation ? Do others agree ? -Matthias [1] http://old.nabble.com/-GSoc--Google-Summer-of-Code-Idea-td27040478.html [2] http://code.google.com/p/myfaces-html5-starter/source/browse/#svn/trunk/src/test/resources/tag-interface [3] http://old.nabble.com/-GSOC--HTML5-Renderkit-Start-up-td27748075.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr
Google SoC
Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
[jira] Resolved: (EXTSCRIPT-92) Groovy Renderer Refresh broken
[ https://issues.apache.org/jira/browse/EXTSCRIPT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-92. -- Resolution: Fixed Groovy Renderer Refresh broken -- Key: EXTSCRIPT-92 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-92 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee: Werner Punz Not sure why this happens but the renderer in the groovy example does not refresh anymore, the java renderers all refresh as expected -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
Hi Martin, There have been some proposals for GSoC. One is the app engine support (which is also available by now for MyFaces 2.0, but too small for a whole GSoC project) and the other one is a HTML 5 renderkit (or component set). Ali Ok is really interested in doing those two. In fact, he already did the first one (see [1] and [2]) and he created a google code project for the HTML 5 renderkit (see [3] and [4] for details). Furthermore Matthias Wessendorf said that he is interested in mentoring this. Regards, Jakob [1] https://issues.apache.org/jira/browse/MYFACES-2504 [2] https://issues.apache.org/jira/browse/MYFACES-2559 [3] http://code.google.com/p/myfaces-html5-starter/ [4] http://old.nabble.com/-GSOC--HTML5-Renderkit-Start-up-td27748075.html 2010/3/9 Martin Marinschek mmarinsc...@apache.org Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
[jira] Created: (EXTSCRIPT-92) Groovy Renderer Refresh broken
Groovy Renderer Refresh broken -- Key: EXTSCRIPT-92 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-92 Project: MyFaces Extensions Scripting Issue Type: Bug Reporter: Werner Punz Assignee: Werner Punz Not sure why this happens but the renderer in the groovy example does not refresh anymore, the java renderers all refresh as expected -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2588) JavaScript error in function oamClearHiddenInput in IE8
[ https://issues.apache.org/jira/browse/MYFACES-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843045#action_12843045 ] Brian Preuß commented on MYFACES-2588: -- The issue seems to be a side effect of a malicious compenent on our page which created a duplicate hidden input field for javax.faces.ViewState, which causes the problems in Internet Explorer. Removing the malicious component fixes the issue, so no need to alter MyFaces code. JavaScript error in function oamClearHiddenInput in IE8 --- Key: MYFACES-2588 URL: https://issues.apache.org/jira/browse/MYFACES-2588 Project: MyFaces Core Issue Type: Bug Affects Versions: 1.2.7 Environment: Windows Vista, Internet Explorer 8.0.6001.18882, MyFaces 1.2.7 Reporter: Brian Preuß Assignee: Jakob Korherr Priority: Blocker Attachments: patch-MYFACES-2588.diff The JavaScript function oamClearHiddenInput generate an error when using IE8. The error says illegal argument in the line form.removeChild(hInput);. You can see a description of this problem at http://groups.google.com/group/alt.comp.lang.javascript/browse_thread/thread/2380af22f06b05a6/475ae9c43505c581. I'll try to submit a patch for that :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (EXTSCRIPT-89) windows
[ https://issues.apache.org/jira/browse/EXTSCRIPT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843021#action_12843021 ] Werner Punz commented on EXTSCRIPT-89: -- Ok the examples now run, all tests pass, I guess we cann call this issue resolved, until the next major updates windows --- Key: EXTSCRIPT-89 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-89 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz make sure that there are no pending bugs for non unix configurations (aka windows) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-89) windows
[ https://issues.apache.org/jira/browse/EXTSCRIPT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Werner Punz resolved EXTSCRIPT-89. -- Resolution: Fixed windows --- Key: EXTSCRIPT-89 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-89 Project: MyFaces Extensions Scripting Issue Type: Improvement Reporter: Werner Punz Assignee: Werner Punz make sure that there are no pending bugs for non unix configurations (aka windows) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTVAL-87) pluggable proxy helper
pluggable proxy helper -- Key: EXTVAL-87 URL: https://issues.apache.org/jira/browse/EXTVAL-87 Project: MyFaces Extensions Validator Issue Type: Improvement Components: Core Reporter: Gerhard Petracek by default extval provides support for beans proxied via cglib. it should be possible to provide a custom proxy helper which is also aware of other proxy libs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[GSoC] HTML 5 RenderKit
Hi, as mentioned before ([1]) an HTML5 renderkit could be a neat MyFaces project for the Google Summer of Code program. A student (Ali Ok) already showed interested (see [1]). Ali created already some google code project to prototype HTML5 stuff in vanilla Facelet XHTML fragments (see [2] and [3]). However the real work has not started!! I think now it is time to write a wiki based on previous discussions and the quick tryouts. I create a pretty empty wiki page (see [4]) to collect ideas and write-up some summary. For the actual implementation/code: We can't use the prototyping project ([2]). Instead we have to go through the ASF process (dev@ mailing list, JIRA, patch, etc.) Ali: Can you update the project ([2]) to make clear that this is only for prototyping? Not the real implementation ? Do others agree ? -Matthias [1] http://old.nabble.com/-GSoc--Google-Summer-of-Code-Idea-td27040478.html [2] http://code.google.com/p/myfaces-html5-starter/source/browse/#svn/trunk/src/test/resources/tag-interface [3] http://old.nabble.com/-GSOC--HTML5-Renderkit-Start-up-td27748075.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Google SoC
Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago - Write (more) new skins for Trinidad - Implement Double-Submit-Handling/Back-Button Handling in one of the MyFaces subprojects - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling what do you guys think? best regards, Martin On 3/9/10, Matthias Wessendorf mat...@apache.org wrote: Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
[jira] Commented: (MYFACES-2590) Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans)
[ https://issues.apache.org/jira/browse/MYFACES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843184#action_12843184 ] Lincoln Baxter III commented on MYFACES-2590: - Sure! Here's an example that I just ran across today: http://www.seamframework.org/Community/PersistAndPassFacesMessagesOverMultiplePageRedirects?cid=2287109 The need for @Inject support in JSF artifacts is going to continue increasing, and it's really a big setback now that we have CDI, which is a pervasive, all-encompasing tool. Really, by omitting this functionality in the JSF spec, we've done a disservice to anyone who wants to use a DI/IoC container. It means that they need to jump through hoops in order to get references to managed beans and other injectable services in their JSF lifecycle artifacts. As we all know, a lot of business logic goes in to custom phase listeners, validators, converters; having access to CDI/@Inject and other annotations will address a wide range of real-life use-cases (such as the one above.) I personally know that I want to be able to @Inject my LoggedInUserBean into my LoggedInUserPasswordValidator -- but I have to access it much like David accesses his MessagesRevival bean. Does that help? Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans) -- Key: MYFACES-2590 URL: https://issues.apache.org/jira/browse/MYFACES-2590 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Environment: ALL Reporter: Lincoln Baxter III JSF implementations should treat the following framework components as JEE components, and pass them through the default WebInjectionProvider.inject() method part of any instantiation process. E.g: Whether or not the framework is instantiating the object for it's use, or the user is asking the framework for a new instance. The benefit: This means that any container provided injection points would automatically be available in the following artifacts: * ManagedBean * PhaseListener * SystemEventListener * Converter * Validator * ... more? For extension writers: Support for native container-injection for all artifacts defined in section 11.4.6 of the JSR-314 spec. ■ ActionListener ■ ApplicationFactory ■ FacesContextFactory ■ LifecycleFactory ■ NavigationHandler ■ PropertyResolver ■ RenderKit ■ RenderKitFactory ■ ResourceHandler ■ StateManager ■ VariableResolver ■ ViewHandler There is a related SPEC issue, Mojarra enhancement, and GlassFish bug also involved in getting this standardized across the board: https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=763 https://glassfish.dev.java.net/issues/show_bug.cgi?id=11655 https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1578 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
Sounds great! Maybe we can also do some work in the area of file uploads (e.g. upload progress, select multiple files,...). Something similar to what Google Mail does for attachments would be nice. Regards, Jakob 2010/3/9 Martin Marinschek mmarinsc...@apache.org Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago - Write (more) new skins for Trinidad - Implement Double-Submit-Handling/Back-Button Handling in one of the MyFaces subprojects - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling what do you guys think? best regards, Martin On 3/9/10, Matthias Wessendorf mat...@apache.org wrote: Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Helping the project
MyFaces is open to any help. The way to get started is to check out the code, get familiar with it and then check the Jira bug log. Any open-unassigned issues are a good place to start. Most ppl. start by tackling issues that affect the projects they are working on, so one idea is to have a project using myfaces that you can build and tweak and while doing so contribute. Contributing to the project involves submitting mailing-list answers, creating JIRA tickets and submitting patches for existing JIRA tickets. MyFaces committers will then review the patches and commit them to the code base if they look good. Sorry, I do not know how KDE development works, so I cannot speak to that part of your question. -Andrew On Mon, Mar 8, 2010 at 8:07 PM, Carlos Ortiz chrono.d...@gmail.com wrote: Hi, Is there any Junior jobs like KDE so i newbie like myself can knowing the internals of MyFaces can help the project. Best Regards Carlos Ortiz.
Re: Google SoC
- Add to that, extend the recompilation we have for jsf in ext-scripting towards CDI (possibly for all two implementations) That would be one of my next tasks post 1.0, maybe I can offload that one. Werner Am 09.03.10 17:19, schrieb Martin Marinschek: Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago - Write (more) new skins for Trinidad - Implement Double-Submit-Handling/Back-Button Handling in one of the MyFaces subprojects - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling what do you guys think? best regards, Martin On 3/9/10, Matthias Wessendorfmat...@apache.org wrote: Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Created: (MYFACES-2593) styles are escaped so that @import *.css doesn't work
styles are escaped so that @import *.css doesn't work - Key: MYFACES-2593 URL: https://issues.apache.org/jira/browse/MYFACES-2593 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Environment: CSS Reporter: Ganesh Jung This one doesn't pull the script with MyFaces 2.0: style type=text/css @import test.css /style No problem with Mojarra here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
On Tue, Mar 9, 2010 at 8:19 AM, Martin Marinschek mmarinsc...@apache.org wrote: Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago Trinidad has some fallback already, however it is only applied when mobile rendering is involved (by user-agent detection of the components). So, we could port that... - Write (more) new skins for Trinidad yeah! :-) - Implement Double-Submit-Handling/Back-Button Handling in one of the MyFaces subprojects - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling what do you guys think? best regards, Martin On 3/9/10, Matthias Wessendorf mat...@apache.org wrote: Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Google SoC
2010/3/9 Martin Marinschek mmarinsc...@apache.org Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 Sure! I would like to profile this stuff better. - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago - Write (more) new skins for Trinidad Adonis Raduca told me he did some work on the selectors when he did casablanca trinidad skin, to make other skins more easier to do, so I think it is possible to create new ones based on casablanca work with some effort. - Implement Double-Submit-Handling/Back-Button Handling in one of the MyFaces subprojects - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling I was thinking based on a suggestion done on JSFDays to take advantage on trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), and refactor that code to allow orchestra conversation scope work without spring (using the new JSF 2.0 custom scope). what do you guys think? best regards, Martin On 3/9/10, Matthias Wessendorf mat...@apache.org wrote: Hey On Tue, Mar 9, 2010 at 4:28 AM, Martin Marinschek mmarinsc...@apache.org wrote: Hi guys, question: Google SoC - I saw some administrative mails already, but no real proposals from the MyFaces community (just one proposal by a potential student). So is there something already worked on with regards to this? Are people interested in mentoring students? In getting projects done? I think we are supposed to use the issue tracker for this year's project - is that true? yep. I understood the mails that way too. Once the ASF has registered, I think Norin will do that 2day, I will get some wiki to prepare the JIRA entry. -Matthias best regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
[jira] Resolved: (EXTVAL-87) pluggable proxy helper
[ https://issues.apache.org/jira/browse/EXTVAL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTVAL-87. Resolution: Fixed Fix Version/s: 1.1.3-SNAPSHOT 2.0.3-SNAPSHOT 1.2.3-SNAPSHOT Assignee: Gerhard Petracek pluggable proxy helper -- Key: EXTVAL-87 URL: https://issues.apache.org/jira/browse/EXTVAL-87 Project: MyFaces Extensions Validator Issue Type: Improvement Components: Core Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT by default extval provides support for beans proxied via cglib. it should be possible to provide a custom proxy helper which is also aware of other proxy libs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2590) Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans)
[ https://issues.apache.org/jira/browse/MYFACES-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843263#action_12843263 ] Jakob Korherr commented on MYFACES-2590: Hmm OK. This is actually not bad :) I personally really like CDI. I think it's a very great technique and it spares you lots of boilerplate code. Unfortunately, this will by no means get into the JSF 2.0 spec, I think. Maybe in JSF 2.NEXT but who knows.. However, I'll take a look at this, because it just seems right and it's a nice feature! Web Container injection support should be provided for additional lifecycle artifacts (not just managed beans) -- Key: MYFACES-2590 URL: https://issues.apache.org/jira/browse/MYFACES-2590 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Environment: ALL Reporter: Lincoln Baxter III JSF implementations should treat the following framework components as JEE components, and pass them through the default WebInjectionProvider.inject() method part of any instantiation process. E.g: Whether or not the framework is instantiating the object for it's use, or the user is asking the framework for a new instance. The benefit: This means that any container provided injection points would automatically be available in the following artifacts: * ManagedBean * PhaseListener * SystemEventListener * Converter * Validator * ... more? For extension writers: Support for native container-injection for all artifacts defined in section 11.4.6 of the JSR-314 spec. ■ ActionListener ■ ApplicationFactory ■ FacesContextFactory ■ LifecycleFactory ■ NavigationHandler ■ PropertyResolver ■ RenderKit ■ RenderKitFactory ■ ResourceHandler ■ StateManager ■ VariableResolver ■ ViewHandler There is a related SPEC issue, Mojarra enhancement, and GlassFish bug also involved in getting this standardized across the board: https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=763 https://glassfish.dev.java.net/issues/show_bug.cgi?id=11655 https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1578 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Google SoC
Hi! - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling Any idea how this should work? What magic is Spring Conversations using here? Ciao, Mario
RE: Google SoC
Hi! From: Leonardo Uribe [mailto:lu4...@gmail.com] Sent: Tuesday, March 09, 2010 7:54 PM To: MyFaces Development Subject: Re: Google SoC - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling I was thinking based on a suggestion done on JSFDays to take advantage on trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), and refactor that code to allow orchestra conversation scope work without spring (using the new JSF 2.0 custom scope). [Mario Ivankovits] Orchestra without Spring, that surely would be great. One thing to keep in mind is that we need AOP or at least proxying to inject the current conversation into the bean. Not too complicated, though. But what does this have to do with trinidad's pageFlowScope? If we leave the EntityManager thing out of line, we just need a JSF 2.0 scope impl and the proxying/interception stuff which is handled by Spring currently. Ciao, Mario
Re: Google SoC
hi mario, ~orchestra without spring will be part of myfaces-codi (hopefully). regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/3/9 Mario Ivankovits ma...@ops.co.at Hi! *From:* Leonardo Uribe [mailto:lu4...@gmail.com] *Sent:* Tuesday, March 09, 2010 7:54 PM *To:* MyFaces Development *Subject:* Re: Google SoC - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling I was thinking based on a suggestion done on JSFDays to take advantage on trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), and refactor that code to allow orchestra conversation scope work without spring (using the new JSF 2.0 custom scope). * * * [Mario Ivankovits] Orchestra without Spring, that surely would be great. One thing to keep in mind is that we need AOP or at least proxying to inject the current conversation into the bean. Not too complicated, though.* *But what does this have to do with trinidad's pageFlowScope?* *If we leave the EntityManager thing out of line, we just need a JSF 2.0 scope impl and the proxying/interception stuff which is handled by Spring currently.* *Ciao,* *Mario*
Re: Google SoC
2010/3/9 Mario Ivankovits ma...@ops.co.at Hi! *From:* Leonardo Uribe [mailto:lu4...@gmail.com] *Sent:* Tuesday, March 09, 2010 7:54 PM *To:* MyFaces Development *Subject:* Re: Google SoC - Extend Orchestra use Conversations based on the JSF 2.0 custom scope API, Extend Orchestra to work with Spring Conversations, to do File-New Window Handling I was thinking based on a suggestion done on JSFDays to take advantage on trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), and refactor that code to allow orchestra conversation scope work without spring (using the new JSF 2.0 custom scope). * * * [Mario Ivankovits] Orchestra without Spring, that surely would be great. One thing to keep in mind is that we need AOP or at least proxying to inject the current conversation into the bean. Not too complicated, though.* *But what does this have to do with trinidad's pageFlowScope?* The code behind pageFlowScope could be used to create a conversational scope. It is just that code has some utility stuff that could be used. *If we leave the EntityManager thing out of line, we just need a JSF 2.0 scope impl and the proxying/interception stuff which is handled by Spring currently.* *Ciao,* *Mario*
[jira] Commented: (MYFACES-2593) styles are escaped so that @import *.css doesn't work
[ https://issues.apache.org/jira/browse/MYFACES-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843277#action_12843277 ] Jakob Korherr commented on MYFACES-2593: After some debugging I found out that style gets escaped in the HtmlResponseWriterImpl. Unfortunately I can't imagine why this was done. I've never heard before that the content of style should be escaped. Furthermore the content of script is only escaped for old browsers. Maybe this was also the reason to put this in for style, but this is a blocker for some new CSS features (like @import) and thus I think we have to drop it for style. styles are escaped so that @import *.css doesn't work - Key: MYFACES-2593 URL: https://issues.apache.org/jira/browse/MYFACES-2593 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Environment: CSS Reporter: Ganesh Jung Assignee: Jakob Korherr This one doesn't pull the script with MyFaces 2.0: style type=text/css @import test.css /style No problem with Mojarra here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google SoC
This is in regard with how Trinidad handle JavaScript free fallback during mobile rendering. Basically, we assign the JavaScript capability for a few mobile user-agents to 'none' in their capability files (Trinidad maintains a capability file for each user-agent). The method supportsScripting determines whether to fallback based on a user-agent's JavaScript capability, and this method is available in org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.XhtmlRenderer. I guess we can tweak this method based on some configuration parameter to return false to accomplish JavaScript free fallback. Mechanism behind JavaScript free fallback: The primary purpose of the JavaScript in the client-side is to assign values to parameters like source, event, etc. 1) During fallback rendering, we encode all these parameters and their values to the name attribute of a component. Example, for commandButton, we render: input type = submit name = sourceencodingkeysourcevalue / All components that are intended to submit a page are rendered as input element of type 'submit' and their name attributes are encoded with parameters and their values. Also, we render a hidden parameter '_noJavaScript' during form rendering to indicate that parameters are encoded. 2) During page submission, the submitting component's name attribute which contains the encoded parameters will be returned to the server. In the Trinidad filter, we check for the hidden parameter '_noJavaScript', if true, we wrap the incoming httpRequest with a wrapper that decoded these parameters from the name attribute. The wrapper adds these decoded parameters (source, event) to the parameterMap. Wrapper Class: org.apache.myfaces.trinidadinternal.webapp.wrappers.BasicHTMLBrowserRequestWrapper Example, a page has two commandButtons, whose source parameters are 'commandButton1' and 'commandButton2' respectively. These commandButtons will be rendered as below: input type = submit name = source_parameterkeycommandButton1 / input type = submit name = source_parameterkeycommandButton2 / if the page is submitted by commandButton2, the payload will contain 'source_parameterkeycommandButton2'. Hence, the wrapper can decoded the source parameter value to be 'commandButton2' Hope it helps. Thanks Mamallan On 3/9/2010 9:51 AM, Matthias Wessendorf wrote: On Tue, Mar 9, 2010 at 8:19 AM, Martin Marinschek mmarinsc...@apache.org wrote: Ok - if you are alright with that, I would have some more proposals. Some starters in the following: - Partial State Saving performance improvements in MyFaces 2.0 - Implement a JavaScript-Free Fallback in Tomahawk, Trinidad and/or Tobago Trinidad has some fallback already, however it is only applied when mobile rendering is involved (by user-agent detection of the components). So, we could port that... Basically, we assign the JavaScript capability for a few mobile user-agents to 'none' in their capability files (Trinidad maintains a capability file for each user-agent). The method supportsScripting which determines whether to fallback based on a user-agent's JavaScript capability is available in org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.XhtmlRenderer. I guess we can tweak this method based on some configuration parameter to return false to accomplish JavaScript free fallback. Mechanism behind JavaScript free fallback: The primary purpose of the JavaScript in the client-side is to assign values to parameters like source, event, etc. 1) During fallback rendering, we encode all these parameters and their values to the name attribute of a component. Example, for commandButton, we render: input type = submit name = sourceencodingkeysourcevalue / All components that are intended to submit a page are rendered as input element of type 'submit' and their name attributes are encoded with parameters and their values. Also, we render a hidden parameter '_noJavaScript' during form rendering to indicate that parameters are encoded. 2) During page submission, the submitting component's name attribute which contains the encoded parameters will be returned to the server. In the Trinidad filter, we check for the hidden parameter '_noJavaScript', if true, we wrap the incoming httpRequest with a wrapper that decoded these parameters from the name attribute. The wrapper adds these decoded parameters (source, event) to the parameterMap. Wrapper Class: org.apache.myfaces.trinidadinternal.webapp.wrappers.BasicHTMLBrowserRequestWrapper Example, a page has two commandButtons, whose source parameters are 'commandButton1' and 'commandButton2' respectively. These commandButtons will be rendered as below: input type = submit name = source_parameterkeycommandButton1 / input type = submit name = source_parameterkeycommandButton2 / if the page is submitted by commandButton2, the payload will contain 'source_parameterkeycommandButton2'. Hence, the wrapper can
[jira] Created: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at every
click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2593) styles are escaped so that @import *.css doesn't work
[ https://issues.apache.org/jira/browse/MYFACES-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2593. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 styles are escaped so that @import *.css doesn't work - Key: MYFACES-2593 URL: https://issues.apache.org/jira/browse/MYFACES-2593 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-beta-2 Environment: CSS Reporter: Ganesh Jung Assignee: Jakob Korherr Fix For: 2.0.0-beta-3 This one doesn't pull the script with MyFaces 2.0: style type=text/css @import test.css /style No problem with Mojarra here. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
[
https://issues.apache.org/jira/browse/MYFACES-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843284#action_12843284
]
Martin Koci commented on MYFACES-2594:
--
This problem is the same issue I've reported against mojarra:
https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1414
Please note that myfaces have problem only in case of
PARTIAL_STATE_SAVING=false.
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at
every click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
[
https://issues.apache.org/jira/browse/MYFACES-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843290#action_12843290
]
Jakob Korherr commented on MYFACES-2594:
Mhm. This is caused, because the current state saving mechanism relies on
rebuilding the view from the VDL page (.xhtml or .jsp). I also had a problem
with this once.
It seems that we somehow have to detect those dynamic tree alterations and also
store them in the state to be able to restore them in the next postback. The
best thing would be to check for the current lifecycle phase when the children
of a component are altered, I think.
Unfortunately I guess the spec does not say anything about this...
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at
every click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
[
https://issues.apache.org/jira/browse/MYFACES-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843297#action_12843297
]
Leonardo Uribe commented on MYFACES-2594:
-
At first view, I think the case with PARTIAL_STATE_SAVING=false should work
(because the whole tree is saved and restored) and the case with
PARTIAL_STATE_SAVING=true should not. We should verify these conditions first.
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at
every click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
[
https://issues.apache.org/jira/browse/MYFACES-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843322#action_12843322
]
Martin Koci commented on MYFACES-2594:
--
PARTIAL_STATE_SAVING=false: the problem is that switched order of components is
never saved. VDL.buildView during Render Response reverts it back. The most
suspicious are if -conditons in ComponentTagHandlerDelegate:
if (facetName == null)
{
parent.getChildren().remove(c);
}
and
if (facetName == null)
{
parent.getChildren().add(c);
}
Result of Render Response is UIData with children=[column1,column2] although
after Invoke Application it was children=[column2,column1]
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at
every click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1746) move InputStreamProvider to be a public API
[ https://issues.apache.org/jira/browse/TRINIDAD-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman resolved TRINIDAD-1746. -- Resolution: Fixed Fix Version/s: 1.2.13-core move InputStreamProvider to be a public API --- Key: TRINIDAD-1746 URL: https://issues.apache.org/jira/browse/TRINIDAD-1746 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Affects Versions: 1.2.13-core Reporter: Jeanne Waldman Assignee: Jeanne Waldman Fix For: 1.2.13-core Attachments: MoveInputStreamProviderToAPI1.2.12.patch, MoveISPAndNameResolverToAPI1.2.12.patch Make InputStreamProvider a public API. This means move org.apache.myfaces.trinidadinternal.share.io.InputStreamProvider to org.apache.myfaces.trinidad.share.io.InputStreamProvider This is needed to implement TRINIDAD-1729 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1727) Tag Doc to list JS Component Class
[ https://issues.apache.org/jira/browse/TRINIDAD-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman updated TRINIDAD-1727: - Resolution: Fixed Fix Version/s: 1.2.13-plugins Status: Resolved (was: Patch Available) Tag Doc to list JS Component Class -- Key: TRINIDAD-1727 URL: https://issues.apache.org/jira/browse/TRINIDAD-1727 Project: MyFaces Trinidad Issue Type: Improvement Components: Documentation Affects Versions: 1.2.11-plugins Reporter: Maria Kaval Assignee: Jeanne Waldman Priority: Minor Fix For: 1.2.13-plugins Attachments: JIRA1727.patch In the component summary section of the component tag doc today, there is a line for UIComponent Class. The UI component class then links to the Java Doc for the corresponding Java Class. This JIRA will track two things: 1) Rename UIComponent Class to Java Class 2) Add a JavaScript Class line to the component summary section at the top of the tag doc which will link to the corresponding JS doc in the js_docs_out directory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1750) Update NameResolver's getProvider doc to say it should return null instead of returning IOException since IOExceptions are expensive
Update NameResolver's getProvider doc to say it should return null instead of returning IOException since IOExceptions are expensive Key: TRINIDAD-1750 URL: https://issues.apache.org/jira/browse/TRINIDAD-1750 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Reporter: Jeanne Waldman Assignee: Jeanne Waldman We might call NameResolver getProvider in a loop for each custom NameResolver - if there are custom NameResolvers. And if so, then we do not want the method to return IOException if the file cannot be resolved. Therefore, change the javadoc to say it should return null if the file name cannot be resolved. Also, update the implementations that we have now so that we do not get NullPointerExceptions if getProvider returns null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2594) Facelets state saving doesn't handle well programmatic component manipulation
[
https://issues.apache.org/jira/browse/MYFACES-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843459#action_12843459
]
Werner Punz commented on MYFACES-2594:
--
Dont get me wrong here since I am more an outsider on this one, but shouldn´t
this be fixable by dragging some kind of child meta information into the delta
state, if the user changes something.
Facelets state saving doesn't handle well programmatic component manipulation
-
Key: MYFACES-2594
URL: https://issues.apache.org/jira/browse/MYFACES-2594
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.0.0-beta-3
Environment: myfaces trunk
Reporter: Martin Koci
Priority: Minor
Simple tests (code pasted below) outputs following results:
1) JSP: switchs colums at every click with no problem
2) Facelets with javax.faces.PARTIAL_STATE_SAVING=false - no visual switch
3) Facelets with javax.faces.PARTIAL_STATE_SAVING=true switchs colums at
every click with no problem
Common code from test.jspx and test.xhtml
... jsp: or facelets stuff here ...
h:form id=form
h:commandButton value=Switch columns
f:actionListener binding=#{testBean} /
/h:commandButton
h:dataTable id=table
h:column
f:facet name=header
h:outputText value=firstName /
/f:facet
/h:column
h:column
f:facet name=header
h:outputText value=surname /
/f:facet
/h:column
/h:dataTable
/h:form
@ManagedBean
@RequestScoped
public class TestBean implements ActionListener {
public void processAction(ActionEvent event) throws
AbortProcessingException {
FacesContext context = FacesContext.getCurrentInstance();
UIComponent table =
context.getViewRoot().findComponent(form:table);
UIComponent column1 = table.getChildren().get(0);
UIComponent column2 = table.getChildren().get(1);
table.getChildren().clear();
table.getChildren().add(column2);
table.getChildren().add(column1);
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
