Hi Mark! On Wed, May 1, 2013 at 11:31 AM, Mark Struberg <[email protected]> wrote:
> > a.) There should be no need to change anything for you in your own code. > All the refactoring is just internally. > > sorry, don't understand. should be no need to change anything in my code, and then you say, 'refactoring is just internally'? > b.) If you do performance testing, then please always switch MyFaces to > ProjectStage 'Production'. > done... i keep project to 'production'...always. I learned that by the big 'comment' outputted in server log when I started using MyFaces (many months ago). :) > c.) regarding atmosphere: you could use the tomcate WebSocket stuff which > is more EE7 like already. > interesting... i have seen some on tomcat list ask about tomcat websocket stuff, and I have recognized that tomcat has did some websocket changes in tomcat 7.0.35 or 7.0.37 release (forgot which one, exactly). are you saying that I could replace atmosphere with tomcat websocket stuff? if so, wow... free myself of atmosphere 'dependency'?!?! :) when I was using glassfish, I saw websocket/comet samples in the past, but thought it was 'easier' to use PrimeFaces Push (and that was the first reason why I started using tomee/tomcat7, since primefaces push or atmosphere needs a lot of work to work with glassfish). > > d.) OWB does not yet support async-supported. But having 1 element in the > servlet chain which doesnt set this flag makes the servlet container switch > off that feature anyway. > hmm interesting... i am aware that servlet 3 has async support; seems as though you are telling me that OWB is not-yet-fully servlet-3-compliant, but I'm not trying to say that too loudly, so please feel free to correct me. :) also, in response to you, I am not implicitly setting async-supported anywhere in my web.xml. There are 2 variables in the game > 1.) tomee > 2.) atmosphere > > if you switch back to an older tomee version: works > correct; from what I remember, an older version of tomee (owb 1.1.8) works with latest version of atmosphere if you keep newest tomee and only switch back atmosphere to an older > version: works > correct; newest tomee works with older atmosphere > only if you have both newest tomee and newest atmosphere: broken > almost-correct. :) both atmosphere and tomee are telling me that this is neither an issue with atmosphere or tomee, so i don't want to say 'broken'; the only unwanted behavior is the 'new' atmosphere log line that shows up in my server/tomcat7-stderr/catalina log on every full page refresh :) > > Oki, so now what does all the logs tell you? Per the test case at the following: https://github.com/smithh032772/PrimePushCounter.git the log shows the following whenever I press F5 key to refresh page in browser: Apr 30, 2013 4:59:15 PM org.atmosphere.cpr.DefaultBroadcaster <init> INFO: /counter support Out Of Order Broadcast: false Apr 30, 2013 5:02:40 PM org.atmosphere.cpr.DefaultBroadcaster <init> INFO: /counter support Out Of Order Broadcast: false > Any Exceptions which got swallowed, etc? > very good question. to this day, i have not learned how to recover tomcat-swallowed exceptions. :) i hope this response helps.
