Mark: not a good idea at startup, too much exception are normal (classnotfound etc) Le 2 mai 2013 07:17, "Mark Struberg" <[email protected]> a écrit :
> > hmmm... i understand 'let it break on any exception', but exclude stuff > > like java.io.* ? > > > In IntelliJ Idea you can set an 'Exception breakpoint' and add conditions. > E.g. not trigger if the Exception gets thrown in any java.io.* class. > > LieGrue, > strub > > > > ----- Original Message ----- > > From: "Howard W. Smith, Jr." <[email protected]> > > To: "[email protected]" <[email protected]> > > Cc: > > Sent: Thursday, 2 May 2013, 1:35 > > Subject: Discussing MyFaces, OpenWebBeans, and Atmosphere > > > > Mark, > > > > Per Romain's request, I thought I might change the subject. see my > > responses below. > > > > ---------- Forwarded message ---------- > >> > >> > >>> 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'? > > > > > >> The OWB-1.2 changes are purely owb internally. You don't need to change > > anything in YOUR code ;) > > > > understood, thanks. > > > > > >> 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). :) > > > > > >> Nah, usually 'Development' is perfectly fine. We do a lot of > > caching only > > in Production, but it's disabled for 'Development'. In Dev mode we > > e.g. > > always read the xhtml pages from the files for each request and build up > > the facelets tree info. Whereas in Production we only read the xhtml > once. > > But then you would not be able to change your xhtml files on the fly in > dev > > mode... > > > > Interesting. I will have to keep this in mind, and this motivates me to > > change project state to development and do some testing. I'm even > wondering > > what will happen if I revert to MyFaces 2.1.10 with latest tomee 1.6.0 > > snapshot (without touching/removing owb 1.2 JARs), and a few other > > tomee/myfaces/atmosphere configurations. > > > > I will try to do this, ASAP, and report test results, here as well. > > > >> 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'?!?! :) > > > > > >> That was before I did read you actually use primefaces push which > really > > needs atmosphere. > > > > okay. > > > > > >> 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. :) > > > > > >> OpenWebBeans IS fully servlet-3 compliant. But it does not use the > > async-spported feature yet. > > > > okay. > > > > > > > >> > >> 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. :) > > > > Start up your debugger and let it break on any exception. Then exclude > > stuff like java.io.* etc until you find something you which looks > curious. > > > > hmmm... i understand 'let it break on any exception', but exclude stuff > > like java.io.* ? > > > > > >> i hope this response helps. > >> > >> > >> > >> > > >
