Gili wrote:
> Craig McClanahan (via Nabble) wrote:
>
> > Gili wrote:
> >> Craig McClanahan wrote:
> >>
> >>> ClientConfig config = new DefaultClientConfig();
> >>> config.getClasses().add(MultiPartReader.class);
> >>> config.getClasses().add(MultiPartWriter.class);
> >>> config.getClasses().add(MultiPartBeanProvider.class);
> >>> config.getClasses().add(MultiPartConfigProvider.class);
> >>> client = Client.create(config);
> >>>
> >>>
> >>
> >> Hi,
> >>
> >> I'm curious, do I still need to manually wire the ClientConfig to use
> >> jersey-multipart on the client?
> >>
> >> Gili
> >>
> > My experience was that this was indeed necessary, although it's worth
> > trying without because there might have been improvements in this area
> > in the client code, since I originally wrote this code.
>
> Nope, the manual configuration is still required. Though
> MultiPartBeanProvider no longer exists... Am I supposed to use
> MultipartFormDispatchProvider instead?
>
I should have noticed this earlier ... sorry.
MultiPartBeanProvider only (and still) exists in the unit tests for
jersey-multipart. It's not part of the actual API like the other three
classes are.
> Gili
Craig
>
> ------------------------------------------------------------------------
> View this message in context: Re: [Jersey] Hello World! and Welcome to
> jersey-multipart
> <http://n2.nabble.com/Hello-World%21-and-Welcome-to-jersey-multipart-tp1343189p1560568.html>
> Sent from the Jersey mailing list archive
> <http://n2.nabble.com/Jersey-f576304.html> at Nabble.com.