[jira] Closed: (SLING-515) IncludeTest fails when run against another Sling instance

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-515.
-------------------------------------

    Resolution: Fixed

Fixed in revision 668150,  DefaultErrorHandlerServlet outputs error info even if response is already committed, without changing response status.

For some reason, the behavior is different when running the integration tests as part of the Maven build (response was not committed in this case) and when running them against a Sling webapp that was already started with mvn jetty:run.

Different Jetty versions are used in both cases, that might explain the difference.

Anyway, I think it's good for the DefaultErrorHandlerServlet to at least output error info even if it's too late to change the HTTP response status, instead of being silent in this case as before.

> IncludeTest fails when run against another Sling instance
> ---------------------------------------------------------
>
>                 Key: SLING-515
>                 URL: https://issues.apache.org/jira/browse/SLING-515
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>    Affects Versions: 2.0.0
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Running the IncludeTest against a separate Sling instance like this:
>  mvn -o -s /dev/null test -Dhttp.port=8080  -Dtest=IncludeTest  -Dhttp.base.path=sling  -Dwebdav.workspace.path=sling
> whereas it passes when run as part of the full build, where Sling runs in the same process and on / as opposed to /sling in the above example.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.