JSF compatibility

Hello.
I am just getting started with JSF and I only have J2SE1.4 and Tomcat 4.1 installed. I would like to know which version of JSTL and JSF would work with that? I downloaded the 1.2 version from https://javaserverfaces.dev.java.net
Would that be compatible?
Thanks

one more thing though
i want to download the sun java studio creator. which version already has jsf 1.1? i could only find the latest ones

Similar Messages

JSF compatibility with Weblogic8.1

Hi,
I've a question regarding JSF compatibility with Weblogic 8.1.
I'm developing web application using JSF and Rich Faces.I'm using rich faces 3.2 and JSF 1.2. And i'm calling services which is written using JDK1.4 and deployed on weblogic8 .
So I'm worried whether I can deploy my JSF web application on Weblogic 8.1 or not ? I don't know which version of Servlet API JSF uses,I believe if it uses 2.3 then
it might be compatible with Weblogic8.1
Please let me know any info about this ?
Thanks,
Anand

So can I use Servlet 2.3 with JSF 1.2 at Facelets. Will it work ?
As I've google some of the sites and it seems Weblogic 8.1 supports JEE 1.3 technologies and JEE1.3 is fully compliant with the Servlet 2.3 specification only.
So I'm not sure if my application which has presentation layer developed using JSF/facelet could be deployed on weblogic 8.1 or not?

HTML code generated by JSF compatibility

IS it correct that HTML code generated by JSF is not AA compatible and also cannot work properly without Javascript. Can any one site some references supporting/opposing the same.

Don't know, I'm pretty sure it does. Though, I've never used MyFaces. MyFaces is OSS and done by apache. Google it and you can find out more about it.
CowKing

JSP & JSF compatibility

Hi all,
We'll begin in implementing the graduation project. I take some module to implemen it.
All the group will use JSP in their modules. But, i want to use JSF in my module.
Will be any problems when we collect our modules in one package ?

Any reply ?

Robustness of the RI?

I'm interested in knowing what the general consensus is on using the JSF reference implementation in a production environment. Instability and inability to scale could be problems. What was the motivation for creating a reference implementation rather than a production version? Are there any commercial or open source efforts to implement the spec in non-RI mode?
Larry C

I would not recommend using the JSF-RI in a production environment as there are some show-stopping bugs in it at the moment (i.e. invalid HTML syntax being created, sub-views not rendering properly when intermixed with HTML, data_table not being able to display static information, etc...). It seems like it will be cool once all the kinks get worked out, but I would wait for a while. You'll spend a lot of time creating workarounds for the problems.
The reference implementation is a proof that the spec is valid. Basically it is a way for other companies to be able to affix a 100% JSF compatibility sticker on their applications/implementations of JSF (there is much more to this though). The RI doesn't mean that the product cannot be used for a production version though.
David

JSF Cross Browser Compatibility

In reading about JSF I find no promise for cross browser compatibility. Am I to assume that this has been missed because
i. JSF is a specification and not an implementation and I should be looking for the implementation to make that promise.
ii. it's basically to hard to promise this.
iii. I didn't look hard enough.
I am guessing it's a (i) with the likely hood of (ii) to follow. But I would be interested on any feed back that anyone cares to add. For example, a implementation that is trying to promise this.

In my opinion, the JSF specification (or better, any specification) can only refer to other specifications, but never to a concrete software product. Consider a sentence like:
        JSF 1.0 is compatible with IEWhat could that mean? Some possibilities:
(1)     As it happened, until now, we did not stumble over a
        faces application that broke when run on our Faces
        reference implementation (version 1_1_01) in a
        WSAD 5.0 container in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765.
        (To breake means to produce a result not legitimized
        by the spec, or to produce no result when one is
        expected, at least not in a reasonable time.
        Breakdowns caused by power failure or other
        reasons outside the scope of the spec to be ignored)Well, not worth any further comment.
