I was not able to reproduce it on my *current* workspace. In fact I did the tests months ago and I've done so many tests to try to make it run since then that I don't remember what was the solution to this one. I ended up to the conclusion that there were too many bugs in Seam 3 (see my summary mail) and also in WAS v8 beta (see my posts in the WAS v8 beta forum, search on "CDI", "Seam", "Jboss", my id there is denisF ...) to run seam 3 on WAS 8 now...
Did you changed the amm.filter.properties file in WAS as explained in my summary mail in this forum? Don't know if this is the solution to the problem WAS v8 is supposed to be out in the coming days. If I have time, I could start again to try to run the booking sample app on it or I could wait that some of bugs that i opened in Seam 3 are closed too.. I didn't yet setup a maven/git env to push correction myself (have to learn git and maven before that...). Denis On 06/07/2011 12:48 PM, jonnie911 wrote: > Hi Denis, > > I am trying to get SeamFaces running in WAS 8 Beta and followed your > recommendations, but how did you get around the startup exception? It's that > bean loading problem in AbstractListener which seems to be > "org.jboss.seam.faces.event.SystemEventBridge"? (it's mentioned > http://seam-framework.2283336.n4.nabble.com/seam-booking-from-CR3-preliminary-testing-results-on-WebSphere-v8-beta-td3395111.html#a3397152 > here ) > > Any hints? > > -- > View this message in context: > http://seam-framework.2283336.n4.nabble.com/Summary-of-a-tentative-to-run-seam-booking-from-Seam-3-CR3-on-WebSphere-v8-beta-tp3419431p3580162.html > Sent from the seam-dev mailing list archive at Nabble.com. > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
