You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by DARRIGUES Bruno RD-MAPS-ISS <br...@orange-ft.com> on 2006/08/31 15:47:45 UTC
RE: [jira] Commented: (MYFACES-1310) IllegalStateException:StrictServlet api:cannot call getOutputSteam() after getWriter() on Weblogic 8.1sp 5
Hi xavier,
Theses problem comes with myfaces and jsfri librairies in the same classpath. To fixe this bug, you have to create a dummy class (find sample on this forum) and delete the jsfRI from your classpath and it will works fine !
Bruno
-----Message d'origine-----
De : xavier l (JIRA) [mailto:dev@myfaces.apache.org]
Envoyé : jeudi 31 août 2006 14:33
À : DARRIGUES Bruno RD-MAPS-ISS
Objet : [jira] Commented: (MYFACES-1310) IllegalStateException:StrictServlet api:cannot call getOutputSteam() after getWriter() on Weblogic 8.1sp 5
[ http://issues.apache.org/jira/browse/MYFACES-1310?page=comments#action_12431870 ]
xavier l commented on MYFACES-1310:
-----------------------------------
exactly same problem here.
I guess it has something to do with that filter: org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:176)
Have you solved it on a way or another?
thanks
> IllegalStateException:Strict Servlet api:cannot call getOutputSteam()
> after getWriter() on Weblogic 8.1 sp 5
> ----------------------------------------------------------------------
> --------------------------------------
>
> Key: MYFACES-1310
> URL: http://issues.apache.org/jira/browse/MYFACES-1310
> Project: MyFaces Core
> Issue Type: Bug
> Environment: Weblogic 8.1 sp 5
> Reporter: Bruno
> Priority: Blocker
>
> i am migrating my website based on jsf myfaces from JOnAS to WebLogic 8.1 sp 5 and i have still this issue :
> i have downloaded the latest snapshot myfaces-core-1.1.4-snapshot
> tomahawk-1.1.3-snapshot
> java.lang.IllegalStateException: strict servlet API: cannot call getOutputStream() after getWriter()
> at weblogic.servlet.internal.ServletResponseImpl.getOutputStream(ServletResponseImpl.java:162)
> at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:176)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
> at simpa.web.utils.AuthorizationFilter.doFilter(AuthorizationFilter.java:58)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
> it is critical for us as the experimentation should start next week
> thanks in advance Bruno
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira