[jira] [Commented] (MYFACES-4297) Client Side state / stateless views should not force session creation
[ https://issues.apache.org/jira/browse/MYFACES-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887769#comment-16887769 ] NCister commented on MYFACES-4297: -- Hi Thomas. I've cloned, built and tested your commit in the *2.2.x* branch and it *works fine* !! In the next days I will try it on 2.3.x branch ... Thanks again. Nicola Cisternino > Client Side state / stateless views should not force session creation > - > > Key: MYFACES-4297 > URL: https://issues.apache.org/jira/browse/MYFACES-4297 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.2.12, 2.3.4 > Environment: Debian 8.4, Debian 9.9 > Tomcat 7.0.42 + JDK 1.7.0_71 (myfaces 2.2.12) > TomEE 7.1.1 + JDK 1.8.0_212 (myfaces 2.3.4) >Reporter: NCister >Assignee: Thomas Andraschko >Priority: Major > Fix For: 2.2.13, 3.0.0-SNAPSHOT, 2.3.5 > > > Hi. > It seems to be +no way+ to have stateless behavior in myfaces. > I'm using javax.faces.STATE_SAVING_METHOD = *client* in web.xml (... as also > described in this post: > [https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map|https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map)]) > but myfaces always create a session to transfer the FacesContext encoding ( > why ?) > I've noticed that it happens in *FaceletViewDeclarationLanguage* > getResponseEncoding method. > I've already tested my code in mojarra (2.2 and 2.3) and it works fine (it > don't creates any session if not +explicitly+ requested through a > SessionScope or ViewScope Bean) > This is a big problem because any, simple, JSF (myfaces) page is virtually > exposed to DOS or flooding attacks generating zombie sessions) > Does in myfaces exists a way (that I don't know) to manage stateless pages? > Thanks. > NC -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MYFACES-4297) Client Side state / stateless views should not force session creation
[ https://issues.apache.org/jira/browse/MYFACES-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887144#comment-16887144 ] NCister commented on MYFACES-4297: -- Sure ! A snapshot will be fine ! Where and when i can download it ? Will i need to compile it from sources ? > Client Side state / stateless views should not force session creation > - > > Key: MYFACES-4297 > URL: https://issues.apache.org/jira/browse/MYFACES-4297 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.2.12, 2.3.4 > Environment: Debian 8.4, Debian 9.9 > Tomcat 7.0.42 + JDK 1.7.0_71 (myfaces 2.2.12) > TomEE 7.1.1 + JDK 1.8.0_212 (myfaces 2.3.4) >Reporter: NCister >Assignee: Thomas Andraschko >Priority: Major > Fix For: 2.2.13, 3.0.0-SNAPSHOT, 2.3.5 > > > Hi. > It seems to be +no way+ to have stateless behavior in myfaces. > I'm using javax.faces.STATE_SAVING_METHOD = *client* in web.xml (... as also > described in this post: > [https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map|https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map)]) > but myfaces always create a session to transfer the FacesContext encoding ( > why ?) > I've noticed that it happens in *FaceletViewDeclarationLanguage* > getResponseEncoding method. > I've already tested my code in mojarra (2.2 and 2.3) and it works fine (it > don't creates any session if not +explicitly+ requested through a > SessionScope or ViewScope Bean) > This is a big problem because any, simple, JSF (myfaces) page is virtually > exposed to DOS or flooding attacks generating zombie sessions) > Does in myfaces exists a way (that I don't know) to manage stateless pages? > Thanks. > NC -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MYFACES-4297) Client Side state / stateless views should not force session creation
[ https://issues.apache.org/jira/browse/MYFACES-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887096#comment-16887096 ] NCister commented on MYFACES-4297: -- Hi Thomas. I really appreciate your immediate fixing ! Unfortunately I have many installations (about 300) where I can't install a 2.3 compatible Web container (TomEE) so ... yes, I need version 2.2 :( Thanks. Nicola Cisternino. > Client Side state / stateless views should not force session creation > - > > Key: MYFACES-4297 > URL: https://issues.apache.org/jira/browse/MYFACES-4297 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.2.12, 2.3.4 > Environment: Debian 8.4, Debian 9.9 > Tomcat 7.0.42 + JDK 1.7.0_71 (myfaces 2.2.12) > TomEE 7.1.1 + JDK 1.8.0_212 (myfaces 2.3.4) >Reporter: NCister >Assignee: Thomas Andraschko >Priority: Major > Fix For: 2.2.13, 3.0.0-SNAPSHOT, 2.3.5 > > > Hi. > It seems to be +no way+ to have stateless behavior in myfaces. > I'm using javax.faces.STATE_SAVING_METHOD = *client* in web.xml (... as also > described in this post: > [https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map|https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map)]) > but myfaces always create a session to transfer the FacesContext encoding ( > why ?) > I've noticed that it happens in *FaceletViewDeclarationLanguage* > getResponseEncoding method. > I've already tested my code in mojarra (2.2 and 2.3) and it works fine (it > don't creates any session if not +explicitly+ requested through a > SessionScope or ViewScope Bean) > This is a big problem because any, simple, JSF (myfaces) page is virtually > exposed to DOS or flooding attacks generating zombie sessions) > Does in myfaces exists a way (that I don't know) to manage stateless pages? > Thanks. > NC -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MYFACES-4297) Client Side state should not not create sessions
[ https://issues.apache.org/jira/browse/MYFACES-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886891#comment-16886891 ] NCister commented on MYFACES-4297: -- ??Could you work on a patch??? Sorry I haven't such myfaces knowledge to make changes ... :( ??Does the same happen with stateless views? Or just with client side statesaving??? *Yes*, same behavior trying: ... Client Side state should not not create sessions > > > Key: MYFACES-4297 > URL: https://issues.apache.org/jira/browse/MYFACES-4297 > Project: MyFaces Core > Issue Type: Bug > Components: General >Affects Versions: 2.2.12, 2.3.4 > Environment: Debian 8.4, Debian 9.9 > Tomcat 7.0.42 + JDK 1.7.0_71 (myfaces 2.2.12) > TomEE 7.1.1 + JDK 1.8.0_212 (myfaces 2.3.4) >Reporter: NCister >Priority: Major > > Hi. > It seems to be +no way+ to have stateless behavior in myfaces. > I'm using javax.faces.STATE_SAVING_METHOD = *client* in web.xml (... as also > described in this post: > [https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map|https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map)]) > but myfaces always create a session to transfer the FacesContext encoding ( > why ?) > I've noticed that it happens in *FaceletViewDeclarationLanguage* > getResponseEncoding method. > I've already tested my code in mojarra (2.2 and 2.3) and it works fine (it > don't creates any session if not +explicitly+ requested through a > SessionScope or ViewScope Bean) > This is a big problem because any, simple, JSF (myfaces) page is virtually > exposed to DOS or flooding attacks generating zombie sessions) > Does in myfaces exists a way (that I don't know) to manage stateless pages? > Thanks. > NC -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (MYFACES-4297) javax.faces.STATE_SAVING_METHOD behaviour
NCister created MYFACES-4297: Summary: javax.faces.STATE_SAVING_METHOD behaviour Key: MYFACES-4297 URL: https://issues.apache.org/jira/browse/MYFACES-4297 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.3.4, 2.2.12 Environment: Debian 8.4, Debian 9.9 Tomcat 7.0.42 + JDK 1.7.0_71 (myfaces 2.2.12) TomEE 7.1.1 + JDK 1.8.0_212 (myfaces 2.3.4) Reporter: NCister Hi. It seems to be +no way+ to have stateless behavior in myfaces. I'm using javax.faces.STATE_SAVING_METHOD = *client* in web.xml (... as also described in this post: [https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map|https://stackoverflow.com/questions/36650846/when-does-jsf-creates-a-session-what-does-it-puts-in-a-session-map)]) but myfaces always create a session to transfer the FacesContext encoding ( why ?) I've noticed that it happens in *FaceletViewDeclarationLanguage* getResponseEncoding method. I've already tested my code in mojarra (2.2 and 2.3) and it works fine (it don't creates any session if not +explicitly+ requested through a SessionScope or ViewScope Bean) This is a big problem because any, simple, JSF (myfaces) page is virtually exposed to DOS or flooding attacks generating zombie sessions) Does in myfaces exists a way (that I don't know) to manage stateless pages? Thanks. NC -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196551#comment-16196551 ] NCister commented on EXTSCRIPT-188: --- Hi Werner. Excuse me ... what's your test environment ? (app. server, jdk) I've tried example war (blog-example-1.0.6, myfaces20-extscript-helloworld-1.0.6, ... ) in Tomcat 7.0.42 + JDK 1.7 with some problems... Thanks. > Extension don't works on Myfaces 2.2.3 / 2.2.11 > --- > > Key: EXTSCRIPT-188 > URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 > Project: MyFaces Extensions Scripting > Issue Type: Bug > Components: MyFaces 2.0 Extension >Affects Versions: 1.0.6-FINAL > Environment: Debian 8.2 > JDK 1.8 > Tomcat 7.0.42 >Reporter: NCister >Assignee: Werner Punz > Fix For: 1.0.6-SNAPSHOT, 1.0.6-FINAL > > > Trying to follow example config > (http://myfaces.apache.org/extensions/scripting/exampleconfig.html) I've > noticed that the web.xml settings are wrong so: > org.apache.myfaces.FACES_INIT_PLUGINS > org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader > must be updated to: > ... > org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader > ... > Again: The example war > (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) > deployed in a clean tomcat 7.0 instance) don't works (no errors, no results > ...) > Does Groovy integration works in MyFaces 2.2 ? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155664#comment-16155664 ] NCister commented on EXTSCRIPT-188: --- Thank you Werner ! > Extension don't works on Myfaces 2.2.3 / 2.2.11 > --- > > Key: EXTSCRIPT-188 > URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 > Project: MyFaces Extensions Scripting > Issue Type: Bug > Components: MyFaces 2.0 Extension >Affects Versions: 1.0.6-FINAL > Environment: Debian 8.2 > JDK 1.8 > Tomcat 7.0.42 >Reporter: NCister >Assignee: Werner Punz > > Trying to follow example config > (http://myfaces.apache.org/extensions/scripting/exampleconfig.html) I've > noticed that the web.xml settings are wrong so: > org.apache.myfaces.FACES_INIT_PLUGINS > org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader > must be updated to: > ... > org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader > ... > Again: The example war > (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) > deployed in a clean tomcat 7.0 instance) don't works (no errors, no results > ...) > Does Groovy integration works in MyFaces 2.2 ? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155377#comment-16155377 ] NCister commented on EXTSCRIPT-188: --- Hi Werner ! I do not want to be tedious ... :-) ... but ... have you news about this issue ? Regards. > Extension don't works on Myfaces 2.2.3 / 2.2.11 > --- > > Key: EXTSCRIPT-188 > URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 > Project: MyFaces Extensions Scripting > Issue Type: Bug > Components: MyFaces 2.0 Extension >Affects Versions: 1.0.6-FINAL > Environment: Debian 8.2 > JDK 1.8 > Tomcat 7.0.42 >Reporter: NCister >Assignee: Werner Punz > > Trying to follow example config > (http://myfaces.apache.org/extensions/scripting/exampleconfig.html) I've > noticed that the web.xml settings are wrong so: > org.apache.myfaces.FACES_INIT_PLUGINS > org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader > must be updated to: > ... > org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader > ... > Again: The example war > (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) > deployed in a clean tomcat 7.0 instance) don't works (no errors, no results > ...) > Does Groovy integration works in MyFaces 2.2 ? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863625#comment-15863625 ] NCister commented on EXTSCRIPT-188: --- Rapid prototyping and customizing is what we all need ... and Groovy is the best choice for Java developers ! Mojarra (but I've not tested it ...) also implements a Groovy integration starting from 1.2 version (a "GroovyFilter" need to be activated in web.xml ) but my favorite choice is myfaces ( !! ) and your implementation seems to be more interesting and integrated (... I don't like the Mojarra idea to map only some url ...) So, Thanks again ! ;-) P.S. I you need a beta tester please do not hesitate to contact me ! > Extension don't works on Myfaces 2.2.3 / 2.2.11 > --- > > Key: EXTSCRIPT-188 > URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 > Project: MyFaces Extensions Scripting > Issue Type: Bug > Components: MyFaces 2.0 Extension >Affects Versions: 1.0.6-FINAL > Environment: Debian 8.2 > JDK 1.8 > Tomcat 7.0.42 >Reporter: NCister >Assignee: Werner Punz > > Trying to follow example config > (http://myfaces.apache.org/extensions/scripting/exampleconfig.html) I've > noticed that the web.xml settings are wrong so: > org.apache.myfaces.FACES_INIT_PLUGINS > org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader > must be updated to: > ... > org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader > ... > Again: The example war > (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) > deployed in a clean tomcat 7.0 instance) don't works (no errors, no results > ...) > Does Groovy integration works in MyFaces 2.2 ? > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
[ https://issues.apache.org/jira/browse/EXTSCRIPT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863392#comment-15863392 ] NCister commented on EXTSCRIPT-188: --- Thank you Werner ! I think that Groovy is one of more interesting and useful JSF extension (I use Groovy extendible plugins everywhere: Web services, Servlet Filters, ) So, thanks for your work ! P.S. Just an info: which myfaces version the current extension (1.0.6) is compatible with ? (So I can use it to test some code ) Regards. > Extension don't works on Myfaces 2.2.3 / 2.2.11 > --- > > Key: EXTSCRIPT-188 > URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 > Project: MyFaces Extensions Scripting > Issue Type: Bug > Components: MyFaces 2.0 Extension >Affects Versions: 1.0.6-FINAL > Environment: Debian 8.2 > JDK 1.8 > Tomcat 7.0.42 >Reporter: NCister >Assignee: Werner Punz > > Trying to follow example config > (http://myfaces.apache.org/extensions/scripting/exampleconfig.html) I've > noticed that the web.xml settings are wrong so: > org.apache.myfaces.FACES_INIT_PLUGINS > org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader > must be updated to: > ... > org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader > ... > Again: The example war > (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) > deployed in a clean tomcat 7.0 instance) don't works (no errors, no results > ...) > Does Groovy integration works in MyFaces 2.2 ? > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EXTSCRIPT-188) Extension don't works on Myfaces 2.2.3 / 2.2.11
NCister created EXTSCRIPT-188: - Summary: Extension don't works on Myfaces 2.2.3 / 2.2.11 Key: EXTSCRIPT-188 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-188 Project: MyFaces Extensions Scripting Issue Type: Bug Components: MyFaces 2.0 Extension Affects Versions: 1.0.6-FINAL Environment: Debian 8.2 JDK 1.8 Tomcat 7.0.42 Reporter: NCister Assignee: Werner Punz Trying to follow example config (http://myfaces.apache.org/extensions/scripting/exampleconfig.html)I've noticed that the web.xml settings are wrong so: org.apache.myfaces.FACES_INIT_PLUGINS org.apache.myfaces.extensions.scripting.servlet.StartupServletContextPluginChainLoader must be updated to: ... org.apache.myfaces.extensions.scripting.jsf.startup.StartupServletContextPluginChainLoader ... Again: The example war (https://repository.apache.org/content/repositories/releases/org/apache/myfaces/extensions/scripting/myfaces20-extscript-helloworld/1.0.5/myfaces20-extscript-helloworld-1.0.5.war) deployed in a clean tomcat 7.0 instance) don't works (no errors, no results ...) Does Groovy integration works in MyFaces 2.2 ? Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYFACES-4082) Composite binding don't works ...
NCister created MYFACES-4082: Summary: Composite binding don't works ... Key: MYFACES-4082 URL: https://issues.apache.org/jira/browse/MYFACES-4082 Project: MyFaces Core Issue Type: Bug Affects Versions: 2.2.11, 2.2.3 Environment: Debian 8.2 JDK 1.8 Netbeans 8.1 Reporter: NCister Priority: Critical I've just tried to set binding of a simple composite. It don't works :-( To manage the componentType methods from user page the only way is to use ViewRoot.findComponent . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
