[
https://issues.apache.org/jira/browse/JOSHUA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313474#comment-15313474
]
Matt Post commented on JOSHUA-274:
----------------------------------
[~chrismattmann], CXF looks interesting. It seems like this would be a
replacement for the [Joshua Translation
Engine|https://github.com/joshua-decoder/joshua_translation_engine/]? The one
advantage to doing the front-end in Python is that often the input needs to go
through pre-processing (tokenization — splitting out punctuation, and
normalization — standardizing different forms of punctuation, character sets,
and so on). This has to match what was done to the training data, and that is
usually done using Perl and Python scripts. We could move all of that
pre-processing to Java fairly transparently but it would take some work. I
wonder if there is some overlap in what is done in projects like Tika?
> Use another HTTPServer other than Suns
> --------------------------------------
>
> Key: JOSHUA-274
> URL: https://issues.apache.org/jira/browse/JOSHUA-274
> Project: Joshua
> Issue Type: Improvement
> Components: decoders
> Affects Versions: 6.0.5
> Reporter: Lewis John McGibbney
> Priority: Critical
> Fix For: 6.1
>
>
> This issue concerns the use of the
> [HttpServer|https://github.com/apache/incubator-joshua/blob/master/src/joshua/decoder/JoshuaDecoder.java#L31]
> within JoshuaDecoder.java.
> We should replace the com.sun.net.httpserver.HttpServer implementation and
> other Sun classes with ones from the Java API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
