Problem solved when changing state saving method to "client"... should I submit a bug or is it normal ?

 


De : Gosuin Gilles [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 27 janvier 2005 14:51
À : [email protected]
Objet : Frame problem

 

Hi !

 

I have an application consisting of two frames. A click on the button in one frame should refresh the other one… The problem is that, the first time, it refreshes the frame normally, the next time it replaces the content of the target frame by the content of the issuing frame, and so on, alternatively…

 

Here’s the relevant code :

 

 

<< index.jsf >>

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">

<html>

            <head>

<title>Title</title>

            </head>

            <frameset cols="20%, *">

                        <frame name="leftFrame" src="">

                        <frame name="rightFrame" src="">

            </frameset>

</html>

 

 

<< leftFrame.jsf >>

 

<?xml version="1.0" encoding="UTF-8"?>

<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>

<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>

<%@ taglib uri="http://myfaces.sourceforge.net/tld/myfaces_ext_0_9.tld" prefix="x" %>

<f:view>

            <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

            <html>

                        <head></head>

                        <body>

                                   <center>

                                               <!-- various components here -->

<h:form target="rightFrame">

                                                           <h:commandButton value="Update" action="">

                                               </h:form>

                                   </center>

                        </body>

            </html>

</f:view>

 

 

<< faces-config.xml >>

 

(...)

 

<navigation-rule>

            <navigation-case>

                        <from-outcome>updateRightFrame</from-outcome>

                        <to-view-id>/rightFrame.faces</to-view-id>

            </navigation-case>

</navigation-rule>

 

(...)

 

 

 

Has anyone an idea of where the problem could come from, or at least of a workaround I could use ? If you need more info, I'll be happy to provide it.

 

Thanks,

 

Gilles.

Reply via email to