Re: [gatein-dev] RestServlet & Request End
Yes I was going to add that this is what I would call a workaround. For
one you are assuming that my REST service knows about a JCR and that I
need to save/commit this session. Also anything else that might be done
during a RequestLifecycle.end() that might cause a failure and the
request to not complete successfully would have to be handled by the
rest service as well no ?
I also don't think this is how requests are handled by the portal
application either. I'm not sure what the exact solution is but I'm
assuming that the REST response should not be completed until the
RestServlet knows everything is finished.
On 09/10/2013 08:42 AM, Nicolas Filotto wrote:
Why not simply calling session.save (what you mean by JCR commit) in
your rest component? No exception should be thrown by
RequestLifeCycle.end()
On Tue, Sep 10, 2013 at 12:00 PM, Nick Scavelli <nscavell(a)redhat.com
<mailto:nscavell@redhat.com>> wrote:
As per https://issues.jboss.org/browse/GTNPORTAL-3257, when a
failure occurs after the REST request handler completes (i.e. JCR
commit), the response is still sent successfully to the client.
Wanted to get some feedback on this. From my perspective this is
something that should probably be handled by the RestServlet in
eXo WS. I don't think there's anything the actual REST service
should do to handle these scenarios. If we are in agreement I can
create a JIRA with eXo WS.
- Nick
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org <mailto:gatein-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/gatein-dev
Attachments:
- attachment.html (text/html — 3.2 KB)