ADF 10g on JBoss 7 - JSF Navigation Does Not Work

[wlovett]

Hi Guys and Gals,

I've encountered yet another problem on my long road of ADF 10g migration to JBoss EAP 6.1 aka (I think) JBoss AS 7.2.

I've managed to deploy ADF 10g components without errors during bootup.  However, when I loadup my initial page and then click on an af:CommandButton to navigate to the next page, nothing happens.  In Chrome, the button isn't clickable.  In IE, the button clicks but no action is taken.  This is also a problem for tab components.  I click on a tab, but nothing happens.  It's like JSF navigation has been disabled or is no longer in service.

The backstory with my web.xml, jar list, etc is located here:   https://community.jboss.org/message/822345

I get the same lack of action whether I include JSF 1.1 or JSF 1.2 in my deployment, or if I remove the WAR_BUNDLES_JSF_IMPL from my web.xml and let JBoss use Mojarra 2.1.19.

Any ideas?

[wlovett]

I linked the button's action attribute with a backing bean to see if I could invoke a method.  No luck.

[wlovett]

It seems actionListeners aren't triggering the construction of a backing bean, nor are they invoked in already constructed beans.  I can only get my backing beans to initialize when they are linked to something like a button's text.

[wlovett]

Looks like I've got (at the least) Javascript problems.  When I pull the page up in IE, I get errors such as the one below

The value of the property '_checkUnload' is null or undefined, not a Function object. 

The value of the property '_defaultTZ' is null or undefined, not a Function object. 

Error: The value of the property '_submitFormCheck' is null or undefined, not a Function object

Could it be that the 10g ADF libraries are having some kind of conflict with JBoss and not generating the appropriate accompanying Javascript to support their actions?  Or do you think I left a library out?  ....

[wlovett]

Turns out I needed to modify my web.xml so that the <web-app> portion had a version="2.4" set.  I believe this triggers JBoss to use the correct JSP version.  Previously I had 2.5.

**Edit**

While this may have been part of the trouble, I also had modified the adf-faces-impl files to remove the 10_1_3_4 underscores.  JDev wouldn't use the library if I didn't.  However, this caused a few other problems.  So I've got one set of files that work to compile in JDev and I've got another set that is put in the deployment's WEB-INF/lib directory.