I don't know what error you are seeing, but the configuration could get complicated if you insist on using WAR_BUNDLES_JSF_IMPL.
The Multi-JSF feature is now integrated into the latest nightly build. Does this help?
There were some errors were were seeing which caused us to upgrade Mojarra JSF 2.1.13 (maybe something above 2.1.7 would work). It looks like JBoss AS 7.1.1 comes with Mojara 2.1.
I read your article, and I appreciate the work, it looks like that will work in the future for us.
But right now, the problem with the nightly build is that GateIn-3.5.0.Beta02_jbossas7 is built with JBoss AS 7.1.1. I think I would have a very hard time trying to integrate the nightly build with GateIn.
I could try again with JBossAS 7, maybe we won't get the JSF errors trying to use the prepackaged version of Mojarra.
But I may have to try the WAR_BUNDLES_JSF_IMPL and I know I will at least have to add a JBoss jar, but I don't know the correct one.
I ran our portlets without updating JSF, so we are using what is in modules in JBossAS 7.1.1, which is Mojarra 2.1.7, not 2.1 as I thought.
Here are the INFO messages (I had mentioned they were errors).
18:56:35,973 INFO [stdout] (http--127.0.0.1-8080-4) Unable to find component with clientId 'pbGd691baa4_2defcc_2d4b89_2da9d7_2d92dcb46144e4_j_id1:j_id432', no need to remove it.
18:56:35,973 INFO [stdout] (http--127.0.0.1-8080-4) Unable to find component with clientId 'pbGd691baa4_2defcc_2d4b89_2da9d7_2d92dcb46144e4_j_id1:j_id434', no need to remove it.
If I click a certain link in one of the portlets, the server.log gets several hundred of these (about 20 per second). If the user stays on that portlet page the server.log rapidly fills up with these. The way I fixed this before, was to upgrade to Mojarra 2.1.13, by using the
WAR_BUNDLES_JSF_IMPL, and the spamming INFO messages stopped.
That worked. I will take your advice and upgrade to Mojarra 2.1.13 this way instead of the WAR_BUNDLES_JSF_IMPL option.
Thanks for your help.