shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Lindner (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SHINDIG-297) Split non-servlet parts of the JsServlet out
Date Thu, 04 Nov 2010 01:06:22 GMT

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

Paul Lindner resolved SHINDIG-297.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0

With r1030653 this is now a reality.


> Split non-servlet parts of the JsServlet out
> --------------------------------------------
>
>                 Key: SHINDIG-297
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-297
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Henning Schmiedehausen
>             Fix For: 3.0.0
>
>         Attachments: jsserver.patch, shindig-297-2.patch
>
>
> Over here, we are using parts of the Shindig code base not through servlets but by other
means (using RESTlets, to be exact). Some functionality of Shindig is inside the Servlets
and this is hard to use if you don't actually have a servlet container to deploy these to.

> The attached patch splits the JsServlet into two parts, JsServlet keeps all the functionality
that is servlet specfic and everything else gets moved into JsServer, which contains the Shindig/Javascript
specific code. JsServer then gets injected by Guice into the Servlet. 
> This patch assumes that SHINDIG-294 and SHINDIG-296 are applied. 
> the patch applies to the current trunk directory with "-p2"

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


Mime
View raw message