Bug 745884 - Consider replacing JBossWeb with the lightweight httpserver for REST endpoint
Summary: Consider replacing JBossWeb with the lightweight httpserver for REST endpoint
Keywords:
Status: CLOSED DUPLICATE of bug 745883
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: EAP
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Tristan Tarrant
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-31
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 19:31 UTC by Manik Surtani
Modified: 2012-07-13 04:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: EDG-31
Environment:
Last Closed: 2011-10-27 07:37:10 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-31 0 None Closed Consider replacing JBossWeb with the lightweight httpserver for REST endpoint 2012-02-13 14:33:53 UTC

Description Manik Surtani 2011-05-16 19:31:23 UTC 
++ This bug is a clone of bug 745883 ++

Complexity: High
project_key: EDG

The current inclusion of JBossWeb in the {{datagrid}} profile is unnecessarily large and unwieldly.

Jason et al have extracted httpserver from the Sun JDK and have repackaged it:

https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/com/sun/httpserver/httpserver/1.0.0.Beta1/httpserver-1.0.0.Beta1.pom

This may be something we could use instead.  Much lighter weight plus it means people won't be able to deploy custom WAR files into the {{datagrid}} profile.

This has some TODOs though:

* Will need a simple Servlet-like wrapper
* Will need to test RestEasy on it
Comment 1 Manik Surtani 2011-05-16 19:32:03 UTC 
Labels: Added: EDG_7
Comment 2 Trustin Lee 2011-05-17 05:17:00 UTC 
Why not Netty?  Bill Burke had some interest in running RestEasy on top of Netty and that makes sense in my opinion.  Less dependency, too.
Comment 3 Tristan Tarrant 2011-09-27 08:39:40 UTC 
Docs QE Status: Removed: NEW
Comment 4 Tristan Tarrant 2011-09-27 08:40:39 UTC 
I wouldn't use the simple httpserver as I wouldn't think it'd be "performant" enough. Netty sounds good.
Comment 5 Manik Surtani 2011-09-27 10:08:03 UTC 
The hard part with raw Netty is that we'd need to get RestEasy working on top of it.  Not impossible - and in fact they may already have an adapter for it - but will need more investigation.  In fact, using Netty would make things easier in that all endpoints will have common config elements.
Comment 6 Bill Burke 2011-09-27 15:02:42 UTC 
I'm definitely interested, but its just a matter of priorities.  Right now I'm focused on security, next will be JAX-RS 2.0.  

I have, in the past, gotten Resteasy to run on top of Grizzly, so it shouldn't be that hard to run it on Netty.  THe abstractions are there.
Comment 7 Tristan Tarrant 2011-10-27 07:37:10 UTC 

*** This bug has been marked as a duplicate of bug 745883 ***
Note You need to log in before you can comment on or make changes to this bug.