smithh032772 wrote:Andy,
Currently, my TomEE/CDI-managed-bean web application pushes data to client(s), perfectly, but what I really want to do is deploy my CDI-managed-bean web application to Glassfish3.1.2.2/WELD, and possibly use Message Beans to send data from Glassfish to TomEE, and TomEE (PrimeFaces Push) will push data to the same clients that are being served by Glassfish/CDI-managed-beans.
I think I need to keep all same code I have now, xhtml page references Push channel, Glassfish/CDI-managed-bean will define the actual push channel ID, and TomEE/PrimeFaces Push will push the data to push channel requested/specified by Glassfish/CDI-managed-bean.
No longer a need to do this, because TomEE and my CDI-managed-bean app is now running on production server, and TomEE/tomcat already has a reputation of working well with PrimeFaces Push (Atmosphere), and my TomEE/CDI-managed-bean web app is performing just as fast as the Glassfish3.1.2.2/JSF-managed-beans web app version.
I replaced most of the frequently-used dynamic SQL with @entity named queries, added query hints (readonly, etc...), and I had to replace many rendered="EL expression" with ui:include src="EL expression" and create new facelets/pages. TomEE committers really helped me big time with the migration to TomEE after I pretty much migrated most of my code from JSF to CDI managed beans.
