-
15. Re: Only in Seam 2.3.0.Final, and not Seam 2.2.2.Final: java.lang.ClassCastException: org.jboss.seam.async.ThreadPoolDispatcher_$$_javassist_seam_2 cannot be cast to org.jboss.seam.async.QuartzDispatcher
Jonathan,
your seam-gen generated app is using wrong namespace for async component, therefore it is not started the Quartz scheduler, but the default one.
xmlns:async="http://jboss.com/products/seam/async"
should be
xmlns:async="http://jboss.org/schemas/seam/async"
-
16. Re: Only in Seam 2.3.0.Final, and not Seam 2.2.2.Final: java.lang.ClassCastException: org.jboss.seam.async.ThreadPoolDispatcher_$$_javassist_seam_2 cannot be cast to org.jboss.seam.async.QuartzDispatcher
With the RichFaces 4.1 release we took some first steps in supporting development of mobile web applications with RichFaces. This initial effort included:
- Creating CSS resources to give the richfaces components a mobile L&F, check these out in the RichFaces mobile showcase (http://showcase.richfaces.org/mobile/#home-page)
- Creating a set of javascript and css resources to enable one to create JSF aplilcations in a single page programming model. This is described in the guide: https://community.jboss.org/wiki/GettingStartedWithMobileRichFaces
- Creating a desktop/mobile hybrid application deomnstrating how to use the above tools. Check out the quickstart or the equivalent archetype.
With RichFaces 5 we will improve our mobile story with the development of mobile-specific components.
-
17. Re: Only in Seam 2.3.0.Final, and not Seam 2.2.2.Final: java.lang.ClassCastException: org.jboss.seam.async.ThreadPoolDispatcher_$$_javassist_seam_2 cannot be cast to org.jboss.seam.async.QuartzDispatcher
Hi Marek,
I've tried that, and it works great. Thank you for spotting that. I clearly copied that from the last working copy of my system. You said that it had chosen a default "one" instead, though. If I try both of those URLs in a browser, only the latter, correct one actually returns a file. However, there are occasions upon which the container will shut itself down, such as an invalid persistence unit, or that MySQL driver is missing. Given that any invalid imports in the components.xml file (and any other configuration files, for that matter), do you think it's wise to shut down the container in this situation, too, in order to prevent either lengthy debugging times or inconsistent behaviour. Afterall, the object in question was of type QuartzDispatcher, so realistically it should never return a default thread dispatcher other than one defined within the Quartz suite itself.
Jonathan.
-
18. Re: Only in Seam 2.3.0.Final, and not Seam 2.2.2.Final: java.lang.ClassCastException: org.jboss.seam.async.ThreadPoolDispatcher_$$_javassist_seam_2 cannot be cast to org.jboss.seam.async.QuartzDispatcher
Hi Brian,
Thanks for the information regarding Richfaces. I'd like to try these features, and ideally I'd like to be able to migrate from initial Icefaces components to Richfaces, especially having a Quartz job forcing a push and update to the screens that I've built. I originally did this using the Icefaces RenderManager.
Jonathan.