X hits on this document

56 views

0 shares

0 downloads

0 comments

16 / 20

Chapter 4. The RichFaces Migration Issues 3.1.x

  • -

    3.2.0

T h e r e a s o n w h y u s a g e o f J S F - R I 1 . 2 _ 0 4 c a u s e s t h e p r o b l e m i s n o t y e t i d e n t i f i e d .

4.3.1.5. Workarounds

To avoid generation of errors from MyFaces in case of invalid filter configuration you can set up the following parameters in web.xml:

... <context-param>

< p a r a m - n a m e > o r g . a p a c h e . m y f a c e s . C H E C K _ E X T E N S I O N S _ F I L T E R < / p a r a m - n a m e <param-value>false</param-value> </context-param> ... >

In case of JSF 1.2_04, upgrading to JSF-RI 1.2_07 [https://javaserverfaces.dev.java.net/servlets/ ProjectDocumentList?folderID=8467&expandFolder=8467&folderID=8819] (last stable version) works.

      • 4.3.2.

        RichFaces 3.2.0 with MyFaces 1.2.2 on WebLogic 10 MP1

        • 4.3.2.1.

          Description

If you try to use RichFaces 3.2.0 with MyFaces 1.2.2 on a WebLogic 10 MP1 server the following error appears:

java.lang.IllegalStateException: Servlet response already use stream, Writer not possible ...

The same project works on Tomcat 6.016, Tomcat 5.5.25 WebLogic 10MP1 with RichFaces 3.1.4.

4.3.2.2. Links

  • RichFaces

Forum

[http://www.jboss.com/index.html?

module=bb&op=viewtopic&p=4141659#4141659]

4.3.2.3. How to reproduce

The problem occurs if the environment mentioned above is set.

4.3.2.4. Causes

Unknown. Possible problem with MyFaces on WebLogic 10MP1.

17

Document info
Document views56
Page views56
Page last viewedMon Dec 05 03:04:11 UTC 2016
Pages20
Paragraphs460
Words3352

Comments