(2)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in a
        WSAD 5.0 container in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765
        (To breake means ...)That is ok... if you have just this combination of components and will never change. Keep in mind that (2) does not promise
anything if you use IE5.5 patch 12345a (and the saying is, there have been several patches to IE ;-)
(3)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any container
        in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765.
        (To breake means ...)Same as (2)
(4)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any container
        in combination with IE 6.0 on any platform with
        any patches.
        (To breake means ...)Maybe what is intended, just impossible to promise. First, such a bold statement about some software can not be proven.
Second, even if you have gained good confidence by thorow testing, who knows which future changes Microsoft will apply to IE 6.0 (via patches, which offen not only correct bugs, but also introduce new and maybe incompatible features)
(5)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any JSP 1.2
        or higher container in combination any broser
        which supports:
           - HTML 4.0.1
           - JavaScript 1.3
           - CSS 1.0
        where IE 6.0 is a browser which supports these
        three standards on any platform with any patches.
        (To breake means ...)It's getting better. But why, for heavens sake, should a JSF specification make a statement about the compliance of IE with HTML 4.0.1, JavaScript 1.3 and CSS 1.0? I think it would be the job of Microsoft to declare the compatibilty of their products with standards (if any applies, whatsoever).
Therefore, lets get rid of these and we have:
(6)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any JSP 1.2
        or higher container in combination any broser
        which supports:
           - HTML 4.0.1
           - JavaScript 1.3
           - CSS 1.0
        (To breake means ...)Nearly finished, just a little bit wordy. It is (nearly) obvious what 'to breake' means. And that it is common wisdom that software breakes, not some specification (Or, as Bertrand Meyer put it, Bubbles don crash. Specifications may be contradictory or fail to describe an algorithm, but never crash). Common wisdom removed gives:
(7)     Implementations of JSF 1.0 need a JSP 1.2 container
        and a browser capable of HTML 4.0.1, JavaScript 1.3
        and CSS 1.0That's it. Specs exist for two reasons. First, to be discussed and thought about. Second, to be implemented. (To the supporters of agile methods: of course you can reverse the sequence ;-). Therefore, specs should be as short and concise as possible, omitting any useless blabla. If the specs are sufficently precise and of moderate complexity, we can even try to prove the compatibility of the specifications. 'COMPATIBLE WITH IE' is advertisement, not tech talk.
Conclusion: Mixing up specifications and implementaions is generally a bad thing. Exception: All sentences where a specification and a implementation are mentioned together should have the form:
         Implementation X does [not] conform to specification Y
