AW: Myfaces + Websphere 6.1 > How to fetch ResponseStateManager?

Hello,

thanks to all your responses regarding the WAS migration. Unfortunately I haven't had the time to respond yet.

My initial problem was caused by the fact that the application hadn't been undeployed properly.

I followed Scott's advice an downgraded my application to JSF 1.1. to get it running. I probably will not switch to Facelets right now.

I am still facing problems.

I do not have a real WAS 6.1 available. Only the one which comes with the RAD7. I am unsecure, wether it is different compared to the the original WAS 6.1.

First issue:
If I bundle the application by hand with maven (according to the myfaces wiki for WAS 6.1 without commons-logging, ...), deploy the file via the administration console of the WAS in RAD, set the classloader of the module properly and access my start-page I will see my starting page but the it does not work properly as the extensionResource-Servlet is not running. A request to
http://<myMachine>:9080/<mycontextRoot>/faces/extensionResource comes up with an 404  contrary to jetty an tomcat. As a consequence my JSCook-Menu is not loaded at all.

Most interestingly I get the following log-statement, no matter whether my META-INF/manifest contains references to the dependencies in the War's WEB-INF/lib-Folder or not:
x.myfaces.x.FacesConfigurator logMetaInf MyFaces-package : myfaces-api not found.
x.myfaces.x.FacesConfigurator logMetaInf MyFaces-package : myfaces-impl not found.
x.myfaces.x.FacesConfigurator logMetaInf MyFaces-package : tomahawk-sandbox not found.
x.myfaces.x.FacesConfigurator logMetaInf MyFaces-package : tomahawk not found.

Regards & thanks for advice in advance

Christian Kölle