You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Antonio Gallardo (JIRA)" <ji...@apache.org> on 2006/03/27 03:10:22 UTC

[jira] Updated: (COCOON-1814) Deprecated method oa.c.environment.Environment.getOutputStream() still used internally

     [ http://issues.apache.org/jira/browse/COCOON-1814?page=all ]

Antonio Gallardo updated COCOON-1814:
-------------------------------------

        Summary: Deprecated method oa.c.environment.Environment.getOutputStream() still used internally  (was: Deprecated form of getOutputStream() still used internally)
    Fix Version: 2.1.9-dev (current SVN)
    Description: 
class o.a.c.environment.wrapper.EnvironmentWrapper deprecated the parameterless getOutputStream, but still uses it internally, resulting in deprecation log spam.

I made a patch, and then when I checked to see if 2.2-dev is affected I saw that it has been fixed there.  Here's the patch for 2.1.9-dev anyway.

  was:
class oac.environment.wrapper.EnvironmentWrapper deprecated the parameterless getOutputStream, but still uses it internally, resulting in deprecation log spam.

I made a patch, and then when I checked to see if 2.2-dev is affected I saw that it has been fixed there.  Here's the patch for 2.1.9-dev anyway.


> Deprecated method oa.c.environment.Environment.getOutputStream() still used internally
> --------------------------------------------------------------------------------------
>
>          Key: COCOON-1814
>          URL: http://issues.apache.org/jira/browse/COCOON-1814
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.1.8, 2.1.9-dev (current SVN)
>     Reporter: Mark Lundquist
>     Assignee: Antonio Gallardo
>      Fix For: 2.1.9-dev (current SVN)
>  Attachments: patch
>
> class o.a.c.environment.wrapper.EnvironmentWrapper deprecated the parameterless getOutputStream, but still uses it internally, resulting in deprecation log spam.
> I made a patch, and then when I checked to see if 2.2-dev is affected I saw that it has been fixed there.  Here's the patch for 2.1.9-dev anyway.

-- 
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