SERIALIZE_STATE_IN_SESSION - What does it do?
We have a custom address tag that seems to behave differently based on whether SERIIALIZE_STATE_IN_SESSION is set to true or false. When it is set to true, the values entered by the user on the page never make it to the managed bean. When it is set to false, the values entered do make it to the managed bean. Any idea why changing the value of this parameter would impact the property being updated in the managed bean or not? Our applications are running in a clustered environment, so we are thinking that SERIALIZE_STATE_IN_SESSION should be set to true so things will failover correctly. Is that correct? Thanks This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document.
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Hi Check if your view scope managed beans implements Serializable interface. When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope beans, and if you have not marked them as Serializable, the values will get lost. In a cluster, it is possible to find configurations where a session is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with that scenario, to avoid exceptions later when the session is deserialized. regards, Leonardo Uribe 2014-09-04 14:51 GMT-05:00 kim.cal...@oneamerica.com: We have a custom address tag that seems to behave differently based on whether SERIIALIZE_STATE_IN_SESSION is set to true or false. When it is set to true, the values entered by the user on the page never make it to the managed bean. When it is set to false, the values entered do make it to the managed bean. Any idea why changing the value of this parameter would impact the property being updated in the managed bean or not? Our applications are running in a clustered environment, so we are thinking that SERIALIZE_STATE_IN_SESSION should be set to true so things will failover correctly. Is that correct? Thanks This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document.
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
i will try to reproduce it, the issue apparently is with ears 2014-09-04 15:12 GMT-05:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com : if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
@Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
the issue is wars of an ear inherit from lib beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com: @Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Decide what to rerender on server side?
Primefaces offers several ways to do client side stuff from the server. For examples see here: http://www.primefaces.org/showcase/ui/misc/requestContext.xhtml While I use primefaces I prefer to keep my hands out of the cookie jar with stuff like this. I mean a datepicker can be replaced with a js widget in 20 minutes if you use a composite component that wraps primefaces date picker. However this stuff would be painful to replace. So my question is, could this be done in some way with JSF or myfaces-impl? cheers
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
As you already know, MyFaces provide some extensions and those extensions register some CDI beans. But the way how the dependencies are loaded are controlled by Tomee and by the CDI implementation, in this case OWB. I have tried in the past to avoid the CDI beans in the integration point, but it is not possible, you need one in order to hold the beans in the scope, and you cannot access JSF from CDI (it works the opposite, access CDI from JSF). regards, Leonardo Uribe 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: the issue is wars of an ear inherit from lib beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com: @Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
but you can share in both something (common thing is the classloader) to match the bean (or name) you need. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:38 GMT+02:00 Leonardo Uribe lu4...@gmail.com: As you already know, MyFaces provide some extensions and those extensions register some CDI beans. But the way how the dependencies are loaded are controlled by Tomee and by the CDI implementation, in this case OWB. I have tried in the past to avoid the CDI beans in the integration point, but it is not possible, you need one in order to hold the beans in the scope, and you cannot access JSF from CDI (it works the opposite, access CDI from JSF). regards, Leonardo Uribe 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: the issue is wars of an ear inherit from lib beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com: @Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
2014-09-04 16:04 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: but you can share in both something (common thing is the classloader) to match the bean (or name) you need. I don't understand. MyFaces just provide the extension points. When and how the extensions are called are up to CDI and maybe Tomee. I suppose the AmbiguousResolutionException is caused because MyFaces is loaded twice by Tomee (when it is using ear). Split that code in a separate jar will not help. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:38 GMT+02:00 Leonardo Uribe lu4...@gmail.com: As you already know, MyFaces provide some extensions and those extensions register some CDI beans. But the way how the dependencies are loaded are controlled by Tomee and by the CDI implementation, in this case OWB. I have tried in the past to avoid the CDI beans in the integration point, but it is not possible, you need one in order to hold the beans in the scope, and you cannot access JSF from CDI (it works the opposite, access CDI from JSF). regards, Leonardo Uribe 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: the issue is wars of an ear inherit from lib beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com: @Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com: Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- --- *SCJA. José Luis Cetina* --- -- --- *José Luis Cetina* ---
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Leonardo, Thanks for the response. We don't have any view scoped managed beans. The bean is session scoped. It does implement Serializable. We recently migrated from MyFaces 1,1,4 to MyFaces 2.1.13. This worked fine before, but isn't working now, if SERIALIZE_STATE_IN_SESSION is set to true. We are still using JSPs, not Facelets. I've stepped through the code several times and haven't discovered the issue yet. Kim Calvin Sr Systems Consultant - Web Solutions OneAmerica P.O. Box 368 Indianapolis, IN 46206 Phone: (317) 285-2401 Fax: (317) 285-7696 kim.cal...@oneamerica.com OneAmerica companies: AUL | State Life | OneAmerica Securities | McCready and Keene | PML | AUL RMS From: Leonardo Uribe lu4...@gmail.com To: MyFaces Discussion users@myfaces.apache.org, Date: 09/04/2014 04:19 PM Subject:Re: SERIALIZE_STATE_IN_SESSION - What does it do? Hi Check if your view scope managed beans implements Serializable interface. When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope beans, and if you have not marked them as Serializable, the values will get lost. In a cluster, it is possible to find configurations where a session is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with that scenario, to avoid exceptions later when the session is deserialized. regards, Leonardo Uribe 2014-09-04 14:51 GMT-05:00 kim.cal...@oneamerica.com: We have a custom address tag that seems to behave differently based on whether SERIIALIZE_STATE_IN_SESSION is set to true or false. When it is set to true, the values entered by the user on the page never make it to the managed bean. When it is set to false, the values entered do make it to the managed bean. Any idea why changing the value of this parameter would impact the property being updated in the managed bean or not? Our applications are running in a clustered environment, so we are thinking that SERIALIZE_STATE_IN_SESSION should be set to true so things will failover correctly. Is that correct? Thanks This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document. __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document.
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Hi 2014-09-04 16:23 GMT-05:00 kim.cal...@oneamerica.com: Leonardo, Thanks for the response. We don't have any view scoped managed beans. The bean is session scoped. It does implement Serializable. We recently migrated from MyFaces 1,1,4 to MyFaces 2.1.13. This worked fine before, but isn't working now, if SERIALIZE_STATE_IN_SESSION is set to true. We are still using JSPs, not Facelets. I've stepped through the code several times and haven't discovered the issue yet. Many things has happened since 1.1. JSP was deprecated in JSF 2.0 and the suggested way is migrate JSP views into Facelets. Some component libraries for JSF 2.0 deprecate JSP too. My suggestion is you could try first move your application to MyFaces 1.2.12 (JSF 1.2) (change from JSF 1.1 EL to Unified EL) and then convert your JSP views into Facelets and try 2.1.13. regards, Leonardo Uribe Kim Calvin Sr Systems Consultant - Web Solutions OneAmerica P.O. Box 368 Indianapolis, IN 46206 Phone: (317) 285-2401 Fax: (317) 285-7696 kim.cal...@oneamerica.com OneAmerica companies: AUL | State Life | OneAmerica Securities | McCready and Keene | PML | AUL RMS From: Leonardo Uribe lu4...@gmail.com To: MyFaces Discussion users@myfaces.apache.org, Date: 09/04/2014 04:19 PM Subject:Re: SERIALIZE_STATE_IN_SESSION - What does it do? Hi Check if your view scope managed beans implements Serializable interface. When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope beans, and if you have not marked them as Serializable, the values will get lost. In a cluster, it is possible to find configurations where a session is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with that scenario, to avoid exceptions later when the session is deserialized. regards, Leonardo Uribe 2014-09-04 14:51 GMT-05:00 kim.cal...@oneamerica.com: We have a custom address tag that seems to behave differently based on whether SERIIALIZE_STATE_IN_SESSION is set to true or false. When it is set to true, the values entered by the user on the page never make it to the managed bean. When it is set to false, the values entered do make it to the managed bean. Any idea why changing the value of this parameter would impact the property being updated in the managed bean or not? Our applications are running in a clustered environment, so we are thinking that SERIALIZE_STATE_IN_SESSION should be set to true so things will failover correctly. Is that correct? Thanks This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document. __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ This e-mail message is intended only for the use of the individual or entity to which the transmission is addressed. Any interception may be a violation of law. If you are not the intended recipient, any dissemination, distribution or copying of this e-mail is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the document.
Re: Decide what to rerender on server side?
Karl, you could look at PrimeFaces requestContext implementation (source code). also, you can maybe ask for something like this to be added as a feature request in MYFACES JIRA. Is there any reason why you prefer not to use PrimeFaces requestContext or the similar feature that is available in OmniFaces library? On Thu, Sep 4, 2014 at 4:30 PM, Karl Kildén karl.kil...@gmail.com wrote: Primefaces offers several ways to do client side stuff from the server. For examples see here: http://www.primefaces.org/showcase/ui/misc/requestContext.xhtml While I use primefaces I prefer to keep my hands out of the cookie jar with stuff like this. I mean a datepicker can be replaced with a js widget in 20 minutes if you use a composite component that wraps primefaces date picker. However this stuff would be painful to replace. So my question is, could this be done in some way with JSF or myfaces-impl? cheers
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
In an ear you have lib part and war libs. Mf only needs war part. If you put mf in lib part, mf needs to ensure it doesn't add again beans. For it you can generate a name for your beans in the extension. This name would be contextual and finally lib part will never be used normally but it will not create any conflict. Le 4 sept. 2014 22:18, Leonardo Uribe lu4...@gmail.com a écrit : 2014-09-04 16:04 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: but you can share in both something (common thing is the classloader) to match the bean (or name) you need. I don't understand. MyFaces just provide the extension points. When and how the extensions are called are up to CDI and maybe Tomee. I suppose the AmbiguousResolutionException is caused because MyFaces is loaded twice by Tomee (when it is using ear). Split that code in a separate jar will not help. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:38 GMT+02:00 Leonardo Uribe lu4...@gmail.com: As you already know, MyFaces provide some extensions and those extensions register some CDI beans. But the way how the dependencies are loaded are controlled by Tomee and by the CDI implementation, in this case OWB. I have tried in the past to avoid the CDI beans in the integration point, but it is not possible, you need one in order to hold the beans in the scope, and you cannot access JSF from CDI (it works the opposite, access CDI from JSF). regards, Leonardo Uribe 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: the issue is wars of an ear inherit from lib beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com : @Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe lu4...@gmail.com: Hi I have tested the latest snapshot from trunk and it is working with tomee 1.7.0. I don't see any exception from this side. regards, Leonardo Uribe 2014-09-03 17:23 GMT-05:00 José Luis Cetina maxtorz...@gmail.com : Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i use the omnifaces viewscoped) and the f:viewAction. But again im getting javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution exception that i reported a few months ago, apparently myfaces 2.2.4 is not working with ears in tomee 1.7.0. I already reported to tomee mailing list but @Romain sayed think so but more a MF issue this time I think @Leonardo 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. smithh032...@gmail.com: if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep OmniFaces CDI @ViewScoped until someone helps you with your issue. Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I experienced no issues. My app is not packaged as an EAR. today, i am using MyFaces 2.2 @ViewScoped beans even though I still have OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). For the first day, running MyFaces 2.2, I am quite pleased. No issues to report, no exceptions in tomee/tomcat log files. On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed CODI and my app is package as ear. maybe i need to try tomee 1.6.1-snapshot 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.com wrote: I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 that's exactly what I did and I don't get the error. Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? -- ---