---------------------------------------------------------------------------------------------------------I have a follow up question, just inspired by yours. It does not especially concern JSF, but web pages in general.
Some time ago, I stumbled over quite a few web sites with big red eye catchers:
OPTIMIZED FOR INTERNET EXPLORER!!!
And really, they did not look good on Netscape Navigator. Now, my question is, what do you think when you hit such a page? My first thoughts (it's long ago) have been:
    - Oh, nice designers. They really care for the majority of people,
      my neighbor uses an IE.
    - They just skiped the work for other browsers and sell this as an
      optimization. And I didn't get it. Very clever.
    - Poor Guys. Probably they had no other browser at hand.
    - Obviously they had publish this tremendously important information
      under pressure, no time to also optimize for others browsers.Wolfgang Oellinger

JSF 1.2 compatibility with JBoss

I would like to know how to configure (or what is required) JSF 1.2 with JBoss 3.2.x

Indianparadesi wrote:
I would like to know how to configure (or what is required) JSF 1.2 with JBoss 3.2.xI don't think JBoss 3.2.x supports JSF, although I could be wrong.

JSF 1.2 and Weblogic 10.3.6 compatibility issue

Hi All,
Our application have been developed in JSF 1.2 and spring DAO. We have deployed it on Weblogic 10.3.6 X86 server.
We are facing an issue like on page load data are populated in the page. Say for example on page load company list getting populated and displayed in the drop down.
If we do any operation like select a company code or submit the page all the data are flushed out from the pages. After that navigation of pages also doesnot work.
We neither get any logs nor exception.
And i am not getting this issue in my local weblogic server - 10.3.5
We are struggling with this issue for more than 10 days now and its critical time for us to fix it ASAP.
Thanks,
Seetha

Hi kalyan,
We are not getting any logs. the control is going to javascript but the page get refreshed and all data are just vanishing.
We have tried to add below entries in weblogic-application.xml
<wls:prefer-application-packages>
<wls:package-name>com.sun.facelets.*</wls:package-name>
<wls:package-name>com.sun.faces.*</wls:package-name>
<wls:package-name>javax.faces.*</wls:package-name>
<wls:package-name>javax.servlet.*</wls:package-name>
</wls:prefer-application-packages>
No change.
Tried this
<wls:library-ref>
<wls:library-name>jsf</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:implementation-version>1.2</wls:implementation-version>
<wls:exact-match>false</wls:exact-match>
</wls:library-ref>
No Change.
tried this
<wls:prefer-application-resources>
<wls:resource-name>APP-INF/lib</wls:resource-name>
</wls:prefer-application-resources>
No Change
Anything we missing here. Why it is working in my local server and not in Integration server?
Kindly help us.
Thanks,
Seetha

JSF 1.2 - Weblogic 10.3.6 compatibility issue

Hi,
Our application have been developed in JSF 1.2 and spring DAO. We have deployed it on Weblogic 10.3.6 X86 server.
We are facing an issue like on page load data are populated in the page. Say for example on page load company list getting populated and displayed in the drop down.
If we do any operation like select a company code or submit the page all the data are flushed out from the pages. After that navigation of pages also doesnot work.
We neither get any logs nor exception.
And i am not getting this issue in my local weblogic server - 10.3.5
We are struggling with this issue for more than 10 days now and its critical time for us t ofix it ASAP.
Please some one kindly help us here

Hi,
I had the same problem with the migration from WLS 10.3.5 to WLS 10.3.6.
I did some testing with different jdevelopers in combination with WLS 10.3.5 and 10.3.6.
The jdeveloper 11.1.2.3.x is only using the JSF 2.0 library, which is backwards compatible with JSF 1.2.
After deploying with WLS 10.3.6 the ADF library 11.1.1.6.0 and the patches 13656274, 13656372.
With the following instructions
I was able to Run my application without the problems that I had with JSF 1.2 and the JDeveloper 11.1.1.6.0.
best regards,
Remco C.

OC4J 10.1.2.0.2 and JSF RI compatibility

We would like to use JSF with Oracle AS (OC4J) 10.1.2.0.2 which is a J2EE 1.3 certified app server.
What version(s) of JSF RI can we use and what are specific configuration instructions, etc.? thx.

J2EE 1.3? Sorry, you're out of luck. You need at least J2EE 1.4 for JSF 1.x and Java EE 5 for JSF 2.x.
Upgrade or consider another MVC framework like Struts. If I am correct, they goes back to J2EE 1.2.

Jsf and richfaces version compatibility issue

Hi,
I am using JRE 1.5 , jsf 1.2 , richfaces 3.3.3 and deployed in Tomcat 6.0.18. I am getting following error.
javax.servlet.ServletException: /allocator.xhtml @30,163 <rich:tree> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: tree
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:321)
root cause
javax.faces.view.facelets.TagException: /allocator.xhtml @30,163 <rich:tree> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: tree
     com.sun.faces.facelets.compiler.CompilationManager.pushTag(CompilationManager.java:289)
     com.sun.faces.facelets.compiler.SAXCompiler$CompilationHandler.startElement(SAXCompiler.java:228)
     com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
     com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
     com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
     com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     com.sun.org.apache.xerces.internal.parsers.XML11Configuration
Thanks,
BPradhan

