You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Barry Kaplan (JIRA)" <ji...@apache.org> on 2006/07/07 00:25:29 UTC
[jira] Created: (HADOOP-351) Remove Jetty dependency
Remove Jetty dependency
-----------------------
Key: HADOOP-351
URL: http://issues.apache.org/jira/browse/HADOOP-351
Project: Hadoop
Type: Wish
Components: ipc
Reporter: Barry Kaplan
Somewhat related to HADOOP-349, it would be nice to not have a Jetty dependency for those of us embedding Hadoop within our own web applications. In particular the Server object is using SocketChannelOutputStream from the Jetty code base. It seems to me that for an object like this it would be better to simply have a Hadoop version of a blocking output stream on an nio channel if necessary vs. using the Jetty version requiring a Hadoop user's to package yet another jar file (and all the complications that are associated with that).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-351) Remove Jetty dependency
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-351?page=all ]
Doug Cutting resolved HADOOP-351.
---------------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
I just committed this. Thanks!
> Remove Jetty dependency
> -----------------------
>
> Key: HADOOP-351
> URL: http://issues.apache.org/jira/browse/HADOOP-351
> Project: Hadoop
> Issue Type: Wish
> Components: ipc
> Reporter: Barry Kaplan
> Assigned To: Devaraj Das
> Fix For: 0.5.0
>
> Attachments: nio_socketstream.patch
>
>
> Somewhat related to HADOOP-349, it would be nice to not have a Jetty dependency for those of us embedding Hadoop within our own web applications. In particular the Server object is using SocketChannelOutputStream from the Jetty code base. It seems to me that for an object like this it would be better to simply have a Hadoop version of a blocking output stream on an nio channel if necessary vs. using the Jetty version requiring a Hadoop user's to package yet another jar file (and all the complications that are associated with that).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-351) Remove Jetty dependency
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-351?page=all ]
Devaraj Das updated HADOOP-351:
-------------------------------
Attachment: nio_socketstream.patch
Modified Server.java to remove Jetty dependency
> Remove Jetty dependency
> -----------------------
>
> Key: HADOOP-351
> URL: http://issues.apache.org/jira/browse/HADOOP-351
> Project: Hadoop
> Issue Type: Wish
> Components: ipc
> Reporter: Barry Kaplan
> Assigned To: Devaraj Das
> Attachments: nio_socketstream.patch
>
>
> Somewhat related to HADOOP-349, it would be nice to not have a Jetty dependency for those of us embedding Hadoop within our own web applications. In particular the Server object is using SocketChannelOutputStream from the Jetty code base. It seems to me that for an object like this it would be better to simply have a Hadoop version of a blocking output stream on an nio channel if necessary vs. using the Jetty version requiring a Hadoop user's to package yet another jar file (and all the complications that are associated with that).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (HADOOP-351) Remove Jetty dependency
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-351?page=all ]
Devaraj Das reassigned HADOOP-351:
----------------------------------
Assign To: Devaraj Das
> Remove Jetty dependency
> -----------------------
>
> Key: HADOOP-351
> URL: http://issues.apache.org/jira/browse/HADOOP-351
> Project: Hadoop
> Type: Wish
> Components: ipc
> Reporter: Barry Kaplan
> Assignee: Devaraj Das
>
> Somewhat related to HADOOP-349, it would be nice to not have a Jetty dependency for those of us embedding Hadoop within our own web applications. In particular the Server object is using SocketChannelOutputStream from the Jetty code base. It seems to me that for an object like this it would be better to simply have a Hadoop version of a blocking output stream on an nio channel if necessary vs. using the Jetty version requiring a Hadoop user's to package yet another jar file (and all the complications that are associated with that).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-351) Remove Jetty dependency
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-351?page=comments#action_12419687 ]
Devaraj Das commented on HADOOP-351:
------------------------------------
Not a problem at all in replicating the class under Hadoop. I will work on it soon.
> Remove Jetty dependency
> -----------------------
>
> Key: HADOOP-351
> URL: http://issues.apache.org/jira/browse/HADOOP-351
> Project: Hadoop
> Type: Wish
> Components: ipc
> Reporter: Barry Kaplan
> Assignee: Devaraj Das
>
> Somewhat related to HADOOP-349, it would be nice to not have a Jetty dependency for those of us embedding Hadoop within our own web applications. In particular the Server object is using SocketChannelOutputStream from the Jetty code base. It seems to me that for an object like this it would be better to simply have a Hadoop version of a blocking output stream on an nio channel if necessary vs. using the Jetty version requiring a Hadoop user's to package yet another jar file (and all the complications that are associated with that).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira