uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yi-Wen Liu <yiwen...@usc.edu>
Subject Re: submit job programically through http request
Date Tue, 01 Dec 2015 22:51:29 GMT
Hi,

I see, I will think about how to do it another way, thanks for those useful
suggestions!

Thanks,
Yi-Wen

On Mon, Nov 30, 2015 at 7:04 AM, Lou DeGenaro <lou.degenaro@gmail.com>
wrote:

> You're right!  My mistake.  I was fooled by my poor use of eclipse
> reference resolution.  BaseHttpDispatcher is used, not DuccEventDispatcher.
>
> Lou.
>
> On Mon, Nov 30, 2015 at 9:52 AM, Jim Challenger <challngr@gmail.com>
> wrote:
>
> > Lou, the CLI actually uses  DuccEventHttpDispatcherCl which derives from
> > BaseHttpDispatcher which does use the java.net HTTP stuff, not Camel.
> Jim
> >
> > On 11/30/15 8:22 AM, Lou DeGenaro wrote:
> >
> >> In org.apache.uima.ducc.transport.dispatcher.DuccEventDispatcher.
> >> dispatchAndWaitForDuccReply DUCC uses Camel to send a Job request and
> >> receive the reply (and thus HTTP is not directly used).
> >>
> >> Lou.
> >>
> >> On Mon, Nov 30, 2015 at 6:11 AM, Lou DeGenaro <lou.degenaro@gmail.com>
> >> wrote:
> >>
> >> There is nothing magical about DUCC's CLI/API, though it is quite
> >>> convenient. If one wanted to send/receive HTTP directly to the
> >>> appropriate
> >>> DUCC daemon one could.  Fetch the DUCC's CLI package source code to
> >>> discover how it is done.
> >>>
> >>> Lou.
> >>>
> >>> On Sun, Nov 29, 2015 at 6:19 PM, Eddie Epstein <eaepstein@gmail.com>
> >>> wrote:
> >>>
> >>> On Sat, Nov 28, 2015 at 7:28 PM, Yi-Wen Liu <yiwenliu@usc.edu> wrote:
> >>>>
> >>>> Hi,
> >>>>>
> >>>>> Yes I've looked at the document.
> >>>>> Sorry I am not sure I am understanding, so because of security
> identity
> >>>>> issue, it is not allowed to simply send http request to the ducc
> server
> >>>>>
> >>>> by
> >>>>
> >>>>> the user?
> >>>>>
> >>>>> Yes, I believe this is correct.
> >>>>
> >>>> Eddie
> >>>>
> >>>>
> >>>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message