do you have a sample with a single bean reproducing the issue? but this is not linked to the last updates on classloading i think (maybe open another thread to ensure it and not make this one noisy?)
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/15 Howard W. Smith, Jr. <[email protected]> > FYI, the following is standard procedure for me, and this has worked for > me...ever since i started using tomee. > > 1. start tomee (an earlier version of tomee 1.6.0 snapshot) > 2. login to web app > 3. logout web app (which takes me back to login page) > 4. stop tomee, install latest tomee 1.6.0 snapshot > 5. start tomee > 6. login to app (since login.xhtml is still open in browser) > > it seems as though my user bean (pf_UsersController) is not invoking > @PostConstruct, because values that have not been null...are now null with > this latest snapshot. > > i'm sure i can do my best to clean up my code and handle/avoid NPE's, but i > wonder what changed in tomee to 'require' me to tighten up my code like > this. lol :) > > > > > > On Wed, May 15, 2013 at 1:20 AM, Howard W. Smith, Jr. < > [email protected]> wrote: > > > well, the latest version that works with my web app (WAR) is > > > > apache-tomee-1.6.0-20130510.041047-66-plus.zip > > > > and > > > > apache-tomee-1.6.0-20130514.041132-71-plus.zip > > > > results in the reported behavior/exceptions. > > > > > > > > > > On Wed, May 15, 2013 at 1:16 AM, Romain Manni-Bucau < > [email protected] > > > wrote: > > > >> There were no changes for wars.... > >> Le 15 mai 2013 07:12, "Howard W. Smith, Jr." <[email protected]> a > >> écrit : > >> > >> > I take that back. With that (latest) snapshot, I am seeing some > strange > >> > (and unwanted) behavior. > >> > > >> > On user login, I had to 'tighten up' my code and handle some null > >> pointer > >> > exceptions. I really don't know what caused the errors. > >> > > >> > It seems like the exceptions occur if I do the following steps: > >> > > >> > 1. start tomee (an earlier version of tomee 1.6.0 snapshot) > >> > 2. login to web app > >> > 3. logout web app (which takes me back to login page) > >> > 4. stop tomee, install latest tomee 1.6.0 snapshot > >> > 5. start tomee > >> > 6. login to app (since login.xhtml is still open in browser) > >> > > >> > in the gist[1], you will find: > >> > > >> > 1. local host log (earlier this evening between 6-7pm my time) which > has > >> > exceptions 'after' I attempted to start 'latest' tomee 'snapshot' and > >> login > >> > my web app > >> > > >> > 2. tomcat7 stderr log (little before 1am, few minutes ago, my time) > >> when i > >> > was attempting to start latest tomee snapshot and login to my web app > >> > > >> > 3. tomcat7 stderr log between 7pm and 1am, when I was running earlier > >> > version of tomee 1.6.0 snapshot > >> > > >> > I wish I knew what changed in latest tomee for it to start misbehaving > >> this > >> > way. :) > >> > > >> > [1] https://gist.github.com/smithh032772/5581744 > >> > > >> > > >> > > >> > On Tue, May 14, 2013 at 1:29 PM, Howard W. Smith, Jr. < > >> > [email protected]> wrote: > >> > > >> > > true... 'others' (myself) just tested latest snapshot and tomee > >> started > >> > > and my web app running/working 'as expected'. :) > >> > > > >> > > > >> > > > >> > > > >> > > On Tue, May 14, 2013 at 12:53 PM, Romain Manni-Bucau < > >> > > [email protected]> wrote: > >> > > > >> > >> it should only affect ears, a lot of users only deploy wars > ;)...but > >> > >> others > >> > >> can test > >> > >> > >> > >> *Romain Manni-Bucau* > >> > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > >> > >> *Blog: **http://rmannibucau.wordpress.com/*< > >> > >> http://rmannibucau.wordpress.com/> > >> > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > >> > >> *Github: https://github.com/rmannibucau* > >> > >> > >> > >> > >> > >> > >> > >> 2013/5/14 Howard W. Smith, Jr. <[email protected]> > >> > >> > >> > >> > when you talk like that, it sounds like 'all' tomee > community/users > >> > >> should > >> > >> > test. :) > >> > >> > > >> > >> > > >> > >> > > >> > >> > On Tue, May 14, 2013 at 12:46 PM, Romain Manni-Bucau > >> > >> > <[email protected]>wrote: > >> > >> > > >> > >> > > yes, > >> > >> > > > >> > >> > > i hacked on the issue too (there was some real issues) so > >> crossing > >> > >> > fingers > >> > >> > > to not have broken something else but it should be better > >> > >> > > > >> > >> > > *Romain Manni-Bucau* > >> > >> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > >> > >> > > *Blog: **http://rmannibucau.wordpress.com/*< > >> > >> > > http://rmannibucau.wordpress.com/> > >> > >> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > >> > >> > > *Github: https://github.com/rmannibucau* > >> > >> > > > >> > >> > > > >> > >> > > > >> > >> > > 2013/5/14 hwaastad <[email protected]> > >> > >> > > > >> > >> > > > Hi, > >> > >> > > > I found out my problem. My EAR has skinny wars and by > accident > >> the > >> > >> > > ear/lib > >> > >> > > > contained a myface-api jar. > >> > >> > > > Somehow this worked earlier.... > >> > >> > > > > >> > >> > > > Well, sorry for making such a fuzz due to my own mistakes :-) > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > -- > >> > >> > > > View this message in context: > >> > >> > > > > >> > >> > > > >> > >> > > >> > >> > >> > > >> > http://openejb.979440.n4.nabble.com/Last-1-6-0-Snapshot-exception-tp4662940p4662945.html > >> > >> > > > Sent from the OpenEJB User mailing list archive at > Nabble.com. > >> > >> > > > > >> > >> > > > >> > >> > > >> > >> > >> > > > >> > > > >> > > >> > > > > >
