Mailing-List: contact chemistry-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chemistry-dev@incubator.apache.org
Message-ID: <889192793.1250585715097.JavaMail.jira@brutus>
Date: Tue, 18 Aug 2009 01:55:15 -0700 (PDT)
From: "Daniel Lichtenberger (JIRA)" <jira@apache.org>
To: chemistry-dev@incubator.apache.org
Subject: [jira] Commented: (CMIS-47) AtomPub: Empty responses on Glassfish
 2.1
In-Reply-To: <2087892027.1249912695246.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CMIS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744422#action_12744422 ] 

Daniel Lichtenberger commented on CMIS-47:
------------------------------------------

Thanks! It would be helpful to have it in 0.61 as well for me, since this is the version I'm currently using.

> AtomPub: Empty responses on Glassfish 2.1
> -----------------------------------------
>
>                 Key: CMIS-47
>                 URL: https://issues.apache.org/jira/browse/CMIS-47
>             Project: Chemistry
>          Issue Type: Bug
>          Components: atompub, server
>         Environment: Chemistry 0.61 (SVN), Glassfish 2.1, Linux, Java 1.6.0_14
>            Reporter: Daniel Lichtenberger
>            Assignee: Florent Guillaume
>         Attachments: CMISServiceResponse.patch
>
>
> I'm getting empty responses with a Chemistry-based AtomPub server on Glassfish 2.1. I'm extending AbderaServlet and use Chemistry's CMISProvider to encapsulate our own repository implementation.
> The same EAR works with JBoss 4.2, and the AtomPub servlet also works with Jetty. A bit of debugging has shown that Abdera and Chemistry process the requests correctly, but the response is never actually written to the container's output stream. Explicitly flushing Chemistry's stream writer in CMISServiceResponse solved the problem  for me (see attached patch against 0.61). Flushing the stream at a later point does not work, as it seems that the StreamWriter itself is not closed or flushed properly.

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