I think that might be debatable as well. My app has been CDI since late last year (2012), and I've been using TomEE (latest versions), and Atmosphere as well.
Now, atmosphere is no longer CDI compliant? I know there are other atmosphere users that have CDI apps and their app is working well. :) right now, I am running latest tomee in production along with an earlier version of atmosphere 1.0.13 snapshot (2013-04-15). So, one would think that I have a CDI app and atmosphere is CDI compliant. right? :) On Tue, Apr 30, 2013 at 4:59 PM, Romain Manni-Bucau <[email protected]>wrote: > Next tomee is cdi compliant, so the issue would be in atmo > Le 30 avr. 2013 22:55, "Howard W. Smith, Jr." <[email protected]> a > écrit : > > > I recognize that openwebbeans JARs are different. > > > > In 2013-04-26 tomee, there are openwebbeans 2013-04-26 JARs > > > > In 2013-04-29 tomee, there are openwebbeans 2013-04-28 JARs > > > > > > > > On Tue, Apr 30, 2013 at 4:48 PM, Howard W. Smith, Jr. < > > [email protected]> wrote: > > > > > interesting. so something changed between 2013-04-26 and 2013-04-29 > > > versions of tomee 1.6.0 snapshot? > > > > > > I can revert to 2013-04-26 version of tomee 1.6.0 snapshot and no > issues > > > if I use latest version of atmosphere 1.0.13 snapshot. :) > > > > > > > > > > > > On Tue, Apr 30, 2013 at 4:40 PM, Romain Manni-Bucau < > > [email protected] > > > > wrote: > > > > > >> Seems it clearly shows that's an atmo issue if it works with a > previous > > >> atmo version (pby in primefaces since atmo is not cdi friendly > normally) > > >> Le 30 avr. 2013 21:20, "Howard W. Smith, Jr." <[email protected] > > > > a > > >> écrit : > > >> > > >> > I am very very new to github, this is my first time publishing a > > project > > >> > (or test case) there. URL below. > > >> > > > >> > https://github.com/smithh032772/PrimePushCounter > > >> > > > >> > I really meant to publish the WAR file. i know you prefer pom/maven, > > but > > >> > this is best i can do for now. > > >> > > > >> > You will need the following: > > >> > > > >> > PrimeFaces 4.0 JAR[1] > > >> > > > >> > Atmosphere 1.0.13 snapshot (latest version) found in snapshot > > folders[2] > > >> > > > >> > atmosphere-runtime > > >> > atmosphere-compat-jbossweb > > >> > atmosphere-compat-tomcat > > >> > > > >> > > > >> > [1] > > >> > > > >> > > > >> > > > http://repository.primefaces.org/org/primefaces/primefaces/4.0-SNAPSHOT/primefaces-4.0-20130421.152903-4.jar > > >> > > > >> > [2] > > >> > > > https://oss.sonatype.org/content/repositories/snapshots/org/atmosphere/ > > >> > > > >> > > > >> > > > >> > On Tue, Apr 30, 2013 at 2:22 PM, Howard W. Smith, Jr. < > > >> > [email protected]> wrote: > > >> > > > >> > > Okay, I have a test case, just trying to upload it to github > (gotta > > >> > > install github for windows). > > >> > > > > >> > > also, I recognized that this behavior occurs on Full Page Refresh; > > >> does > > >> > > not occur for AJAX/PPR requests. > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > On Tue, Apr 30, 2013 at 2:07 PM, Howard W. Smith, Jr. < > > >> > > [email protected]> wrote: > > >> > > > > >> > >> On Tue, Apr 30, 2013 at 1:58 PM, Romain Manni-Bucau < > > >> > >> [email protected]> wrote: > > >> > >> > > >> > >>> I'd need to look deeper in atmos to check but seems you just > have > > a > > >> log > > >> > >>> issue, no? > > >> > >>> > > >> > >> > > >> > >> I don't think it is a log issue anymore. > > >> > >> > > >> > >> > > >> > >>> > > >> > >>> That said please just compare 2 steps with a unique change > > otherwise > > >> > >>> that's > > >> > >>> impossible to help you > > >> > >>> > > >> > >> > > >> > >> I think I have done that. > > >> > >> > > >> > >> step 1: compared latest tomee 1.6.0 snapshot with a previous > > version > > >> of > > >> > >> atmosphere 1.0.13 snapshot (2013-04-15); test result = do not > > >> experience > > >> > >> this unwanted logging/behavior > > >> > >> > > >> > >> step 2: compared latest tomee 1.6.0 snapshot with latest > atmosphere > > >> > >> 1.0.13 snapshot (2013-04-26); test result = unwanted > > >> logging/behavior, > > >> > >> because defaultbroadcaster is instantiated on every user HTTP > > >> request; > > >> > >> which reminds me of @RequestScoped bean with constructor or > > >> > @PostConstruct > > >> > >> executing on every (http) request. > > >> > >> > > >> > >> > > >> > >> > > >> > > > > >> > > > >> > > > > > > > > >