In my development box , I can use any version of jre, tomcat.
But, we have our department dev and prod server configured with jre 1.5 and tomcat 6.0.18
Some other applications are running in those environment with jre 1.5 and tomcat 6.0.18. I cannot upgrade just for new application.
when tomcat6 was downloaded in our department dev and prod server , they are installed with jre5. Subsequently servers are upgraded with jre6 but it seems like tomcat recognises jre5 not jre6. Let me know if i am wrong about jre version tomcat is trying to use.
Also, can you help me with the environment I have and problems i am encountering with jsf and richfaces.
Thanks,
BPradhan
Edited by: user618018 on Feb 1, 2013 5:03 PM

JSF Shopping List

Hi all....my development team has been working in a web framework for the past 8+ months and we have hit a few serious roadblocks. I'm considering spearheading a switch to JSF, but I need to know if it will meet our requirements. After a perusal of O'Reilly's JSF book, by Hans Bergen, I have a general feel, but I'm interested in your opinions & experiences--e.g., the framework we're using claims to have certain functionality, but it's clearly broken.
Some of the items on this list have obvious answers & some are answerred in the O'Reilly book, but I'm interested in confirmation from you, the folks in the trenches.
Thanks in advance for your help,
- Mike
Shopping List:
General Items:
- what are JSFs biggest drawbacks if I were to use it as an enterprise technology for the next 5 years?
- what are the biggest problems with Facelets?
- if I use Facelets, do I still have to be a JSP guru?
- what are the best books on JSF?
- which is better, MyFaces or RI?
Specific Items:
- does JSF have the ability to create a library of reusable components?
- backwards compatibility of components as new versions are released?
- server-side and client-side validation?
- can I easily create custom validation components?
- does JSF have any glaring concurrency issues?
- can I programmatically add components to a page at run time?
- does JSF require me to use JDK1.5, or can I use 1.4?
- does JSF support a single application properties file for i18n?
- does JSF support per-page properties file for i18n (that override what is in the application file)?
- can I easily display a single page in a different language?
- does JSF allow for page inheritence? (can I create custom sub-pages from a generic parent "SearchPage"?)

I'll answer the things that I can. You cover quite a range with your questions though...
- what are JSFs biggest drawbacks if I were to use
e it as an enterprise technology for the next 5
years?- JSF is still a young technology and will likely undergo a number of changes that will break backwards compatibility.
- Performance could become an issue on very large applications.
- what are the biggest problems with Facelets?- There are a number of little "got'cha's" once you start getting into it. Expect to be writing a number of custom validators and components.
- There is a lack of control over the faces lifecycle, which can frustrate attempts to skip phases.
- if I use Facelets, do I still have to be a JSP
P guru?Not at all. Faces actually takes over for JSP quite nicely, especially once you realize it's full capability. However, it doesn't hurt to have minimal knowledge of JSP. Nothing more than a developer worth his salary couldn't learn in a day or two.
- what are the best books on JSF?I like Core JavaServer Faces by David Geary and Cay Horstmann. Partial book is online:
http://www.horstmann.com/corejsf/
- which is better, MyFaces or RI?Hah! This could start a few wars. Honestly, haven't looked much at MyFaces but I know that it just extends the RI with some extra components. Most people who use MyFaces swear by it. However, I wrote an entire enterprise application with just the RI and my own customs. Works great!
- does JSF have the ability to create a library of
f reusable components?Yes, absolutely. I did this with my app and the new library will be very helpful to future projects.
- backwards compatibility of components as new
w versions are released?Ok... Here you might have a few problems. I've already heard rumours of JSF 1.2 breaking a lot of 1.1. I know that there were major changes between 1.0 and 1.1 too. The JSF developers do not seem to be terribly concerned with backwards compatibility.
- server-side and client-side validation?Server-side only. You'll need to use a client-side technology (such as JavaScript) for client-side validation. However, JSF components offer JavaScript hooks, so you can easily execute functions onchange, onclick, onblur, etc...
- can I easily create custom validation components?Easy is a relative term. =) Not always. Writing customs will require a high learning curve. How easy it is depends on what you're doing and how closely you're tying it into other pre-existing components/validators/converters. After each custom you write, it starts getting a little easier.
- does JSF support a single application properties
s file for i18n?I'll hazard a guess on this one, don't quote me on it. A separate message properties file is required for each locale. The message bundle will choose the appropriate one for each locale.
- does JSF support per-page properties file for i18n
n (that override what is in the application file)?I think not. Again, just guessing here.
- can I easily display a single page in a different
t language?Yes, actually this is quite easy. Assuming you set up the locale properly, you just need to use the h:outputText component with f:loadBundle to retrieve the messages.
Hope this helps,
CowKing

