The operating system used by the server should make no difference. However, the appserver software might. Recent (JEE) full-stack webapp servers come with JSF built into the server, but it might not be exactly the same implementation or version of JSF as the one you're using on your desktop. Furthermore, if you develop and test using Tomcat (which doesn have built-in JSF) and then deploy to JBoss or WebSphere (which do), there could be a conflict between the internally-supplied JSF implementation code needed to run under Tomcat and the JSF implementation code that's already in the server.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Apr 12, 2006
i am using jboss 5.1 on both my laptop and on the server
Anyway, i found the issue. One quick point, the remote server is not UNIX server but LINUX server
If you read RichFaces Guide for supported browsers. Then RichFaces is not supported for IE on LINUX server. It supports Firefox and Opera browsers
The reason why they don't list IE for Linux is because there is no IE for Linux. That's the client OS, they're referring to, not the server OS.
I can confidently that, on behalf of myself and all my app users that RichFaces does run just fine on a Linux server and (Windows) IE clients.
IE, however, is notoriously bad at adhering to web standards. For the most part, RIchFaces adapts to the user's browser and smooths out a lot of the IE quirks. The only place I've seen it to really differ noticeably is in the margins and padding on JSF Form objects, and that may actually not be RichFaces fault, since the "h:form" isn't RichFaces, it's core JSF.
Any style information you provide yourself will, alas, have to be tested in IE and non-IE environments unless your audience is exclusively enslaved to IE. RichFaces makes the job slightly more complex, since the RichFaces skins provide a lot of style information themselves and you'll need to co-ordinate with that, but that's not a problem unique to RichFaces.
Fortunately, most of the major browsers (including IE and Firefox) come with tools that can help you analyze the unexpected shifts in layout. Don't forget, however, that the user's "compatability mode" selection for IE can also shift stuff, since IE is not only at variance with the published standards, but varies from release to release as well as which DTD is in effect when the page is rendered.
Joined: Apr 12, 2006
i got your point
i quickly came to my conclusion when i saw it works fine in firefox when i tested the code deployed on LINUX server