Problem with clientWindow id and Deltaspike 0.7
Hi, In my sandbox app Deltaspike fails with a TomEE that has been upgraded to 2.2.3. Error: WebBeans context with scope type annotation @WindowScoped does not exist within current thread When I debug it is because Deltaspike asks ServletExternalContextImpl for the ClientWindow. It get's null and everything fails. I have put breakpoints everywhere that ClientWindow can be set and it is simply not set before deltaspike asks. Mark was able to reproduce it once and only once :( Romain got stackoverflow error with that error when he tried against tomee trunk and with my sample project. I asks on myfaces list because I want to know this: When I boot TomEE and make a request to faces servlet, what should set ClientWindow in ServletExternalContextImpl? Any ideas why this is to late (or why deltaspike is to early?) Cheers
Re: Problem with clientWindow id and Deltaspike 0.7
Hi, could you try to use DeltaSpikes window handling? I never faced any issues with JSF 2.0/2.1 and DeltaSpike. Maybe it's some incompatibly between JSF 2.2 and DS in some cases. Maybe we should ask Gerhard, he developed the bridge for JSF 2.2. Regards, Thomas 2014-05-21 20:21 GMT+02:00 Karl Kildén karl.kil...@gmail.com: Hi, In my sandbox app Deltaspike fails with a TomEE that has been upgraded to 2.2.3. Error: WebBeans context with scope type annotation @WindowScoped does not exist within current thread When I debug it is because Deltaspike asks ServletExternalContextImpl for the ClientWindow. It get's null and everything fails. I have put breakpoints everywhere that ClientWindow can be set and it is simply not set before deltaspike asks. Mark was able to reproduce it once and only once :( Romain got stackoverflow error with that error when he tried against tomee trunk and with my sample project. I asks on myfaces list because I want to know this: When I boot TomEE and make a request to faces servlet, what should set ClientWindow in ServletExternalContextImpl? Any ideas why this is to late (or why deltaspike is to early?) Cheers
Re: Problem with clientWindow id and Deltaspike 0.7
@thomas: the bridge just gets active once you enable the client-window of jsf (otherwise deltaspike continues as usual). regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2014-05-21 20:34 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com: Hi, could you try to use DeltaSpikes window handling? I never faced any issues with JSF 2.0/2.1 and DeltaSpike. Maybe it's some incompatibly between JSF 2.2 and DS in some cases. Maybe we should ask Gerhard, he developed the bridge for JSF 2.2. Regards, Thomas 2014-05-21 20:21 GMT+02:00 Karl Kildén karl.kil...@gmail.com: Hi, In my sandbox app Deltaspike fails with a TomEE that has been upgraded to 2.2.3. Error: WebBeans context with scope type annotation @WindowScoped does not exist within current thread When I debug it is because Deltaspike asks ServletExternalContextImpl for the ClientWindow. It get's null and everything fails. I have put breakpoints everywhere that ClientWindow can be set and it is simply not set before deltaspike asks. Mark was able to reproduce it once and only once :( Romain got stackoverflow error with that error when he tried against tomee trunk and with my sample project. I asks on myfaces list because I want to know this: When I boot TomEE and make a request to faces servlet, what should set ClientWindow in ServletExternalContextImpl? Any ideas why this is to late (or why deltaspike is to early?) Cheers
Re: Problem with clientWindow id and Deltaspike 0.7
I can confirm that removing either: dependency groupIdorg.apache.myfaces.extensions.validator/groupId artifactIdmyfaces-extval-core/artifactId version2.0.7/version /dependency Or removing context-param param-namejavax.faces.CLIENT_WINDOW_MODE/param-name param-valueurl/param-value /context-param solves my problem On 21 May 2014 20:57, Gerhard Petracek gerhard.petra...@gmail.com wrote: @thomas: the bridge just gets active once you enable the client-window of jsf (otherwise deltaspike continues as usual). regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2014-05-21 20:34 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com : Hi, could you try to use DeltaSpikes window handling? I never faced any issues with JSF 2.0/2.1 and DeltaSpike. Maybe it's some incompatibly between JSF 2.2 and DS in some cases. Maybe we should ask Gerhard, he developed the bridge for JSF 2.2. Regards, Thomas 2014-05-21 20:21 GMT+02:00 Karl Kildén karl.kil...@gmail.com: Hi, In my sandbox app Deltaspike fails with a TomEE that has been upgraded to 2.2.3. Error: WebBeans context with scope type annotation @WindowScoped does not exist within current thread When I debug it is because Deltaspike asks ServletExternalContextImpl for the ClientWindow. It get's null and everything fails. I have put breakpoints everywhere that ClientWindow can be set and it is simply not set before deltaspike asks. Mark was able to reproduce it once and only once :( Romain got stackoverflow error with that error when he tried against tomee trunk and with my sample project. I asks on myfaces list because I want to know this: When I boot TomEE and make a request to faces servlet, what should set ClientWindow in ServletExternalContextImpl? Any ideas why this is to late (or why deltaspike is to early?) Cheers
Re: Problem with clientWindow id and Deltaspike 0.7
hi karl, that combination (extval + jsf 2.2 bridge of ds) is currently undefined due to the undefined order of the different wrappers... regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2014-05-21 21:38 GMT+02:00 Karl Kildén karl.kil...@gmail.com: I can confirm that removing either: dependency groupIdorg.apache.myfaces.extensions.validator/groupId artifactIdmyfaces-extval-core/artifactId version2.0.7/version /dependency Or removing context-param param-namejavax.faces.CLIENT_WINDOW_MODE/param-name param-valueurl/param-value /context-param solves my problem On 21 May 2014 20:57, Gerhard Petracek gerhard.petra...@gmail.com wrote: @thomas: the bridge just gets active once you enable the client-window of jsf (otherwise deltaspike continues as usual). regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2014-05-21 20:34 GMT+02:00 Thomas Andraschko andraschko.tho...@gmail.com : Hi, could you try to use DeltaSpikes window handling? I never faced any issues with JSF 2.0/2.1 and DeltaSpike. Maybe it's some incompatibly between JSF 2.2 and DS in some cases. Maybe we should ask Gerhard, he developed the bridge for JSF 2.2. Regards, Thomas 2014-05-21 20:21 GMT+02:00 Karl Kildén karl.kil...@gmail.com: Hi, In my sandbox app Deltaspike fails with a TomEE that has been upgraded to 2.2.3. Error: WebBeans context with scope type annotation @WindowScoped does not exist within current thread When I debug it is because Deltaspike asks ServletExternalContextImpl for the ClientWindow. It get's null and everything fails. I have put breakpoints everywhere that ClientWindow can be set and it is simply not set before deltaspike asks. Mark was able to reproduce it once and only once :( Romain got stackoverflow error with that error when he tried against tomee trunk and with my sample project. I asks on myfaces list because I want to know this: When I boot TomEE and make a request to faces servlet, what should set ClientWindow in ServletExternalContextImpl? Any ideas why this is to late (or why deltaspike is to early?) Cheers
