JBossDeveloper

can we keep this work around in setup() and do ..when i tried with this i was not able to run

WebConversation wc = WebConversationFactory.makeWebConversation();
String jsessionId = wc.getCookieValue("JSESSIONID");
wc.putCookie("JSESSIONID", "0000" + jsessionId);

I think it should work fine to initialize the WebConversation in setup(). You just need to make sure that you use a new "WebSphere" WebConversation any time you create a new JSFClientSession.

Stan

A new wiki page for this problem is here:
http://wiki.jboss.org/auth/wiki/JSFUnitOnWebSphere

The code in previous posts is for the Beta 1 and Beta 2 versions of JSFUnit.

Stan

Hey can you help me to get rid from these logs.

Ex:-

FacesConfigur I org.apache.myfaces.config.FacesConfigurator feedStandardConfig Reading standard config META-INF/standard-faces-config.xml

Manfred Maelzer wrote:

I read out the 'serverinfo' now and if there's "websphere" in it I use the workaround to initialize the jsfclientsession.

That's a good idea Manfred.  Since nobody has been able to tell me a programatic way to obtain the cache ID, maybe I'll build a workaround into JSFUnit for the next release.

Stan

Koushlendra kushwah wrote:

 

Hey can you help me to get rid from these logs.

 

Ex:-

FacesConfigur I org.apache.myfaces.config.FacesConfigurator feedStandardConfig Reading standard config META-INF/standard-faces-config.xml

 

FacesConfigur I org.apache.myfaces.config.FacesConfigurator feedContextSpecifiedConfig Reading config /WEB-INF/faces-config.cbotransactional.xml

Koushlendra,

That's a MyFaces message.  It has nothing to do with JSFUnit and it certainly has nothing to do with this discussion.

Stan