Recognize Browser-Version in JSF doesn’t work on WAS6.1

2011-11-03 Thread Georg Füchsle
Hallo! To recognize the user’s browser version I examine the HttpHeader in a request scoped managed bean: FacesContext ctx = FacesContext.getCurrentInstance(); ExternalContext extctx = ctx.getExternalContext(); Map map = extctx.getRequestHeaderValuesMap(); String a

Re: Recognize Browser-Version in JSF doesn’t work on WAS6.1

2011-11-03 Thread Tobias Eisentrager
Hy Georg, You will nee to overwrite the JSF Version which ships with WAS 6.1 - i think it is IBM's implementation of JSF 1.1 - no myfaces here. - Add a current myfaces version to the war's classpath. - In your EAR File you will need to set the class load to PARENT_LAST (To do that open the applica

space character in rendered pages

2011-11-03 Thread Visagie, Gerhard
Hi Guys; We have a Myfaces2,trinidad2 and tomahawk2 site running on Tomcat6. I noticed in the output there are multiple "\&\#\9\;" use to make the output look pretty. (I have added the slashes for html sake). How do I get rid of those? Regards Gerhard Visagie To read FirstRand Bank's Disclaim

Re: Recognize Browser-Version in JSF doesn’t work on WAS6.1

2011-11-03 Thread Georg Füchsle
Hallo Toby, I don't use RAD. Therefore I set the Classloader's settings in the WAS admin console. If I set the Class Loader of the Web-Module to PARENT_LAST, the Web-App cannot be started. I get the following output: [03.11.11 14:40:21:366 CET] 001c WebExtensionP W Servlet Faces Servlet is

Re: Recognize Browser-Version in JSF doesn’t work on WAS6.1

2011-11-03 Thread Tobias Eisentrager
I am not sure how to change it with the Admin console - but it should be similar. Be sure to change it in both - the EAR and the WAR. Did you see this article? http://wiki.apache.org/myfaces/Websphere_Installation On Thu, Nov 3, 2011 at 4:07 PM, Georg Füchsle wrote: > Hallo Toby, > > I don't use

Re: space character in rendered pages

2011-11-03 Thread Leonardo Uribe
Hi I think this is something more related to Trinidad than to MyFaces Core or Tomahawk. The reason is Trinidad has its own renderkits and response writers, so in this case it is better to check Trinidad configuration params first. regards, Leonardo Uribe 2011/11/3 Visagie, Gerhard : > Hi Guys;

Re: Recognize Browser-Version in JSF doesn’t work on WAS6.1

2011-11-03 Thread Georg Füchsle
Hi Toby, I gave up for today. No matter what I do, as soon as I switch the class loader of the webapp I get SRVE0201E: Das Servlet [javax.faces.webapp.FacesServlet] ist keine Servlet-Klasse. when starting the application. I did not mention that I use the sun implementation. On the weekend I will