<?xml version="1.0" encoding="UTF-8"?>
<section id="myfaces" role="NotInToc">
    <?dbhtml filename="myfaces.html"?>
    <sectioninfo>
        <keywordset>
            <keyword>MyFaces</keyword>
            <keyword>RichFaces</keyword>
            <keyword>WebLogic</keyword>
        </keywordset>
    </sectioninfo>
    <title>RichFaces 3.2.0 with MyFaces 1.2.2 on WebLogic 10 MP1</title>
    <section>
        <title>Description</title>
        <para>
            If you try to use <property>RichFaces 3.2.0</property> with <property>MyFaces 1.2.2</property> on a
            <property>WebLogic 10 MP1</property> server the following error appears:
        </para>
            <programlisting role="JAVA"><![CDATA[java.lang.IllegalStateException: Servlet response already use stream, Writer not possible
...]]></programlisting>
       
     
        <para>
            The same project works on <property>Tomcat 6.016</property>, <property>Tomcat 5.5.25</property>  
            <property>WebLogic 10MP1</property>  with <property>RichFaces 3.1.4</property>.
        </para>
    </section>
    <section>
        <title>Links</title>
        <itemizedlist>
            <listitem>
                <para>
                    <ulink url="http://www.jboss.com/index.html?module=bb&amp;op=viewtopic&amp;p=4141659#4141659">RichFaces Forum</ulink>
                </para>
            </listitem>
        </itemizedlist>
    </section>
    <section>
        <title>How to reproduce</title>    
        <para>
           The problem occurs if the environment mentioned above is set.
        </para>
    </section>
    <section>
        <title>Causes</title>
        <para>
            Unknown. Possible problem with <property>MyFaces</property> on <property>WebLogic 10MP1</property>. 
        </para>
    </section>
    
    <section>
        <title>Workarounds</title>
        <para>
            Switching to <ulink url="https://javaserverfaces.dev.java.net/servlets/ProjectDocumentList?folderID=8467&amp;expandFolder=8467&amp;folderID=8819">JSF-RI 1.2_07</ulink>
            fixes the problem (see forum post)
        </para>
    </section>
</section>