[JSF 2.0] and HTML 5? How things are planned?

Hello,
How far is JSF 2.0 from handling HTML 5?
Of course, it surely can't handle it today, but maybe next year some of us will find the need of starting their new web site with this new HTML version.
How is it planned? Will HTML 5 be a standard feature of JSF 2 (or JSF 3?) or will it require the download of a special project: an additional component having its own lifecycle?
How things are roughly planned?
Regards,
Grunt.

I predict it will be implemented as a new component library by someone, but on the server side it will probably retain the same Faces servlet (i.e. same lifecycle) making extensive use of the AJAX capabilities. What will be interesting to see is if any new server side interfaces intended to be implemented by UIComponents will show up and what they would look like.
Of course one thing very nice to have is automatic detection and backwards compatibility with non HTML-5 browsers. I predict also that will be there but not work very well.

JSF layout driving me crazy!

I've been working hard on a jsf powered project manager and am running into some problems with IE compatability. I got everything aligned and positioned the way (more or less) I wanted it, but when I tested it against IE all hell broke loose (specifically with the dateInput component). I took a few screen shots to explain my problem...
What it looks like in Firefox: http://img6.imagepile.net/img6/91064firefox.png
What it looks like in IE: http://img6.imagepile.net/img6/76581ie.png
Each div outlined for refrence: http://img6.imagepile.net/img6/77815sh.png
(keep in mind the design is still in development)
CSS:
body {
        padding: 1em;
        font-family: georgia, times, "times new roman", serif;
        color: #000;
img {
        border:0px;
.container {
        border: 1px solid #333;
        overflow: auto;
.banner {
        background-color: #666;
        border-bottom: 1px solid #333;
.banner h1 {
        margin: 0;
        padding: .5em;
.side {
        float: right;
        margin-right: 2em;
        padding-top: 1em;
        padding-bottom: 1em;
        overflow: auto;
        height: 400px;
.sectionHeader {
        text-align: center;
        padding-bottom: 1em;
.side p {
        margin-top: 0;
.content {
        float: left;
        margin-right: 1em;
        padding-top: 1em;
        padding-bottom: 1em;
        margin-left: 2em;
        overflow: auto;
        height: 400px;
.content h2 {
        margin-top: 0;
.footer {
        clear: both;
        background-color: #666;
        text-align: center;
.pageHeader {
        text-align: center;
        padding-top: 1em;
}JSF Code:
    <%@include file="WEB-INF/inc/imports.inc"%>
    <html>
    <head>
            <title>LS Project Manager - Project Creation Wizard</title>
            <link rel="stylesheet" href="css/master.css" type="text/css" />
            <link rel="stylesheet" href="css/tabbedPane.css" type="text/css" />
    </head>
    <body>
    <f:view>
            <t:saveState value="#{pcwBacker}"/>
            <t:div styleClass="container" id="container">
                    <%@include file="WEB-INF/inc/navigationbar.inc"%>
                    <t:div styleClass="pageHeader" id="pageHeader">
                            <t:outputText value="Project Creation Wizard"/>
                    </t:div>
                    <t:div styleClass="content">
                            <t:panelTabbedPane styleClass="tabbedPane"
                                            activeTabStyleClass="activeTab"
                                            inactiveTabStyleClass="inactiveTab"
                                            disabledTabStyleClass="disabledTab"
                                            activeSubStyleClass="activeSub"
                                            inactiveSubStyleClass="inactiveSub"
                                            tabContentStyleClass="tabContent"
                                            serverSideTabSwitch="false"
                                            selectedIndex="#{pcwBacker.currentIncompleteStep - 1}">
                                    <h:form></h:form> 
                                    <t:panelTab label="General Information">
                                            <h:form>
                                            <t:panelGrid columns="3">
                                                    <h:outputText value="Name: "/>
                                                    <h:inputText id="name" value="#{pcwBacker.name}" required="true" />
                                                    <t:message forceSpan="true" for="name"/>
                                                    <h:outputText value="Category:"/>
                                                    <h:selectOneMenu id="category" value="#{pcwBacker.category}" required="true">
                                                            <f:selectItems value="#{pcwBacker.categoryItems}"/>
                                                    </h:selectOneMenu>
                                                    <t:message forceSpan="true" for="category"/>
                                                    <h:outputText value="Status:"/>
                                                    <h:selectOneMenu id="status" value="#{pcwBacker.status}">
                                                            <f:selectItems value="#{pcwBacker.statusItems}"/>
                                                    </h:selectOneMenu>
                                                    <t:message forceSpan="true" for="status"/>
                                                    <h:outputText value="Phase: "/>
                                                    <h:selectOneMenu id="phase" value="#{pcwBacker.phase}">
                                                            <f:selectItems value="#{pcwBacker.phaseItems}"/>
                                                    </h:selectOneMenu>
                                                    <t:message forceSpan="true" for="phase"/>
                                                    <h:outputText value="Date Due: "/>
                                                    <t:inputDate id="date" type="full" value="#{pcwBacker.dueDate}" required="true"
                                                                    popupCalendar="true"/>
                                                    <t:message forceSpan="true" for="date"/>
                                                    <t:commandButton action="#{pcwBacker.enableStepTwo}"
                                                            value="#{pcwBacker.completed ? 'Update' : 'Next Step'}"/>
                                            </t:panelGrid>
                                            </h:form>
                                    </t:panelTab>
                                    <t:panelTab rendered="#{pcwBacker.stepTwoEnabled}" label="People Involved">
                                            <h:form>
                                            <t:panelGrid columns="3">
                                                    <h:outputText value="Leader: "/>
                                                    <h:selectOneMenu id="leader" value="#{pcwBacker.leaderId}" required="true">
                                                            <f:selectItems value="#{pcwBacker.workerItems}"/>
                                                    </h:selectOneMenu>
                                                    <t:message for="leader" forceSpan="true"/>
                                                    <h:outputText value="Assignees: "/>
                                                    <s:selectManyPicklist id="assignees" value="#{pcwBacker.assignees}" size="5">
                                                            <f:selectItems value="#{pcwBacker.workerItems}"/>
                                                    </s:selectManyPicklist>
                                                    <t:message for="assignees" forceSpan="true"/>
                                                    <t:commandButton action="#{pcwBacker.enableStepThree}"
                                                                    value="#{pcwBacker.completed ? 'Update' : 'Next Step'}"/>
                                                    </t:panelGrid>
                                                    </h:form>
                                            </t:panelTab>
                                            <t:panelTab rendered="#{pcwBacker.stepThreeEnabled}" label="Project Description">
                                            <h:form>
                                            <t:panelGrid columns="2">
                                                    <t:inputText/>
                                                    <t:commandButton action="#{pcwBacker.enableFinalStep}"
                                                                    value="#{pcwBacker.completed ? 'Update' : 'Next Step'}"/>
                                            </t:panelGrid>
                                            </h:form>
                                    </t:panelTab>
                                    <t:panelTab rendered="#{pcwBacker.finalStepEnabled}" label="Final">
                                            <h:form>
                                            <t:panelGrid columns="2">
                                                    <t:inputText/><t:commandButton/>
                                            </t:panelGrid>
                                            </h:form>
                                    </t:panelTab>
                            </t:panelTabbedPane>
                    </t:div>
                    <t:div styleClass="side">
                            <t:div styleClass="sectionHeader">
                                    <t:outputText value="Summery"/>
                            </t:div>
                            <t:panelGrid columns="2" cellpadding="10px">
                                    <t:outputText value="Name: #{pcwBacker.name}" rendered="#{pcwBacker.name != null}"/>
                                    <t:outputText value="Status: #{pcwBacker.statusDesc}" rendered="#{pcwBacker.status != null}"/>
                                    <t:outputText value="Phase: #{pcwBacker.phaseDesc}" rendered="#{pcwBacker.phase != null}"/>
                                    <t:outputText value="Category: #{pcwBacker.categoryDesc}" rendered="#{pcwBacker.phase != null}"/>
                                    <t:outputText value="Date Due: #{pcwBacker.dueDate}"/>
                            </t:panelGrid>
                            <h:outputText value="Assignees"/>
                            <t:dataList var="assignee" value="#{pcwBacker.assignees}">
                                    <t:htmlTag value="li">
                                            <t:outputText value="#{pcwBacker.names[assignee]}"/>
                                    </t:htmlTag>
                            </t:dataList>
                    </t:div>
            </t:div>
    </f:view>
    </body>
    </html>The main focus: getting the inputDate working, the border around the container stretching, and not have one div fall beneath another or overlap when the window is resized.
Any help would be endlessly appreciated. Thank you!
Message was edited by:
octoberdaniel

Thank you for the help. I got everything working with:
body {
padding: 1em;
font-family: georgia, times, "times new roman", serif;
color: #000;
img {
border:0px;
.container {
width: 1000px;
margin: 0 auto;
border: 1px solid #333;
.banner {
border-bottom: 1px solid #333;
.banner h1 {
margin: 0;
padding: .5em;
.side {
width: 400px;
float: right;
padding: 1em;
overflow: auto;
height: 400px;
.sectionHeader {
text-align: center;
padding-bottom: 1em;
.side p {
margin-top: 0;
.content {
position: absolute;
padding: 1em;
overflow: auto;
height: 400px;
.content h2 {
margin-top: 0;
.footer {
clear: both;
background-color: #666;
text-align: center;
.pageHeader {
text-align: center;
padding-top: 1em;
Forgeting a doctype also messed some stuff up...
but I am still having trouble with my calander popup... Any idea?
Message was edited by:
octoberdaniel

JSF and links with parameters to restore jsf page state

Hi,
I've been developing a forum using JSF. It's going to be something similar to the one we are just using.
If a user, while browsing forum, find something interesting he should have a possiblity to copy URL form his browser and give it to his friend.
The URL should contain all necesary parameters to restore a same view (a subpage of a forum etc) a first user had. What's best approach to do it ?
Say, I have a few AJAX components on a forum page, how can I restore their states ? What's even more interesting how can I generate add parameters to URL in a browser ?
I've found a good solution for my problem:
[http://ocpsoft.com/prettyfaces/]
"PrettyFaces is an OpenSource extension with enhanced support for +JavaServer
Faces+ - JSF 1.1, 1.2 and 2.0 - enabling creation of bookmark-able,
pretty URLs. PrettyFaces solves the "RESTful URL" problem elegantly,
including features such as: page-load actions, seamless integration with
faces navigation, dynamic view-id assignment, managed parameter
parsing, and configuration-free compatibility with other web frameworks"

best approach would be http://www.phpbb.com/ :-)
seems crazy going to all that hassel, phpbb is so simple, infact a lot of jsf forums such as primefaces [http://primefaces.prime.com.tr/forum/] use phpbb, as you can have your fourm up and running in no time
Edited by: pNev on 3 Meith 2010 00:38

JSF compatibility

Similar Messages

Maybe you are looking for